Pkg xen devel - Mar 2014 - Bug#741456: xen-utils-common: Starting domUs with xm fails - unable to find xenbr0. Works with xl.

Package: xen-utils-common
Version: 4.3.0-3
Severity: normal

Dear Maintainer,

I've just set up a fresh Jessie system using the installer dated 2014-03-05,
then installed and enabled Xen 4.3.  I've done this quite a few times before
using Wheezy and 4.1.

I set up xenbr0, then created a test domU using xen-create-image, which
completed without issue.  However I was unable to start the new domU,
getting the error message:

	Could not find bridge device bridge name
	xenbr0

xenbr0 is definitely there and working and responds to all the usual
diagnostic tools.

I notice that the xen installation still defaults to using xm, although
the documentation says that it's deprecated.  I therefore changed
/etc/default/xen to specify a TOOLSTACK of xl and re-booted.

The domU then started up without difficulty, confirming that xenbr0 is
in fact there and working.

Perhaps it's time to make xl the default?  Is xm suffering from bit rot?

John


-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xen-utils-common depends on:
ii  gawk            1:4.0.1+dfsg-2.1
ii  lsb-base        4.1+Debian12
ii  python          2.7.5-5
ii  ucf             3.0027+nmu1
ii  udev            204-7
ii  xenstore-utils  4.3.0-3+b1

xen-utils-common recommends no packages.

xen-utils-common suggests no packages.

-- Configuration Files:
/etc/default/xendomains changed:
XENDOMAINS_SAVE=""
XENDOMAINS_RESTORE=false
XENDOMAINS_AUTO=/etc/xen/auto
XENDOMAINS_STOP_MAXWAIT=300

/etc/xen/xend-config.sxp changed:
(network-script 'network-bridge bridge=xenbr0')
(vif-script vif-bridge)
(dom0-min-mem 512)
(enable-dom0-ballooning no)
(total_available_memory 0) 
(dom0-cpus 0)
(vncpasswd '')


-- no debconf information