RE: [Xen-cim] Problems creating an image for Xen hypervisor

["Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>]

If you are fine with a SLES10 image, then you can try these two options:

1. Follow the Xen user documentation for creating a file backed VBD and
copy the dom0 files into VBD as described here.
http://www.cl.cam.ac.uk/Research/SRG/netos/xen/readmes-2.0/user/user.htm
l#SECTION02520000000000000000

2. Make a LVM backed VBD. Mount the LVM logical volume in local mount
point (ex. /mnt/tmp). Then use SLES's "Install into directory" tool and
setup a base install in /mnt/tmp. You can then use the LVM logical
volume as the disk for the DomU. This has worked for me in the past with
SLES9 SP3. I have not tried this with SLES10 but it should work in
theory :-) 

Once you have the image running, you can try using SLES's "yast lan"
tool within the DomU console to setup a dummy Ethernet connection and
that should get your network up and running.

Hope this helps.
Aravindh Puthiyaparambil 
Xen Development Team
Tredyffrin E240 
E-Mail:  aravindh.puthiyaparambil@xxxxxxxxxx

> -----Original Message-----
> From: xen-cim-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-cim-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of John Marberg
> Sent: Tuesday, May 16, 2006 8:00 AM
> To: xen-cim@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-cim] Problems creating an image for Xen hypervisor
> 
> 
> Hello,
> 
> The VSM/CIM team is experiencing difficulties creating a Linux image
to be
> installed on a Xen hypervisor. Gareth suggested that we post this note
to
> the distribution. We'd appreciate any feedback on the issues described
> below.
> 
> 1. Testing:
> 
> We have not been able to create a functional image for Xen in our
> environment.  We have tried SLES tools but have not been able to
properly
> finish the image creation phase.  We've also tried using a pre-built
image
> from the Web (jailtime.org); the image we chose works perfectly when
we
> try
> it on a RHEL based hypervisor, whereas when we try it on the SLES
> hypervisor we cannot properly configure the network. That is, we are
able
> to boot the image and connect to it with the console, but we cannot
get it
> to communicate over the network. This means that until we solve this
we
> will not be able to test anything that relies on collecting
information
> from the guest (e.g., get guest OS).  In short, in our lab we have not
> been
> able to get any working image on a SLES10 based hypervisor.
> 
> 2. Delivery to customers:
> 
> The issue of how to help VSM users create functional virtual systems
on
> Xen
> is still open. We have several people working on possible approaches
to
> deal with this. However, all the suggestions made at our last meeting
on
> this issue (May 4) assume there is a straightforward way to create a
> working image on SLES10. So far, we have not been able to validate
this
> assumption.
> 
> Thanks,
> 
> John Marberg
> 
> Storage and Systems Technology, IBM Haifa Labs,  Haifa 31905, Israel
> Tel: +972-4-829-6244  Fax +972-4-829-6112  marberg@xxxxxxxxxx
> 
> 
> _______________________________________________
> Xen-cim mailing list
> Xen-cim@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-cim

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