[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

  • To: "Fajar A. Nugraha" <list@xxxxxxxxx>
  • From: GNUbie <gnubie@xxxxxxxxx>
  • Date: Fri, 14 Jan 2011 08:44:34 +0800
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 13 Jan 2011 16:46:01 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=MzbzR4+Hgn1J6hBtVeYOoUQWscpwwgCOFMA25TZ88CQEDbL2T0fiu4YS8YOinm8mY4 uaLwhLPBDINBEkKe9YLyznZDU+ASwwYySwR0kBllpjtQpzWc6I/iiTjs515gBoeTRR/B NAd6z1dfPisRVaOvvnWDE1BCtxHLCaiFXFVhk=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello Fajar,

On Fri, Jan 14, 2011 at 6:04 AM, Fajar A. Nugraha <list@xxxxxxxxx> wrote:
> I assume you ACTUALLY have the correct partition/LV with LABEL=/ on
> domU's disk image?

Yes. But as I've said, I also tried using /dev/sda2 and /dev/xvda2 but
with no luck.

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

This system (domU) used to be in another dom0 that uses /dev/xvd*
partitions then I dump'ed and restore'd a copy of this system to this
new dom0 that uses /dev/sd* partitions.

I remember that the original partitions of this domU from its original
dom0 were:

 202        1   10240001 xvda1 => /
 202        2  356485632 xvda2 => /data
 202        3     917504 xvda3 => swap

But even from the original dom0, the domU do not have a /dev/xvdb partition.

Going back to your question. I don't remember creating the /dev/xvdb
partition and it doesn't have an /dev/xvdb partition.

Before I restore'd the dump'ed domU to its new place, I fdisk'ed the
volume and created two (2) partitions for the /boot and /. Please take
note that the original domU from the original dom0, I dump'ed the
/dev/xvda1 which contains the entire / partition and when I restore'd
it to the new dom0 for this new domU, I made sure that I mounted the
second partition first which is the / then mounted the first partition
inside the /boot.

Now, I'm not aware if there is any other configuration that checks and
expects this /dev/xvdb partition aside from checking the /etc/fstab
which I already changed as per my original message for this thread.

Please advice. Thank you.



Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.