From mboxrd@z Thu Jan 1 00:00:00 1970 From: kishore kumar Subject: Re: [Xen-devel] Xen Dom U kernel Date: Mon, 19 Apr 2010 12:08:35 -0700 Message-ID: References: <4BC60244.5070300@goop.org> <20100417122221.GI1878@reaktio.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2072615210==" Return-path: In-Reply-To: <20100417122221.GI1878@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: Jeremy Fitzhardinge , xen-devel@lists.xensource.com, xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============2072615210== Content-Type: multipart/alternative; boundary=001485f921f213ff8404849bb037 --001485f921f213ff8404849bb037 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I included kernel =3D "/boot/vmlinuz-2.6.32.10" ramdisk =3D "/boot/initrd-2.6.32.10.img" (This is the same as my Dom 0. As= I am trying to boot the same Dom 0 as my Dom U without any changes) disk =3D ['phy:sda2,sda2,w'] root=3D "/dev/VolGroup01/LogVol00 ro" I see my .config and I have CONFIG_XEN_BLKDEV_FRONTEND=3Dm CONFIG_XEN_BLKDEV_BACKEND=3Dy CONFIG_XEN_BACKEND=3Dy Below is the output pasted. Any help please on what is going wrong here? XENBUS: Device with no driver: device/vbd/2050 XENBUS: Device with no driver: device/vif/0 XENBUS: Device with no driver: device/console/0 Magic number: 1:252:3141 drivers/rtc/hctosys.c: unable to open rtc device (rtc0) Initalizing network drop monitor service Freeing unused kernel memory: 3392k freed Write protecting the kernel read-only data: 6912k Red Hat nash version 5.1.19.6 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading ehci-hcd.ko module ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver insmod used greatest stack depth: 5712 bytes left Loading ssb.ko module Loading ohci-hcd.ko module ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver Loading uhci-hcd.ko module uhci_hcd: USB Universal Host Controller Interface driver Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... lvm used greatest stack depth: 5328 bytes left Activating logical volumes Volume group "VolGroup01" not found Trying to resume from /dev/VolGroup01/LogVol01 Unable to access resume device (/dev/VolGroup01/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 init used greatest stack depth: 4888 bytes left Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.32.10 #2 Call Trace: [] panic+0xa5/0x167 [] ? xen_force_evtchn_callback+0xd/0xf [] ? _write_unlock_irq+0x30/0x3c [] ? trace_hardirqs_on_caller+0x110/0x134 [] ? trace_hardirqs_on+0xd/0xf [] ? _write_unlock_irq+0x37/0x3c [] do_exit+0x7e/0x701 [] sys_exit_group+0x0/0x1b [] sys_exit_group+0x17/0x1b [] system_call_fastpath+0x16/0x1b On Sat, Apr 17, 2010 at 5:22 AM, Pasi K=E4rkk=E4inen wrote: > On Fri, Apr 16, 2010 at 03:24:53PM -0700, kishore kumar wrote: > > I am using my Dom 0 kernel to boot as my Dom U. > > I edited /etc/xen/xmexample1 file and modified only below lines > > > > kernel=3D"/boot/vmlinux-2.6.32.10" > > memory=3D512 > > vcpus=3D5 > > root =3D "/dev/VolGroup01/LogVol00 ro" > > Below is the output I pasted after freezing. Not sure what is wrong= . > Can > > you please help me here?? > > I doubt if I have provided the correct root option? > > > > I bet that kernel has xen block frontend driver as a module? > > You don't seem to have ramdisk/initrd image, > so you simply don't have the driver loaded at all > to access the root disk in the guest. > > You must create an initrd image that loads the driver module in the guest= . > > > > > VFS: Cannot open root device "VolGroup01/LogVol00" or > unknown-block(0,0) > > > > Please append a correct "root=3D" boot option; here are the availabl= e > > partitions: > > > > Kernel panic - not syncing: VFS: Unable to mount root fs on > > unknown-block(0,0) > > > > Root was not found - this is usually because you don't have the xen > blockdev frontend driver loaded. > > -- Pasi > > --001485f921f213ff8404849bb037 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I included
kernel =3D "/boot/vmlinuz-2.6.32.10"
ramdisk =3D "/boot/initrd-2.6.32.10.img" (This is the same a= s my Dom 0.=A0 As I am trying to boot the same Dom 0 as my Dom U without an= y changes)
disk =3D ['phy:sda2,sda2,w']=A0
root=3D "/dev/VolGroup01/LogVol00 ro"
=A0
=A0 I see my .config and I have
CONFIG_XEN_BLKDEV_FRONTEND=3Dm
CONFIG_XEN_BLKDEV_BACKEND=3Dy
CONFIG_XEN_BACKEND=3Dy
=A0
Below is the output pasted.=A0 Any help please on what is going wrong = here?

