Re: [Users] Making v2v easier?

FWIW, importing directly from an ESX server still works: virt-v2v-host: - RHEL/CentOS 6.5 physical host ( virt-v2v uses qemu-kvm = extra++ slow on a VM) - Packages: virt-v2v-0.9.1-5.el6_5.x86_64 libguestfs-winsupport-1.0-7.el6.x86_64 libguestfs-tools-c-1.20.11-2.el6.x86_64 libguestfs-tools-1.20.11-2.el6.x86_64 libguestfs-1.20.11-2.el6.x86_64 virtio-win-1.6.7-2.el6.noarch ( RHEL only? ) - network acces to: oVirt export domain (NFS) esx host(s) to import from (HTTPS) - virt-v2v has to run as root to mount the oVirt NFS export domain - Edit ~/.netrc and add a line for the esx host(s) to import from (change the <> parts): machine <esx.host.fqdn> login <esxuser> password <esxpassword> - Fix permissions on netrc file: chmod 600 ~/.netrc - Run virt-v2v ( again: change the <> parts, ?no_verify=1 is needed when esx uses self signed certs) LIBGUESTFS_DEBUG=1 virt-v2v -ic esx://<esx.host.fqdn>/?no_verify=1 -o rhev -os <rhev.export.domain.host:/var/exports/export_domain> --network <target_network_name> <vmname> Conversion can take quite some time after the disk copy, especially when virt-v2v removes the vmware tools. Running on a physical host (or using nested virtualization) helps. On Mon, Jan 20, 2014 at 8:59 AM, Sander Grendelman <sander(a)grendelman.com&gt; wrote: