virt-v2v fails with 404 error on vpx conversion from vmware 7.0.3

[zdeems]

check of the 'path' value against the source_re regex appears to fail, dropping the 'path' value into the super-old mode of adding
"-flat" to the vmdk filename. No such file has existed for quite a few modern versions of vmware.

[rwmjones]

Could you please show the full virt-v2v command, and attach the full output when you use the additional -v -x parameters.

[zdeems]

virt-v2v.log

Specific hostnames etc cleaned up.

[zdeems]

The error is legitimate - there is no vmdk file including the text "-flat" in its name. That is added in vCenter.ml

[rwmjones]

I asked our QE if they have seen this.

You could also try a VDDK conversion which is what we generally use. Requires the proprietary VMware library.

[rwmjones]

We are having trouble reproducing this issue. Can you describe exactly the VMware set up. Was the guest created normally? Are you using vSAN or any other uncommon storage type? Did you move or delete the guest's disk? What steps would we use to reproduce this?

[zdeems]

I’m not doing anything unusual. No snapshots, all VSAN. Very simple vm configs. This is the way oVirt calls virt-v2v which is why I’m testing it. oVirt is initially broken for VMware provider based imports because the libvirt version is too old, and it’s unable to pull a vm list from the hypervisor. Get past that by updating libvirt manually, and conversion fails every time with this 404 error, regardless of vm size, complexity, guest OS, number of disks, etc. Happy to demonstrate