On Fri, Jan 14, 2011 at 12:03 AM, GNUbie <gnubie@xxxxxxxxx> wrote:
> Hello all,
>
> Please advice on how I can move forward from this bootup problem. I
> already tried changing the value of the "root=" option to /dev/sda2
> and /dev/xvda2 with no luck. I also tried to re-generate a new initrd
> adding the options of "--with xennet --with xenblk" but still with no
> luck.
> title GNU/Linux (2.6.34.7-56.40.i686)
> root (hd0,0)
> kernel /boot/vmlinuz-2.6.34.7-56.40.i686 root=LABEL=/ console=hvc0
> initrd /boot/initrd-2.6.34.7-56.40.i686.img
I assume you ACTUALLY have the correct partition/LV with LABEL=/ on
domU's disk image?
> Loading xen-blkfront.ko module
> [ 0.456365] blkfront device/vbd/2050 num-ring-pages 1 nr_ents 32.
> [ 0.460302] blkfront device/vbd/2064 num-ring-pages 1 nr_ents 32.
> [ 0.484444] blkfront device/vbd/2051 num-ring-pages 1 nr_ents 32.
> [ 0.487167] blkfront: regular deviceid=0x802 major,minor=8,2,
> assuming parts/disk=16
> [ 0.488610] blkfront: regular deviceid=0x810 major,minor=8,16,
> assuming parts/disk=16
> [ 0.488850] xvdb: unknown partition table
> [ 0.559870] blkfront: regular deviceid=0x803 major,minor=8,3,
> assuming parts/disk=16
You should see the disks and detected partition tables on boot. Your
log only xvdb is detected with "unknown partition table", which is
weird. Does the disk image actually HAVE partition on it, or do you
create a filesystem directly on that image? What does your domU config
file looks like? What does "fdisk -l /path/to/your/disk-image" look
like?
--
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home