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

Re: [Xen-users] Target filesystem doesn't have requested /sbin/init.


  • To: xen-users@xxxxxxxxxxxxx
  • From: Alexandre Kouznetsov <alk@xxxxxxxxxx>
  • Date: Mon, 23 Jul 2012 12:24:52 -0500
  • Delivery-date: Mon, 23 Jul 2012 17:26:28 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>

Hello.

Mount your VM6.img as loop device within Dom0, check if it is consistent and /sbin/init is there.

Also, within BusyBox you can check what is mounted as "/" and if it's readable.


El 23/07/12 05:50, jaeyong yoo escribió:
Oh, and by the way, the guest image does not have bootloader and could
that be a problem?
Should not. Xen guest VM without kernel and/or bootloader is a normal case. Although, usually you wish to install the same kernel image (via your guest's regular package managing system), as on your Dom0, in order to have the right /lib/modules.

Also, how can I install a bootloader to the guest image?
Normally you don't install bootloader in a guest VM, unless it's HVM (your is PV).

It is possible to boot the guest VM using kernel stored in guest's filesystem, but the bootloader will not reside within guest image. Instead, in case of Xen, you use a small program called pygrub within Dom0. It reads the image, extract the config, the kernel and initrd, then boot them. Check pygrub's documentation, usually it works fine.

On the low level, the booting process is pretty much the same as if you were using kernel and initrd from Dom0 filesystem. The difference is that you don't actually have the needed kernel image in Dom0, it's extracted on the fly from DomU's image just before booting.

Greetings.

--
Alexandre Kouznetsov

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users


 


Rackspace

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