Description of problem: Example URI of "Convert from ESXi hypervisor over SSH to local libvirt" is incorrect in v2v man page Version-Release number of selected component (if applicable): virt-v2v-1.36.10-6.el7.x86_64 libguestfs-1.36.10-6.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.Check vmx info in v2v man page,found example URI of "Convert from ESXi hypervisor over SSH to local libvirt" is incorrect #man virt-v2v .... Convert from ESXi hypervisor over SSH to local libvirt You have an ESXi hypervisor called "esxi.example.com" with SSH access enabled. You want to convert from VMFS storage on that server to a local file. virt-v2v \ -i vmx -it ssh \ "root.com/vmfs/volumes/datastore1/guest/guest.vmx" \ -o local -os /var/tmp The guest must not be running. Virt-v2v would not need to be run as root in this case. For more information about converting from VMX files see "INPUT FROM VMWARE VMX" below. .... 2.If missing "ssh://" in the vmx url when convert guest from VMFS storage by virt-v2v, will pop up below error # virt-v2v -i vmx -it ssh root.196.89/vmfs/volumes/59b21f90-80cd9f45-9122-30e1715dcab0/esx6.0-rhel7.4-x64-vmware-tools/esx6.0-rhel7.4-x64-vmware-tools.vmx [ 0.0] Opening the source -i vmx root.196.89/vmfs/volumes/59b21f90-80cd9f45-9122-30e1715dcab0/esx6.0-rhel7.4-x64-vmware-tools/esx6.0-rhel7.4-x64-vmware-tools.vmx virt-v2v: error: vmx URI remote server name omitted If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [...] Actual results: Because v2v claims must specify a remote "ssh://..." URI pointing to the VMX file when using the SSH input transport. "ssh://" is missing in the URI example of "Convert from ESXi hypervisor over SSH to local libvirt" in v2v man page Expected results: Add "ssh://"to URI example of "Convert from ESXi hypervisor over SSH to local libvirt" in v2v man page，looks like virt-v2v \ -i vmx -it ssh \ "ssh://root.com/vmfs/volumes/datastore1/guest/guest.vmx" \ -o local -os /var/tmp Additional info:
Fixed upstream with https://github.com/libguestfs/libguestfs/commit/3d4c84185a5098f04e59e6d363b370d4d40e4c13 which is fixed in libguestfs >= 1.37.38.
Verify the bug with below builds: virt-v2v-1.38.2-3.el7.x86_64 libguestfs-1.38.2-3.el7.x86_64 Steps: 1.Check vmx info in v2v man page #man virt-v2v .... Convert from ESXi hypervisor over SSH to local libvirt You have an ESXi hypervisor called "esxi.example.com" with SSH access enabled. You want to convert from VMFS storage on that server to a local file. virt-v2v \ -i vmx -it ssh \ "ssh://root.com/vmfs/volumes/datastore1/guest/guest.vmx" \ -o local -os /var/tmp The guest must not be running. Virt-v2v would not need to be run as root in this case. For more information about converting from VMX files see "INPUT FROM VMWARE VMX" below. .... Result: Example URI of "Convert from ESXi hypervisor over SSH to local libvirt" is correct, so move the bug from ON_QA to VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:3021