Mailinglist Archive: opensuse-bugs (6165 mails)

< Previous Next >
[Bug 618678] blkback thread hangs after unsuccessful xen domU start
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 1 Jul 2010 18:46:52 +0000
  • Message-id: <20100701184652.14F6A245520@xxxxxxxxxxxxxxxxxxxxxx>
http://bugzilla.novell.com/show_bug.cgi?id=618678

http://bugzilla.novell.com/show_bug.cgi?id=618678#c4


--- Comment #4 from Harald Koenig <koenig@xxxxxxxx> 2010-07-01 18:46:50 UTC ---
(In reply to comment #2)
so I have to reboot again... -- next/last "single domU" test will use a 64bit
suse 11.1 domU instead of cenots, just in case you want to argue... -- so
stay
tuned;-)

uh, oh! I've now tried to start/stop/start/stop other VMs and surprise:
the problem does not get triggered by suse 11.1, sles 11 and centos 5 (both 32
and 64 bit PVMs).
some of them have been changed to use disk images as local files, others still
use iscsi disks (as I was lacy to change all configs;), so at least it's not an
iscsi issue;)

right now it looks like the problem is related to using
vmlinuz-2.6.9-55.0.12.ELxenU or vmlinuz-2.6.9-89.0.23.ELxenU
kernels form centos 4u5 and 4u8, again both 32 and 64 bit domU seem to trigger
the problem!


next update -- even more obfuscation:-(
I replaced that vmlinuz-2.6.9* kernel in a centos4u4 domU
by a 2.6.18-8.el5xen kernel (32bit for 1st test) from centos 5u0 (which I use
successfully
for a centos 5u0 domU), the initrd was directly copied from that working 5u0
domU.

using that 5u0 kernel/initrd the 4u4 did not come up correctly, it crashed
before
it could access the rootfs (because the real 5u0 uses a plain rootfs partition
while the 4u4 has rootfs in LVM -- console log of the crash below).

BUT even if it only used the same kernel/initrd, this domU start
again triggers that problem which blocks any further domU start:-(

there is no additional output from "xm dmesg" when starting/stopping such a
problematic domU, sono additional clue from that channel:-(


right no I do not understand

- why centos 5u0 works fine while booting 5u0 kernel with 4u4 kernel triggers
further problems after crashing at end of initrd
- how to get the centos4 machines working in 11.3/xen4 :-(


just to state again: these PVMs run just fine with 11.1 (xen 3.3) and 11.2 (xen
3.4).

are there known issues in xen 4.0 with older xen kernel versions in domU ?
or any specific issues with centos 4u5/4u8 in xen4 ?



this is the diff between the config files of centos 4u4 and 5u0:

-------------------------------------------------------------------------------
< name="os-centos4u4"
<
bootargs="--entry=hda1:/boot/vmlinuz-2.6.18-8.el5xen,/boot/initrd-2.6.18-8.el5xen.img.c5"
< disk=[ diskroot + 'os-centos4u4-flat.vmdk,hda,w' , diskroot +
'os-centos4u4-builddisk-flat.vmdk,hdb,w' ]
< extra="root=/dev/mapper/VolGroup00-LogVol01"
< vif=[ 'mac=00:0c:29:18:4b:5a,bridge=br0,model=rtl8139', ]
-------------------------------------------------------------------------------
name="os-centos5"
bootargs="--entry=hda1:/boot/vmlinuz-2.6.18-8.el5xen,/boot/initrd-2.6.18-8.el5xen.img"
disk=[ diskroot + 'os-centos5-flat.vmdk,hda,w' ]
extra="root=/dev/hda1"
vif=[ 'mac=00:0c:29:4a:bf:fc,bridge=br0,model=rtl8139', ]
-------------------------------------------------------------------------------

so there is no significant difference...


"expected" (now that I see it;) panic when booting 4u4 disk with 5u0
kernel/initrd:

Started domain os-centos4u4 (id=1)
Linux version 2.6.18-8.el5xen
(mockbuild@xxxxxxxxxxxxxxxxxxx) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52))
#1 SMP Thu Mar 15 21:02:53 EDT 2007
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 000000007d800000 (usable)
1280MB HIGHMEM available.
727MB LOWMEM available.
NX (Execute Disable) protection: active
ACPI in unprivileged domain disabled
Built 1 zonelists. Total pages: 514048
Kernel command line: root=/dev/mapper/VolGroup00-LogVol01
[...]
Creating root device.
Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
Error: Domain 'os-centos4u4' does not exist.
Error: Domain 'os-centos4u4' does not exist.



and here is the full xen config file for the centos4u4 vm -- still hoping that
there will be some bells ringing when you see some "unimportant" bits of
information ;-)


--- 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8<
---
name="os-centos4u4"

memory=1000
maxmem=2000
vcpus=4

on_poweroff="destroy"
on_reboot="restart"
on_crash="restart"
localtime=0


extra="root=/dev/mapper/VolGroup00-LogVol01"

bootloader="/usr/lib/xen/boot/domUloader.py"
builder="linux"
#bootargs="--entry=hda1:/boot/vmlinuz-2.6.9-55.0.12.ELxenU,/boot/initrd-2.6.9-55.0.12.ELxenU.img"
#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.9-89.0.15.plus.c4xenU,/boot/initrd-2.6.9-89.0.15.plus.c4xenU.img"
bootargs="--entry=hda1:/boot/vmlinuz-2.6.18-8.el5xen,/boot/initrd-2.6.18-8.el5xen.img.c5"

diskroot='file:/etc/xen/images/'
#iskroot='iscsi:iqn.2010-04.de.science-computing:'
disk=[ diskroot + 'os-centos4u4-flat.vmdk,hda,w' , diskroot +
'os-centos4u4-builddisk-flat.vmdk,hdb,w' ]

vif=[ 'mac=00:0c:29:18:4b:5a,bridge=br0,model=rtl8139', ]

nographic=1
apic=1
acpi=1
pae=1
# serial="pty"
--- 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8<
---



so, enough for today, I'm running out of ideas for now:-(

--
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.

< Previous Next >
List Navigation