[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 13:09:43 +0800
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 13 Jan 2011 21:10:45 -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=J7aPLq1YcaNitYFUdN/Bo5+dSRPjD39CsF64dWm3QOLuJgtRJigyXfo9H6HzC3yuVu RPFPHweNgnWZSsXYtqBf7DVVo3O+766jLmW1aPUJzGuzDEe4ieKyYv7W5CsMtvHwEMQ0 YEL/P/sWJdqk95T1rLoX/8XCifA6VxRLLJfu8=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello Fajar,

On Fri, Jan 14, 2011 at 12:03 PM, Fajar A. Nugraha <list@xxxxxxxxx> wrote:
> How do you know it's actually mapped as sda?

Only in my /etc/fstab for that domU.

> You need to get it. Even if it's only to get disk mappings (whatever
> format it's in, whether python or xml)
> It's possible that the domU config maps the disk as xvdb (for
> example). Then all attempts to use xvda2 or sda2 will be useless.

I'm afraid how to answer this question. Actually, I am trying to boot
my domU at the AWS EC2 environment which is now an EBS volume. The
domU came from an S3 and I made a copy to the EBS volume. I apologize
in advance if I am in the wrong mailing list.

> Good,
> Try checking to see if the label actually exists. Run
> e2label /dev/sdk1
> e2label /dev/sdk2

# e2label /dev/sdk1

# e2label /dev/sdk2

> At this point you NEED to know what the domU detects the disk as. domU
> config file might help.


> Also, disable "quiet" on grub config line (if it's there). During boot
> of Ubuntu Lucid in my setup, it shows these lines:

I don't have it on my GRUB config.

> In particular, you need to look at these lines
> [    0.205765] XENBUS: Device with no driver: device/vbd/51712 =>
> "51712" is block device id for xvda
> [    0.774316] blkfront: xvda: barriers enabled
> [    0.775478]  xvda: xvda1 xvda2 xvda3 => this shows that
> xen_blkfront driver handles the block device xvda, and it correctly
> detects three partitions.
> Your problem might be something as simple as not having xen block
> device frontend installed, either built in or as a module.

I'm wondering why it keeps on expecting the xvd* mapping except that
if the domU config is really expecting for it.

Do I need to rebuild the kernel and initrd?

Below is the kernel config file that comes with the kernel that I'm
using for this domU:

# grep -i xen config-
# CONFIG_NETXEN_NIC is not set
# Xen driver support

# cat /etc/modprobe.conf
alias eth0 xennet
alias scsi_hostadapter xenblk
alias ipv6 off
alias net-pf-10 off
options ipv6 disable=1

Thank you in advance.



Xen-users mailing list



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