Hi Mohammed,

We struggled using virt-v2v directly with OpenStack. Our approach was using ovftool to export the VM as OVA and then create a qcow2 image that we can import in OpenStack. So many manual steps involved.

So I tested your tool aganst vsphere 7.x vcenter. But I just can't manage to get it working.

It keeps complaining about the path of the source VM. I can use the following just fine with virt-v2v:

virt-v2v -v -x --password-file pass.txt -ic vpx://user123@vcenter.somedomain.local/GE%Office%20One/Projects/esx01.somedomain.local?no_verify=1 test-vm-01

Using the same in your tool:

docker run -it --rm --privileged   \

-v /dev:/dev   \

-v /usr/lib64/vmware-vix-disklib/:/usr/lib64/vmware-vix-disklib:ro   \

--env-file <(env | grep OS_)   registry.atmosphere.dev/library/migratekit:latest   migrate   \

--vmware-endpoint vcenter.somedomain.local   \

--vmware-username user123   \

--vmware-password XXXXXX   \

--vmware-path /GE%Office%20One/Projects/esx01.somedomain.local/test-vm-01

Results in:

Error: vm '/GE%Office%20One/Projects/esx01.somedomain.local/test-vm-01' not found

I tried many different variants of the path none has worked.

Is there a way to lookup the path of a VM?

I can also use:

virsh -c 'vpx://user123@vcenter.somedomain.local/GE%Office%20One/Projects/esx01.somedomain.local?no_verify=1 list --all

which shows me all VMs running on that particular ESXi host.

Best Regards,

Oliver