WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

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

To: "Fajar A. Nugraha" <list@xxxxxxxxx>
Subject: Re: [Xen-users] Xen domU cannot boot via PV-GRUB
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
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=30vVdfpR6dgpiyfg8E7e++/IKZKE0B3pEFp0Ql18kUM=; b=DH7yFBctp53Ym4wFIVxlf8O1dRaQ1WKeqsDYEsbi3jYzuX95gOnytc0BRht/Y0iG/n Gx4GM+3f93LONNPpwpOjVpfN0O45JYnqnKQuEI4V+sRbn+ucJlKSukE0mljuMDDSj192 HU4jQzoAtoQJV+lnU4Nn1dkuxkw6+PrZnB7eM=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTikn8f8kAPXnuzBSoqnonYReBcURt2iQHONM0=ew@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTinCYYnfeux+uQUX-51mN4di4vMfD5ibdBE-LBm+@xxxxxxxxxxxxxx> <AANLkTikx1vs8gbX-TGARiWQeYgh7A57OWK3BRX-de978@xxxxxxxxxxxxxx> <AANLkTi=kG2Ms2dBV1RCggLGAMWE-dR0uihpzYnRCukxa@xxxxxxxxxxxxxx> <AANLkTikACkH3q6Zt-RcSp2iW2tqRUaYxSeV49J7pcBQb@xxxxxxxxxxxxxx> <AANLkTi=R3kGV9y=h=76XjSXsSSiroLP-m5+7VUd23WaC@xxxxxxxxxxxxxx> <AANLkTikn8f8kAPXnuzBSoqnonYReBcURt2iQHONM0=ew@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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
/boot

# 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-2.6.34.7-56.40.i686
CONFIG_XEN=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=80
CONFIG_XEN_SAVE_RESTORE=y
CONFIG_XEN_DEBUG_FS=y
CONFIG_XEN_BLKDEV_FRONTEND=m
# CONFIG_NETXEN_NIC is not set
CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_HVC_XEN=y
# Xen driver support
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=m
CONFIG_XENFS=m
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_XEN_SYS_HYPERVISOR=y

# 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.

Regards,

GNUbie

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users