On Wed, Jul 16, 2008 at 1:10 PM, jd <[EMAIL PROTECTED]> wrote:
> Hi Brett,
> Here are the steps.. :
>  -- Do a create like on Linux_CD_Install image in the image store.
>  -- Give a name CentOS_5_2
>  -- Edit CentOS_5_2
>   - Select the disk that is pointing to /dev/cdrom
>   - click on properties.
>   - In the dialog that pops up, change from Physical disk to File/VBD
>   - change /dev/cdrom to full path of the iSO
>   - press ok.
>  -- Provision the image :)
> This should work, but let us know if you run in to problems
> /Jd

Apologies for the long delay in replying....

I must be missing something basic about ConVirt.

After struggling with ConVirt I decided to use the built in tools in
CentOS 5.2, virt-manager, virt-clone and virt-install and found their
use to be straight forward and easy to understand and use.  Once I
built a basic CentOS 5.2 guest, it was easy to clone, make unique
guests and put into production.  Once I found I could put a soft-link
in the /etc/xen/auto directory to guests that I want booted with the
host, I was able to put a couple of guests into production.

What issues/problems is ConVirt trying to address that are not covered
by Virtual Machine Manager (www.virt-manager.org) tools built into

Thank you,


This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
XenMan-Users mailing list

Reply via email to