Bug#388839: dom0 crashes and reboots machine when domU is started.
Package: xen-linux-system-2.6.17-2-xen-686
Version: 2.6.17-9
I have a testing (Etch) system up to date as of today. I installed
ii libc6-xen 2.3.6.ds1-4
ii linux-image-2.6.17-2-xen-686 2.6.17-9
ii linux-modules-2.6.17-2-xen-686 2.6.17-9
ii xen-docs-3.0-unstable 3.0-unstable+hg11292-2
ii xen-hypervisor-3.0-unstable-1-i386 3.0-unstable+hg11292-2
ii xen-ioemu-3.0-unstable 3.0-unstable+hg11292-2
ii xen-linux-system-2.6.17-2-xen-686 2.6.17-9
ii xen-tools 2.5-2
ii xen-utils-3.0-unstable-1 3.0-unstable+hg11292-2
ii xen-utils-common 3.0+hg11292-2
Hypervisor boots and loads dom0 fine. I had to add 'netloop' to /etc/modules
in order for the bridge to be configured properly.
After that, I built a couple of domU images, one with Sarge and the other with
Etch. When either domU is started, the dom0 panics and reboots. If I remove
the 'vif' from the domu.cfg, then the domU boots but without network interfaces.
I'm using
(network-script network-bridge)
(vif-script vif-bridge)
in xend-config.sxp, and
kernel = '/boot/vmlinuz-2.6.17-2-xen-686'
ramdisk = '/boot/initrd.img-2.6.17-2-xen-686'
vif = [ 'ip=192.168.0.30' ]
in domu.cfg; note that commenting out the last line allows the domU to boot,
but without network interfaces.
--
Ernesto Hernández-Novich - On Linux 2.6.16 i686 - Unix: Live free or die!
Geek by nature, Linux by choice, Debian of course.
If you can't aptitude it, it isn't useful or doesn't exist.
GPG Key Fingerprint = 438C 49A2 A8C7 E7D7 1500 C507 96D6 A3D6 2F4C 85E3
Reply to: