http://bugzilla.novell.com/show_bug.cgi?id=618678 http://bugzilla.novell.com/show_bug.cgi?id=618678#c10 Harald Koenig <koenig@linux.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|koenig@linux.de | --- Comment #10 from Harald Koenig <koenig@linux.de> 2010-07-02 15:03:01 UTC --- ok, more tests and details;) my currect guess: there is some problem when shutting down a xen domain, either due to problems in old xen kernels (2.6.9) or due to unexpected crash in domU. I've created a very small disk image based on centos-4u4 with both 2.6.9 and 2.6.18 (centos5) kernels which you can find here, together with a small xen config file for testing: ftp://ftp.science-computing.de/outgoing/koenig/xen4/ in the config file there are two bootargs variants: #bootargs="--entry=hda1:/boot/vmlinuz-2.6.9-89.0.23.ELxenU,/boot/initrd-2.6.9-89.0.23.ELxenU.img" bootargs="--entry=hda1:/boot/vmlinuz-2.6.18-8.el5xen,/boot/initrd-2.6.18-8.el5xen.img" 1) with the 4u4 2.6.9 kernel (commented out by default) it will boot and run init=/bin/bash and you have a very limited number of tools (e.g. "mount -n /proc ; ps uax" works;). when I leave this init shell with exit, the kernel will panic due to pid 1 exiting. with xen4 this will terminate the domU (in 11.2 xen3.4 the domU will remain and I have to "xm destroy ..." it). after this single start/crash I can no longer start any domU without reboot of dom0. 2) the 2.6.18 kernel/initrd is a copy of a domU running centos5 -- this centos5 domU does not trigger any problems! BUT: in this example system, it can't mount the rootfs (see before: root partition vs. LVM), so the kernel panics and domU terminates. this is the default setting, because for my 11.3/xen4 server this is enough (as domU id 1) to trigger the problem and block any further startup of can you reproduce that either (1) or (2) will lock you dom0 too ? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.