XENBUS: Device with no driver: device/vbd/2050

XENBUS: Device with no driver: device/vif/0

XENBUS: Device with no driver: device/console/0

Magic number: 1:252:3141

drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

Initalizing network drop monitor service

Freeing unused kernel memory: 3392k freed

Write protecting the kernel read-only data: 6912k

Red Hat nash version 5.1.19.6 starting

Mounting proc filesystem

Mounting sysfs filesystem

Creating /dev

Creating initial device nodes

Setting up hotplug.

Creating block device nodes.

Loading ehci-hcd.ko module

ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

insmod used greatest stack depth: 5712 bytes left

Loading ssb.ko module

Loading ohci-hcd.ko module

ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver

Loading uhci-hcd.ko module

uhci_hcd: USB Universal Host Controller Interface driver

Scanning and configuring dmraid supported devices

Scanning logical volumes

Reading all physical volumes. This may take a while...

lvm used greatest stack depth: 5328 bytes left

Activating logical volumes

Volume group "VolGroup01" not found

Trying to resume from /dev/VolGroup01/LogVol01

Unable to access resume device (/dev/VolGroup01/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

init used greatest stack depth: 4888 bytes left

Kernel panic - not syncing: Attempted to kill init!

Pid: 1, comm: init Not tainted 2.6.32.10 #2

Call Trace:

[<ffffffff8105b747>] panic+0xa5/0x167

[<ffffffff8100ed81>] ? xen_force_evtchn_callback+0xd/0xf

[<ffffffff81475d48>] ? _write_unlock_irq+0x30/0x3c

[<ffffffff8108c9f4>] ? trace_hardirqs_on_caller+0x110/0x134

[<ffffffff8108ca25>] ? trace_hardirqs_on+0xd/0xf

[<ffffffff81475d4f>] ? _write_unlock_irq+0x37/0x3c

[<ffffffff8105efa7>] do_exit+0x7e/0x701

[<ffffffff8105f6c6>] sys_exit_group+0x0/0x1b

[<ffffffff8105f6dd>] sys_exit_group+0x17/0x1b

[<ffffffff81012d72>] system_call_fastpath+0x16/0x1b

On Sat, Apr 17, 2010 at 5:22 AM, Pasi K=E4rkk=E4= inen <pasik@iki.fi= > wrote:
On Fri, Apr 16, 2010 at 03:24:53PM -0700, kishore kumar w= rote:
> =A0 =A0I am using my Dom 0 kernel to boot as my Dom U.
>= ; =A0 =A0I edited /etc/xen/xmexample1 file and modified only below lines>
> =A0 =A0kernel=3D"/boot/vmlinux-2.6.32.10"
> =A0 =A0mem= ory=3D512
> =A0 =A0vcpus=3D5
> =A0 =A0root =3D "/dev/VolGr= oup01/LogVol00 ro"
> =A0 =A0Below is the output I pasted after f= reezing. =A0Not sure what is wrong. =A0Can
> =A0 =A0you please help me here??
> =A0 =A0I doubt if I have prov= ided the correct root option?
>

I bet that kernel has xe= n block frontend driver as a module?

You don't seem to have ramd= isk/initrd image,
so you simply don't have the driver loaded at all
to access the root= disk in the guest.

You must create an initrd image that loads the d= river module in the guest.

>
> =A0 =A0VFS: Cannot open root device &quo= t;VolGroup01/LogVol00" or unknown-block(0,0)
>
> =A0 =A0Pl= ease append a correct "root=3D" boot option; here are the availab= le
> =A0 =A0partitions:
>
> =A0 =A0Kernel panic - not syncing: VFS: Unable to mount root f= s on
> =A0 =A0unknown-block(0,0)
>

Root was not fo= und - this is usually because you don't have the xen blockdev frontend = driver loaded.

-- Pasi


--001485f921f213ff8404849bb037-- --===============2072615210== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users --===============2072615210==--