search for: 3d6bf00

...2v/virt-v2v.pl | 29 ++++++---- v2v/virt-v2v.xml | 62 +++++++++++++++++++++++ 6 files changed, 169 insertions(+), 113 deletions(-) delete mode 100644 v2v/virt-v2v.conf create mode 100644 v2v/virt-v2v.xml diff --git a/MANIFEST b/MANIFEST index 3d6bf00..2513714 100644 --- a/MANIFEST +++ b/MANIFEST @@ -35,6 +35,6 @@ t/003-syntax.t t/004-ExecHelper.t TODO v2v/run-v2v-locally -v2v/virt-v2v.conf +v2v/virt-v2v.xml v2v/virt-v2v.conf.pod v2v/virt-v2v.pl diff --git a/lib/Sys/VirtV2V/Connection/LibVirtXML.pm b/lib/Sys/VirtV2V/Connection/LibVirtXML.pm...

The following patches are where I'm currently at with ESX support. I can now import a domain from ESX along with its storage. Note that I'm not yet doing any conversion. In fact, I've never even tested past the import stage (I just had an exit in there). The meat is really in the 4th patch. The rename of MetadataReader->Connection was because the Connection is now really providing

With this patchset I have successfully[1] imported a RHEL 5 guest directly from ESX with the following command line: virt-v2v -ic 'esx://yellow.marston/?no_verify=1' -op transfer RHEL5-64 Login details are stored in ~/.netrc Note that this is the only guest I've tested against. I haven't for example, checked that I haven't broken Xen imports. Matt [1] With the exception of