[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#388839: marked as done (dom0 crashes and reboots machine when domU is started.)

Your message dated Fri, 22 Sep 2006 23:38:39 +0200
with message-id <20060922213839.GA13863@wavehammer.waldi.eu.org>
and subject line Bug#388839: dom0 crashes and reboots machine when domU is started.
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
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

--- End Message ---
--- Begin Message --- 
On Fri, Sep 22, 2006 at 04:19:33PM -0400, Ernesto Hernández-Novich wrote:
> 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.

Known regression in 2.6.17. Use 2.6.18.

Bastian

-- 
Hailing frequencies open, Captain.

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: