From mboxrd@z Thu Jan 1 00:00:00 1970 From: kishore kumar Subject: Re: Xen Dom U kernel Date: Mon, 19 Apr 2010 16:28:03 -0700 Message-ID: References: <4BC60244.5070300@goop.org> <20100417122221.GI1878@reaktio.net> <20100419192755.GT1878@reaktio.net> <4BCCCB40.9080803@triad.rr.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0482639203==" Return-path: In-Reply-To: <4BCCCB40.9080803@triad.rr.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: listmail Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============0482639203== Content-Type: multipart/alternative; boundary=001636284a52ffb3f804849f4f31 --001636284a52ffb3f804849f4f31 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Could you please let me know where this break=3Dpremount option should be added? What is the location of the xen block devices. I want to load this module and check giving the above option and see if it works for me. Thank You. On Mon, Apr 19, 2010 at 2:29 PM, listmail wrote: > I don't have any issues using my dom0 kernel & initrd to boot pv domU, > config has CONFIG_XEN_BLKDEV_FRONTEND=3Dm as well. > > However, thats when passing through file based images & LVM from the dom0 > to the domU. Is this more of an issue when LVM is implemented on the dom= U > itself??? That's what I am seeing here. Should he be adding a > break=3Dpremount option to initrd and checking visibility of the LVM root= from > busybox? > > > Pasi K=E4rkk=E4inen wrote: > >> On Mon, Apr 19, 2010 at 12:08:35PM -0700, kishore kumar wrote: >> >> >>> 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) >>> >>> >>> >> >> You cannot use the dom0 initrd/ramdisk for domU! >> >> dom0 initrd contains drivers for the physical hardware, while in the dom= U >> initrd >> you need to have drivers for the _virtual_ hardware! >> >> In the log below root was not found because the drivers for the xen bloc= k >> devices >> are not loaded. >> >> -- Pasi >> >> >> >> >>> 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 <[1]pasik@iki.fi= > >>> 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 line= s >>> > >>> > 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 >>> available >>> > 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 >>> >>> References >>> >>> Visible links >>> 1. mailto:pasik@iki.fi >>> >>> >> >> _______________________________________________ >> Xen-devel mailing list >> >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >> >> > > --001636284a52ffb3f804849f4f31 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
=A0
Could you please let me know where this break=3Dpremount option should= be added?
What is the location of the xen block devices. I want to load this mod= ule and check giving the above option and see if it works for me.=A0
Thank You.
=A0
On Mon, Apr 19, 2010 at 2:29 PM, listmail <listmail@triad.rr.= com> wrote:
I don't have any issues usin= g my dom0 kernel & initrd to boot pv domU, =A0config has CONFIG_XEN_BLK= DEV_FRONTEND=3Dm as well.

However, thats when passing through file based images & LVM from th= e dom0 to the domU. =A0Is this more of an issue when LVM is implemented on = the domU itself??? =A0That's what I am seeing here. =A0Should he be add= ing a break=3Dpremount option to initrd and checking visibility of the LVM = root from busybox?


Pasi K=E4rkk=E4inen wrote:
On Mon, Apr 19, 2010 at 12:08:35PM -0700, kishore kumar w= rote:
=A0
=A0 I included
=A0 kernel =3D= "/boot/vmlinuz-2.6.32.10"
=A0 ramdisk =3D "/boot/initrd-= 2.6.32.10.img" (This is the same as my Dom 0. =A0As
=A0 I am trying to boot the same Dom 0 as my Dom U without any changes)
=
=A0 =A0

You cannot use the dom0 initrd/ramdisk for = domU!

dom0 initrd contains drivers for the physical hardware, while = in the domU initrd
you need to have drivers for the _virtual_ hardware!

In the log belo= w root was not found because the drivers for the xen block devices
are n= ot loaded.

-- Pasi


=A0
=A0 disk =3D ['phy:sda2,sda2= ,w']
=A0 root=3D "/dev/VolGroup01/LogVol00 ro"

=A0 = =A0 I see my .config and I have
=A0 CONFIG_XEN_BLKDEV_FRONTEND=3Dm
=A0 CONFIG_XEN_BLKDEV_BACKEND=3Dy
= =A0 CONFIG_XEN_BACKEND=3Dy

=A0 Below is the output pasted. =A0Any he= lp please on what is going wrong here?

=A0 XENBUS: Device with no dr= iver: device/vbd/2050

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

=A0 XENBUS: Devi= ce with no driver: device/console/0

=A0 Magic number: 1:252:3141
=
=A0 drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

=A0 = Initalizing network drop monitor service

=A0 Freeing unused kernel memory: 3392k freed

=A0 Write protecti= ng the kernel read-only data: 6912k

=A0 Red Hat nash version 5.1.19.= 6 starting

=A0 Mounting proc filesystem

