[Pkg-xen-devel] Bug#623120: xen-utils-4.1: unable to start non-hvm VMs when using Xen 4.1

[Theo Cabrerizo Diem]

Package: xen-utils-4.1
Version: 4.1.0-2
Severity: important

I had a working Xen server with 4.0 hypervisor and 2.6.32 kernels.
After updating (and booting up) 4.1 hypervisor with 2.6.38 kernel, any attempt to create a VM failed (also the ones saved from previous book don't come up either).

If I try to use xl :
# xl create /etc/xen/lithium.vm.carpediem.sh.cfg 
Parsing config file /etc/xen/lithium.vm.carpediem.sh.cfg
libxl: error: libxl_device.c:476:libxl__wait_for_device_model Device Model not ready
xl: fatal error: libxl_create.c:535, rc=-1: libxl__confirm_device_model_startup

There's one line into /var/log/xen/qemu-dm-lithium.vm.carpediem.sh.log (which didn't existed before the xl command):
libxl: cannot execute /usr/lib/xen-4.1/lib/qemu-dm: No such file or directory

Using xm command, which works perfectly if I boot into 4.0 hypervisor with 2.6.32 kernel:
xm create /etc/xen/lithium.vm.carpediem.sh.cfg 
Using config file "/etc/xen/lithium.vm.carpediem.sh.cfg".

Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

Looking into /var/log/xen/xend.log
[...]
[2011-04-16 17:41:52 1941] DEBUG (XendDomainInfo:1881) XendDomainInfo.handleShut
downWatch
[2011-04-16 17:41:52 1941] DEBUG (DevController:139) Waiting for devices tap2.
[2011-04-16 17:41:52 1941] DEBUG (DevController:139) Waiting for devices vif.
[2011-04-16 17:41:52 1941] DEBUG (DevController:144) Waiting for 0.
[2011-04-16 17:41:52 1941] DEBUG (DevController:628) hotplugStatusCallback /loca
l/domain/0/backend/vif/6/0/hotplug-status.

And stays like this ... until I see the shutdown of the domain after the error message described at xm output:
[2011-04-16 17:43:32 1941] DEBUG (XendDomainInfo:3071) XendDomainInfo.destroy: d
omid=6
[2011-04-16 17:43:32 1941] DEBUG (XendDomainInfo:2401) Destroying device model
[2011-04-16 17:43:32 1941] DEBUG (XendDomainInfo:2408) Releasing devices
[...]

Let me know which further information would be needed for additional diagnostics.

PS: If I boot with 4.0 hypervisor and 2.6.32 packages, everything works as intended


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

Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xen-utils-4.1 depends on:
ii  e2fslibs                1.41.12-2        ext2/ext3/ext4 file system librari
ii  iproute                 20110315-1       networking and traffic control too
ii  libc6                   2.11.2-13        Embedded GNU C Library: Shared lib
ii  libncurses5             5.9-1            shared libraries for terminal hand
ii  libuuid1                2.17.2-9.1       Universally Unique ID library
ii  libxenstore3.0          4.1.0-2          Xenstore communications library fo
ii  python-support          1.0.13           automated rebuilding support for P
ii  python2.6               2.6.6-8+b1       An interactive high-level object-o
ii  udev                    167-2            /dev/ and hotplug management daemo
ii  xen-utils-common        4.1.0~rc6-1      XEN administrative tools - common 
ii  zlib1g                  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages xen-utils-4.1 recommends:
ii  bridge-utils                  1.4-5      Utilities for configuring the Linu
ii  xen-hypervisor-4.1-amd64 [xen 4.1.0-2    Xen Hypervisor on AMD64

Versions of packages xen-utils-4.1 suggests:
ii  xen-docs-4.1                  4.1.0-2    Documentation for Xen

-- no debconf information