What were you trying to do that didn't work?

We are trying to do virt-v2v migration from Openstack to vmware which has issue when source is VMware as openstack hypervisor 

Please provide the package NVR for which bug is seen:

This bug is similar to this https://bugzilla.redhat.com/show_bug.cgi?id=1988211

In this case it openstack hypervisor is VMware and entry needed is serial0.fileName with something that virt-v2v needs to understand 

How reproducible:

Migration fails when virt-v2v tries to get the VM info (libvirt xml) with error:
error: internal error: VMX entry 'serial0.fileName' doesn't contain a port part

Steps to reproduce

1. Source Vmware which is used as hypervisor for Redhat Openstack 
2. Use virt-v2v to migrate vm from Vmware for VM which are created from Openstack but on vmware 
3. Target is RHOSP 16.2/17.1

Expected results

Migration should work without workaround and following is workaround

Workaround/ReleaseComments

 
To migrate, we will need to update the vmx file on the vCenter and to keep the vmx entry consistent, it should be updated only after shutting it down

To work this around,

1. shutdown the VM

2. keep the backup of the vmx file

3. update the entry serial0.fileName with a sample telnet URI in the format "telnets://<ip>:<port>" e.g telnets://10.28.100.26:18979
 
Original entry:
serial0.fileName = "ZmVybmV0IGdBQUFBQUJrdFotaW8yclpkRXR6N3dBcDdyYkFMaWFUMVd4RENJSHgtUXpkTlMyTzRRejI3V192QVlOVUY3ZU1SOTNHZXJrN1dGb2stS0EybmpwWFQ4NjJNNlgwc2ZDdmNlOE50eFNhcU1XdlNBTmdhazQ1T1J3LUI5OEZsSDdwMDBZa2R6bWt4Y1Ax"
 
If we change the line to:
"telnets://10.28.100.26:18979#thumbprint=18:F5:79:E5:73:A5:22:83:C0:57:B9:B4:FA:CE:60:19:F1:12:F5:7B"
 
4. save the file

Actual results

Need to be fixed so that no additional entry is needed and warm migration can work