Description of problem: Delete info"export PATH=/path/to/nbdkit-1.1.x:$PATH" in virt-v2v-input-vmware manual page Version-Release number of selected component (if applicable): virt-v2v-1.40.2-10.module+el8.1.0+3311+ebd017c2.x86_64 How reproducible: 100% Steps to reproduce: 1.Check vddk info in virt-v2v-input-vmware man page # man virt-v2v-input-vmware ..... VDDK: Importing a guest The -it vddk parameter selects VDDK as the input transport for disks. To import a particular guest from vCenter server or ESXi hypervisor, use a command like the following, substituting the URI, guest name and SSL thumbprint: $ export PATH=/path/to/nbdkit-1.1.x:$PATH $ virt-v2v \ -ic 'vpx://root.com/Datacenter/esxi?no_verify=1' \ -it vddk \ -io vddk-libdir=/path/to/vmware-vix-disklib-distrib \ -io vddk-thumbprint=xx:xx:xx:... \ "Windows 2003" \ -o local -os /var/tmp Actual results: There is no need to set "export PATH=/path/to/nbdkit-1.1.x:$PATH" during v2v conversion via vddk Expected results: As description Additional info:
Simple patch sent: https://www.redhat.com/archives/libguestfs/2019-July/msg00190.html
Fixed upstream with https://github.com/libguestfs/libguestfs/commit/6d251e3828ff94deac7589b5892df174430e01f9 which is in libguestfs >= 1.41.1.
Verify the bug with build: virt-v2v-1.40.2-11.module+el8.1.0+3730+7d905127.x86_64 Steps: 1.Check the nbdkit info in virt-v2v-input-vmware man page # man virt-v2v-input-vmware ..... VDDK: Importing a guest The -it vddk parameter selects VDDK as the input transport for disks. To import a particular guest from vCenter server or ESXi hypervisor, use a command like the following, substituting the URI, guest name and SSL thumbprint: $ virt-v2v \ -ic 'vpx://root.com/Datacenter/esxi?no_verify=1' \ -it vddk \ -io vddk-libdir=/path/to/vmware-vix-disklib-distrib \ -io vddk-thumbprint=xx:xx:xx:... \ "Windows 2003" \ -o local -os /var/tmp .... Result: Info "export PATH=/path/to/nbdkit-1.1.x:$PATH" has been deleted, 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/RHBA-2019:3723