There were some definite bugs which I hopefully corrected with the
commit from this morning.  Be sure to use the latest code from trunk.
Also, you'll need to run again.

Regarding KVM installation/configuration, I have mainly been working
off of Fedora 16.  The version of KVM included with Fedora 16 seems
more stable than Red Hat or CentOS 6.x.  The code should work under
these OS's but automatic conversion of existing ESXi images to
KVM-compatible qcow2 images probably won't work.  The version of
qemu-img included with Fedora 16 is able to do the conversion
correctly.  The versions included with Red Had and CentOS do not.

Regarding image conversion, you should be able load an existing vmdk
ESXi image on KVM if the image resides in the repository path.  The
code should copy it to the datastore in the format specified for the
image type in the VM profile for your KVM host.  Be sure to set this
to qcow2.

I fixed some bugs which caused base image creation to fail in the
commit this morning.  Please try this out.

I started the following page which describes which components to
install and how to configure networking and storage:


On Tue, Jun 19, 2012 at 5:02 PM, Dmitri Chebotarov <> wrote:
> Hi
> Has anyone tried Libvirt in 2.3 RC3?
> I've updated VCL 2.2.1 to VCL 2.3 and cannot get Libvirt working.
> I've made some adjustments and able to successfully capture an image, but
> cannot make reservation based on the image.
> I'm using CentOS 6.2 with KVM as VM host (yum groupinstall  Virtualization
> 'Virtualization Client' 'Virtualization Platform' 'Virtualization Tools').
> If Libvirt is working for you, could you please share your configuration
> (ie. VM host version and packages, VCL computer configuration, etc) ?
> --
> Thank you,
> Dmitri Chebotarov
> Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging
> 223 Aquia Building, Ffx, MSN: 1B5
> Phone: (703) 993-6175
> Fax: (703) 993-3404

Reply via email to