=A0 Mounting sysfs fi= lesystem

=A0 Creating /dev

=A0 Creating initial device nodes

=A0 S= etting up hotplug.

=A0 Creating block device nodes.

=A0 Loadi= ng ehci-hcd.ko module

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

=A0 insmod used greatest stack depth: 5712 bytes left

=A0 Loadin= g ssb.ko module

=A0 Loading ohci-hcd.ko module

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

=A0 Loading uhc= i-hcd.ko module

=A0 uhci_hcd: USB Universal Host Controller Interface driver

=A0= Scanning and configuring dmraid supported devices

=A0 Scanning logi= cal volumes

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

=A0 lvm used greatest stack depth: 5328 bytes left

=A0 Activatin= g logical volumes

=A0 Volume group "VolGroup01" not found<= br>
=A0 Trying to resume from /dev/VolGroup01/LogVol01

=A0 Unable= to access resume device (/dev/VolGroup01/LogVol01)

=A0 Creating root device.

=A0 Mounting root filesystem.

= =A0 mount: could not find filesystem '/dev/root'

=A0 Setting= up other filesystems.

=A0 Setting up new root fs

=A0 setupro= ot: moving /dev failed: No such file or directory

=A0 no fstab.sys, mounting internal defaults

=A0 setuproot: erro= r mounting /proc: No such file or directory

=A0 setuproot: error mou= nting /sys: No such file or directory

=A0 Switching to new root and = running init.

=A0 unmounting old /dev

=A0 unmounting old /proc

=A0 unmo= unting old /sys

=A0 switchroot: mount failed: No such file or direct= ory

=A0 init used greatest stack depth: 4888 bytes left

=A0 K= ernel panic - not syncing: Attempted to kill init!

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

=A0 Call Trace:<= br>
=A0 [<ffffffff8105b747>] panic+0xa5/0x167

=A0 [<ffff= ffff8100ed81>] ? xen_force_evtchn_callback+0xd/0xf

=A0 [<fffff= fff81475d48>] ? _write_unlock_irq+0x30/0x3c

=A0 [<ffffffff8108c9f4>] ? trace_hardirqs_on_caller+0x110/0x134
=A0 [<ffffffff8108ca25>] ? trace_hardirqs_on+0xd/0xf

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

=A0 [<f= fffffff8105efa7>] do_exit+0x7e/0x701

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

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

=A0 [<ffffffff8101= 2d72>] system_call_fastpath+0x16/0x1b

=A0 On Sat, Apr 17, 2010 at= 5:22 AM, Pasi K=E4rkk=E4inen <[1]pasik@iki.fi> wrote:

=A0 =A0 On Fri, Apr 16, 2010 at 03:24:53PM -0700, kishore kumar wrote:<= br>=A0 =A0 > =A0 =A0I am using my Dom 0 kernel to boot as my Dom U.
= =A0 =A0 > =A0 =A0I edited /etc/xen/xmexample1 file and modified only bel= ow lines
=A0 =A0 >
=A0 =A0 > =A0 =A0kernel=3D"/boot/vmlinux-2.6.32.10"
=A0 =A0= > =A0 =A0memory=3D512
=A0 =A0 > =A0 =A0vcpus=3D5
=A0 =A0 > = =A0 =A0root =3D "/dev/VolGroup01/LogVol00 ro"
=A0 =A0 > =A0= =A0Below is the output I pasted after freezing. =A0Not sure what is
=A0 =A0 wrong. =A0Can
=A0 =A0 > =A0 =A0you please help me here??
= =A0 =A0 > =A0 =A0I doubt if I have provided the correct root option?
= =A0 =A0 >

=A0 =A0 I bet that kernel has xen block frontend driver= as a module?

=A0 =A0 You don't seem to have ramdisk/initrd imag= e,
=A0 =A0 so you simply don't have the driver loaded at all
=A0 =A0 to= access the root disk in the guest.

=A0 =A0 You must create an initr= d image that loads the driver module in the
=A0 =A0 guest.
=A0 =A0 &g= t;
=A0 =A0 > =A0 =A0VFS: Cannot open root device "VolGroup01/Log= Vol00" or
=A0 =A0 unknown-block(0,0)
=A0 =A0 >
=A0 =A0 > =A0 =A0Please ap= pend a correct "root=3D" boot option; here are the available
= =A0 =A0 > =A0 =A0partitions:
=A0 =A0 >
=A0 =A0 > =A0 =A0Kern= el panic - not syncing: VFS: Unable to mount root fs on
=A0 =A0 > =A0 =A0unknown-block(0,0)
=A0 =A0 >

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

References
=A0 Visible links
=A0 1. mailto:pasik@iki.f= i
=A0 =A0

__________________________= _____________________
Xen-devel mailing list=20

Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
=A0


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