Re: [Xen-users] XEN 4.0.1 + pv_ops kernel DomU issues

[David Gonzalez Herrera <dgonzalezh@xxxxxxxxx>]

Hi Ricie,

On Mon, Oct 25, 2010 at 8:52 PM, Richie <listmail@xxxxxxxxxxxx> wrote:

On 10/25/2010 09:11 PM, David Gonzalez Herrera wrote:

Richie,

Well here is the command I use to build my initrd

mkinitrd -v -f --with=xen-netfront --with=xen-blkfront --preload=xen-blkfront --preload=xen-netfront /boot/initrd-2.6.32.24domU.img  2.6.32.24xen

And the command you suggested:

[root@vm linux-2.6-xen]# zcat /boot/initrd-2.6.32.24domU.img | cpio -it | grep xen
15665 blocks
lib/xen-netfront.ko
lib/xen-blkfront.ko

And the error still is coming up:

Trying to resume from /dev/vg0/swap
Unable to access resume device (/dev/vg0/swap)
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!
Pid: 1, comm: init Not tainted 2.6.32.24xen #2
Call Trace:
 [<ffffffff81048a6a>] ? panic+0x86/0x13c
 [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1
 [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1
 [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1
 [<ffffffff8100ef51>] ? xen_force_evtchn_callback+0x9/0xa
 [<ffffffff8100f5d2>] ? check_events+0x12/0x20
 [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1
 [<ffffffff8100f5bf>] ? xen_restore_fl_direct_end+0x0/0x1
 [<ffffffff81309145>] ? _write_lock_irq+0x7/0x16
 [<ffffffff810518ec>] ? exit_ptrace+0x96/0x101
 [<ffffffff8104a7cf>] ? find_new_reaper+0x74/0x7d
 [<ffffffff8104b79e>] ? forget_original_parent+0x2d/0x112
 [<ffffffff8104b893>] ? exit_notify+0x10/0x126
 [<ffffffff8104bbf6>] ? do_exit+0x24d/0x2b1
 [<ffffffff8104bccd>] ? do_group_exit+0x73/0x9d
 [<ffffffff8104bd09>] ? sys_exit_group+0x12/0x16
 [<ffffffff8130971a>] ? error_exit+0x2a/0x60
 [<ffffffff81012a82>] ? system_call_fastpath+0x16/0x1b

I'm sorry if this bothers anyone but I'm no developer and those cryptic kernel messages really leave me lost.

Thanks.

I see you have the following from early post of domU config:

kernel = "/boot/vmlinuz-2.6.32.24xen"
ramdisk = "/boot/initrd-2.6.18domU.img"

It's odd to see 2.6.18 initrd w/2.6.32.24 kernel.  I assume you have since changed this to /boot/initrd-2.6.32.24domU.img?

Yeah Sr, I've changed that, that was a typo I made when creating image.

At some point in time did you install this 2.6.32.24xen kernel within the domU? (or at least copied over the respective /lib/modules into it's filesystem? [haven't done the latter before i think u probably would need System.map as well).

Well That's not very likely to solve the problem because as you see from my config I'm not using pygrub to start the DomU, I'm using custom 2.6.32.24xen kernel and the self-made initrd image, although I tried your suggestion and copied the modules and System.map to DomU with no luck either
 

Alternatively, does the disk.img filesystem have a kernel/initrd to which you can copy out (mount via loopback in dom0, using kpartx as needed) and try as well?

Well yeah I used a local yum-xen.conf and installed it into an image i made with dd, it contains a base CentOS system like debootstrap but fot centos, I monted the .img and copied the modules dir over but as I said no luck, man, I keep searching and some seem to have solved the issue but their medicines are not good for my pain.

Also I tried using stock centos xenified kernel 2.6.18 for which I also created a custom initrd image with the same result, with the exception that I see this 

225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s...
XENBUS: Timeout connecting to device: device/vbd/51713 (local state 3, remote state 1)
Loading ehci-hcd.ko module
Loading ohci-hcd.ko module
Loading uhci-hcd.ko module
USB Universal Host Controller Interface driver v3.0
Loading jbd.ko module
Loading ext3.ko module
Loading scsi_mod.ko module
SCSI subsystem initialized
Loading sd_mod.ko module
Loading libata.ko module
Loading sata_nv.ko module
Loading dm-mod.ko module
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: dm-devel@xxxxxxxxxx
Loading dm-log.ko module
Loading dm-mirror.ko module
Loading dm-zero.ko module
Loading dm-snapshot.ko module
Loading dm-mem-cache.ko module
Loading dm-region_hash.ko module
Loading dm-message.ko module
Loading dm-raid45.ko module
device-mapper: dm-raid45: initialized v0.2594l
Loading xennet.ko module
netfront: Initialising virtual ethernet driver.
Waiting for driver initialization.
Scanning and configuring dmraid supported devices
Scanning logical volumes
  Reading all physical volumes.  This may take a while...
Activating logical volumes
  Volume group "vg0" not found
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!

This same same configuration I was using for all of my DomUs with XEN 3.4.2 and the same boot messages showed but the DomU started fine.

If someone needs to see the way I customized my .config file for the kernel I can put it in pastebin, here it is http://pastebin.com/LREstQvY

I'll keep you and the list updated on the progress I made but I'm quite stuck here, so I really need to find myself a solution

Thanks for the help.

---
David
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users