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

[Xen-users] Populating a guest image


  • To: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Ferreira, N. L. (Nuno)" <n.l.ferreira@xxxxx>
  • Date: Wed, 21 Jan 2009 10:27:13 +0100
  • Delivery-date: Wed, 21 Jan 2009 01:28:11 -0800
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi *

I'm training a bit on the subject "Populating a guest image".
My goal is to build a guest image of Scientific Linux (SL) and clone it whenever necessary. I'm trying both xen-strap (http://www.gridpp.ac.uk/wiki/Xen-strap) and virt-install utilities to install into a LVM (wanted a non-graphical tool) .

Xen-strap installs very well SL creating separate swap and root partitions, which is cool for later backup. This utility creates the domU guest kernel on dom0. Thus, the guest configuration files reads kernel and ramdisk from dom0.

virt-install does the same good job, but the guest kernel is installed on the domU boot. Guest configuration file uses in this case the pygrub bootloader.

My questions are:

1 - Virt-install creates self-contained guests (kernel inside domU) whereas xen-strap not.
Which one of these is easier to migrate to other similar physical machines?

2 - Is it possible to convert a domU which reads the kernel from dom0 to a self-contained guest, like the one created by virt-install? If yes, how?


Cheers,
Nuno


_______________________________________________
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®.