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

[David Gonzalez Herrera <dgonzalezh@xxxxxxxxx>]

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.

---
David Gonzalez H.
DGHVoIP - OPEN SOURCE TELEPHONY SOLUTIONS
Phone Bogotá: +(57-1)289-1168
Phone Medellin: +(57-4)247-0985
Mobile: +(57)315-838-8326
MSN: david@xxxxxxxxxxxxxxxx
Skype: davidgonzalezh
WEB: http://www.dghvoip.com/
Proud Linux User #294661

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

On 10/25/2010 07:51 PM, David Gonzalez Herrera wrote:

Hi Richie,

Well no LVM on the DomU, kernel just trying to look for vg0 which is present on Dom0 but not DomU, tried omitting the lvm modules from being added to initrd image but it still tries to load a non-existent vg.

Also I wanted to point out that I'm creating my initrd.img from my running Dom0 kernel which is working good but when I try to boot a DomU with it and the custom initrd.img I get the mentioned error.

Thank you for your quick replies guys.

---

I looked at your output and don't see indication, just before the mount root attempt, that there is a drive available?  For example on my domU boot under a Xenified kernel i see "[    1.236643] blkfront: xvda: barriers enabled" ahead of the root mount.  I would think you should see some indication that a drive was detected.  Do you think it worth checking your initrd image?  Something like "zcat /boot/initrd.img-$(uname -r) | cpio -it | grep xen"

Otherwise nothing else is coming to mind.

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