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

RE: [Xen-users] domu under sles10

  • To: "Janko Harej" <janko.harej@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
  • Date: Thu, 12 Apr 2007 13:01:13 +0200
  • Delivery-date: Thu, 12 Apr 2007 04:00:30 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: Acd87qDuWsuV6exbTFW/G8DXxrsvagAAZUeA
  • Thread-topic: [Xen-users] domu under sles10


> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Janko Harej
> Sent: 12 April 2007 11:37
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] domu under sles10
> Hi,
> I'm trying to build non sles10 domU under sles10 dom0. I've downloaded
> centos and debian images from www.jailtime.org fixed the config file
> and try to start domU.
> After creating domU from images I get
> Kernel panic - not syncing: VFS: Unable to mount root fs on 
> unknown-block(0,0)
> I'm running without problems two sles10 domU machines.
> After using google allot :-) I found something about creating initrd -
> how do I do that for debian or centos?

It doesn't make any difference whether you use debian, centos or some
other OS. You need to create the initrd in the host-machine, using the
xen-kernel that you've got there. So, if you're using sles, it should be
something like this:

mkinitrd somewhere/initrd-$ver-xenU $ver-xen --with=blkfront 
[$ver would be something like, matching the version of your
xenified linux kernel]. 

The location of "somwhere" could be /boot, but doesn't have to be. 

> Comparing sles10 domU and centos/debian xen image files I see that in
> debian/centos boot directory is empty but not in sles10

You don't need anyting in the guest's boot directory, as the kernel and
initrd are loaded from Dom0's file-system. 
Whether you still have something in /boot in the guest obviously depends
the way it was installed and if the install process decided to stuff
something in /boot for some reason (e.g. it ALWAYS writes some files to
/boot, whether it's necessary or not). 

> Please help me out
> Thank you all in advance
> -- 
> Janko Harej
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

Xen-users mailing list



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