On Fri, Jan 29, 2010 at 06:05:10PM +0000, Matthew Booth wrote:
This change adds the ability to import a guest and its storage from VMware's ESX server using the LibVirt connection.
An example command line:
virt-v2v -ic 'esx://yellow.marston/?no_verify=1' -op transfer RHEL5-64
This will import the guest RHEL5-64 from esx server yellow.marston, copying its storage to a local pool called transfer.
Sys::VirtV2V::Connection is refactored to be a superclass. Subclasses are now created explicitly by virt-v2v.pl rather than using a generic instantiate mechanism.
Sys::VirtV2V::Connection::LibVirt knows explicitly about ESX, and will use the new Sys::VirtV2V::Transfer::ESX to fetch its storage.
virt-v2v.pl is updated to reflect the other changes.
I didn't look at this in great detail, but some quick comments: - get_guest_devices function has disappeared. I didn't quite get why. - get_volume looks complicated. I wonder how stable those ESX paths are and whether there are configurations which have other paths (however it does seem correct for my ESX 4 server). Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into Xen guests. http://et.redhat.com/~rjones/virt-p2v