Re: Xen Dom U kernel

[Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>]

On Thu, Apr 22, 2010 at 02:35:04PM -0700, kishore kumar wrote:
> OK.
> what could be the reason for my domU creation is failing here?

Hmm, Are you using a RHEL5/CentOS based userspace to build the initrd image?

If you are please take a look at this:
http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher

> 
> Mounting proc filesystem
> Mounting sysfs filesystem
> Creating /dev
> Creating initial device nodes
> Setting up hotplug.
> Creating block device nodes.
> Scanning and configuring dmraid supported devices
> Scanning logical volumes
> Reading all physical volumes. This may take a while...
> Found volume group "VolGroup01" using metadata type lvm2
> lvm used greatest stack depth: 4912 bytes left
> Activating logical volumes
> 2 logical volume(s) in volume group "VolGroup01" now active
> Trying to resume from /dev/VolGroup01/LogVol01
> No suspend signature on swap, not resuming.
> 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.33 #3
> Call Trace:
> [<ffffffff810513fa>] panic+0xa5/0x171
> [<ffffffff81006891>] ? xen_force_evtchn_callback+0xd/0xf
> [<ffffffff8148ce94>] ? _raw_write_unlock_irq+0x30/0x3b
> [<ffffffff8107ecb8>] ? trace_hardirqs_on_caller+0x110/0x134
> [<ffffffff8107ece9>] ? trace_hardirqs_on+0xd/0xf
> [<ffffffff8148ce9b>] ? _raw_write_unlock_irq+0x37/0x3b
> [<ffffffff81054b0c>] do_exit+0x7c/0x6f5
> [<ffffffff8107189f>] ? up_read+0x2b/0x2f
> [<ffffffff81055221>] sys_exit_group+0x0/0x1b
> [<ffffffff81055238>] sys_exit_group+0x17/0x1b
> [<ffffffff81009cf2>] system_call_fastpath+0x16/0x1b