This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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

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

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-

And the command you suggested:

[root@vm linux-2.6-xen]# zcat /boot/initrd- | cpio -it | grep xen
15665 blocks

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


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

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

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

At some point in time did you install this 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).

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?

Xen-users mailing list