Package: xen-hypervisor-4.0-i386 Version: 4.0.1-2 Severity: normal Hi,
Take the following config file (standard lenny kernel and initrd, with some customization for iSCSI root): name = "lenny3" kernel = "vmlinuz-2.6.26-2-686-bigmem" ramdisk = "initrd.img-2.6.26-2-686-bigmem" memory = 100 vcpus = 1 vif = [ 'mac=00:16:3e:00:00:17, bridge=br695, vifname=lenny3.alma-g' ] extra = "break=top" on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' Start the domain: xm create -c lenny3.conf [...] (initramfs) >From another terminal, save the guest: xm save lenny3 /tmp/lenny3.save The guest console says: Suspending xenbus... and detaches. Restore the guest (paused to attach its console before continuing): xm restore -p /tmp/lenny3.save xm console lenny3 xm unpause lenny3 The console starts spewing out "BUG: recent printk recursion" and the domain spins until destroyed. The same thing happens on (live or not) migration. The very same domains could be migrated without issues under Xen 3.2 (more precisely, before I upgraded my dom0 to squeeze -- previously it was running lenny with the etch dom0 kernel for stability). Migrating squeeze guests isn't a problem in the same setup (just replace 26-2 with 32-5 in the above config). This looks like a regression. On the other hand, it doesn't seem to affect a lot of people, because I couldn't find anything relevant on the web. Please tell me if I can help debugging the issue further. -- Thanks, Feri. -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-xen-686 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash xen-hypervisor-4.0-i386 depends on no packages. Versions of packages xen-hypervisor-4.0-i386 recommends: ii xen-utils-4.0 4.0.1-2 XEN administrative tools Versions of packages xen-hypervisor-4.0-i386 suggests: pn xen-docs-4.0 <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
