Description of problem: Add virt-v2v and libvirt version to the beginning of v2v debug log Version-Release number of selected component (if applicable): virt-v2v-1.45.94-3.el9.x86_64 How reproducible: 100% Steps to Reproduce: 1.Convert a guest from VMware to rhv by virt-v2v and add -v -x to collect the debug log # virt-v2v -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk6.7 -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78 -ip /home/passwd -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -op /home/rhvpasswd -os nfs_data -b ovirtmgmt esx7.0-rhel8.5-x86_64 -v -x libvirt xml is: <domain type='vmware' xmlns:vmware='http://libvirt.org/schemas/domain/vmware/1.0'> <name>esx7.0-rhel8.5-x86_64</name> <uuid>4203738d-97d7-2aae-66fe-2afbc4fb4d39</uuid> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='static'>1</vcpu> ..... Actual results: There is no virt-v2v and libvirt version in virt-v2v-1.45.94-3 debug log Expected results: As above description Additional info: There is virt-v2v and libvirt version in virt-v2v-1.45.3-3 debug log
Thanks - upstream fix: https://github.com/libguestfs/virt-v2v/commit/1673fc4b640f754fbdc942a6636fd0e95b996144
Pre-Verified with the version: virt-v2v-1.45.95-3.el9.x86_64 # virt-v2v -ic vpx://root.73.141/data/10.73.75.219/?no_verify=1 -it vddk -io vddk-libdir=/root/vddk_libdir/latest -io vddk-thumbprint=1F:97:34:5F:B6:C2:BA:66:46:CB:1A:71:76:7D:6B:50:1E:03:00:EA -ip /v2v-ops/esxpw -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -op /v2v-ops/rhvpasswd -os nfs_data -b ovirtmgmt esx6.7-rhel8.5-x86_64 -v -x virt-v2v: virt-v2v 1.45.95rhel=9,release=3.el9 (x86_64) libvirt version: 7.10.0 libvirt xml is: <domain type='vmware' xmlns:vmware='http://libvirt.org/schemas/domain/vmware/1.0'> <name>esx6.7-rhel8.5-x86_64</name> modify to verified:Tested
Verified with the version: virt-v2v-1.45.96-1.el9.x86_64 libvirt-libs-8.0.0-0rc1.1.el9.x86_64 # virt-v2v -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk6.7 -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78 -ip /home/passwd -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -op /home/rhvpasswd -os nfs_data -b ovirtmgmt esx7.0-rhel8.5-x86_64 -v -x virt-v2v: virt-v2v 1.45.96rhel=9,release=1.el9 (x86_64) libvirt version: 8.0.0 libvirt xml is: <domain type='vmware' xmlns:vmware='http://libvirt.org/schemas/domain/vmware/1.0'> <name>esx7.0-rhel8.5-x86_64</name> <uuid>4203cd28-fd78-f9f7-7d2d-30815e253d22 .......................... Moving the status 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 (new packages: virt-v2v), 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-2022:2566