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

Re: [Xen-users] /dev/sda2 does not exist. Dropping to a shell! (Dom0: Ubuntu 10.10, DomU: Ubuntu 10.10)


  • To: "Fajar A. Nugraha" <list@xxxxxxxxx>
  • From: Hitesh Khandelwal <hitesh.iitk@xxxxxxxxx>
  • Date: Thu, 10 Mar 2011 19:35:55 -0500
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 10 Mar 2011 16:36:46 -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; b=bbavZ6NlRx6W25cRnJ2+9wRwjCk+kLHCBgfj1A2b039JF9sgQv2HmXii5Bi5W/j/XO mqu50qaNvubOlCjQbzVsZJufQMvdIoXNgTDLvkamD812srbf2uXoiXR+TQFzbm9H72bB 1A+dIC4xbO0LpGQhfVRIYJwfigcs0wd8/1D1M=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Replied inline:

On Wed, Mar 9, 2011 at 9:33 PM, Fajar A. Nugraha <list@xxxxxxxxx> wrote:
On Thu, Mar 10, 2011 at 7:34 AM, Hitesh Khandelwal
<hitesh.iitk@xxxxxxxxx> wrote:
> root        = '/dev/sda2 ro'

For starters, change that to /dev/xvda2

> disk        = [
>
>  'file:/home/hkhande/xen-image/domains/cloud-vm06/disk.img,sda2,w',

... and here as well. Though newer kernel version will silently change
sd* to xvd*, sometimes the mapping seems inconsistent (sda -> xvde)
 
As I already mentioned in my earlier post, I tried xvda as well. This is the error I received:

Loading, please wait...
mount: mounting none on /dev failed: No such device
W: devtmpfs not available, falling back to tmpfs for /dev
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
[    5.572796] kjournald starting.  Commit interval 5 seconds
[    5.572824] EXT3-fs: mounted filesystem with writeback data mode.
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
init: ureadahead main process (803) terminated with status 5
 


> Everything works fine with pygrub, but I need to use Dom0 xenified kernel
> only.

Why?

If you want to do it anyway, start with copying domU's kernel and
initrd to dom0, and use that. Using dom0 kernel&initrd for domU might
require extra effort, which you might not know how to do yet ...
 
I meant, I want to use the same xen kernel I compiled for running Dom0. because this patch: http://lists.xensource.com/archives/html/xen-devel/2010-10/msg01261.html
is still absent in ubuntu stock kernels. That patch is part of xen kernel I compiled for Dom0, hence want to use the same kernel for DomU as well. Can you please elaborate how to use Dom0 kernel and initramfs for booting DomU?
 

> I also modified /etc/initramfs-tools/modules in Dom0 to include
> scsi_mod, sd_mod, blkbk modules, followed by update-initramfs.

... as shown here.

blkbk is xen block backend device driver, needed by dom0 but not
needed by domU. domU needs xen_blkfront and xen_netfront.

--
Fajar

Thanks for your reply.
Hitesh
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

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