Description of problem: Should hidden "virt-v2v: warning: /usr/share/virt-tools/pnp_wait.exe is missing.."during conversion Version-Release number of selected component (if applicable): virt-v2v-1.42.0-6.module+el8.4.0+8855+a9e237a9.x86_64 libguestfs-1.42.0-2.module+el8.4.0+8855+a9e237a9.x86_64 How reproducible: 100% Steps to Reproduce: 1. There is "virt-v2v: warning: /usr/share/virt-tools/pnp_wait.exe is missing.."during windows conversion # virt-v2v -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 -it vddk -io vddk-libdir=/home/vmware-vix-disklib-distrib -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 -oo rhv-direct -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -op /home/rhvpasswd -of raw -os nfs_data -b ovirtmgmt esx7.0-win2019-x86_64 [ 1.2] Opening the source -i libvirt -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 esx7.0-win2019-x86_64 -it vddk -io vddk-libdir=/home/vmware-vix-disklib-distrib -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78 [ 2.9] Creating an overlay to protect the source from being modified [ 3.8] Opening the overlay [ 10.1] Inspecting the overlay [ 15.6] Checking for sufficient free disk space in the guest [ 15.6] Estimating space required on target for each disk [ 15.6] Converting Windows Server 2019 Standard to run on KVM virt-v2v: warning: /usr/share/virt-tools/pnp_wait.exe is missing. Firstboot scripts may conflict with PnP. ** (process:16133): WARNING **: 12:20:28.458: Entity http://pcisig.com/pci/1af4/105a referenced but not defined virt-v2v: warning: there is no QXL driver for this version of Windows (10.0 x86_64). virt-v2v looks for this driver in /usr/share/virtio-win/virtio-win.iso The guest will be configured to use a basic VGA display driver. virt-v2v: This guest has virtio drivers installed. [ 36.1] Mapping filesystem data to avoid copying unused and blank areas [ 37.2] Closing the overlay [ 37.5] Assigning disks to buses [ 37.5] Checking if the guest needs BIOS or UEFI to boot [ 37.5] Initializing the target -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -op /home/rhvpasswd -os nfs_data ........ Actual results: As above description Expected results: Should hidden this warning because there is no pnp_wait.exe in /usr/share/virt-tools/ at all # ls /usr/share/virt-tools/ rhev-apt.exe rhsrvany.exe Additional info：
I downgraded it to a debug message: https://github.com/libguestfs/virt-v2v/commit/834bea6931b49dc4b14ebe04fd0e0884290bfb78
Test the bug with builds: virt-v2v-1.42.0-11.module+el8.5.0+10793+d881d728.x86_64 Steps: 1.Convert a windows guest to rhv # virt-v2v -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 -it vddk -io vddk-libdir=/home/vmware-vix-disklib-distrib -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 -oo rhv-direct -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -op /home/rhvpasswd -of raw -os nfs_data -b ovirtmgmt esx7.0-win2016-x86_64 [ 0.5] Opening the source -i libvirt -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 esx7.0-win2016-x86_64 -it vddk -io vddk-libdir=/home/vmware-vix-disklib-distrib -io vddk-thumbprint=B5:52:1F:B4:21:09:45:24:51:32:56:F6:63:6A:93:5D:54:08:2D:78 [ 2.2] Creating an overlay to protect the source from being modified [ 3.0] Opening the overlay [ 8.2] Inspecting the overlay [ 15.4] Checking for sufficient free disk space in the guest [ 15.4] Estimating space required on target for each disk [ 15.4] Converting Windows Server 2016 Standard to run on KVM ** (process:131224): WARNING **: 14:05:13.566: Entity http://pcisig.com/pci/1B36/0100 referenced but not defined virt-v2v: This guest has virtio drivers installed. [ 28.7] Mapping filesystem data to avoid copying unused and blank areas [ 29.2] Closing the overlay [ 29.5] Assigning disks to buses [ 29.5] Checking if the guest needs BIOS or UEFI to boot [ 29.5] Initializing the target -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -op /home/rhvpasswd -os nfs_data [ 30.8] Copying disk 1/1 to qemu URI json:{ "file.driver": "nbd", "file.path": "/tmp/v2vnbdkit.VjtlFI/nbdkit4.sock", "file.export": "/" } (raw) ^C (0.00/100%) Result: There is no warning info like: "virt-v2v: warning: /usr/share/virt-tools/pnp_wait.exe is missing.."during windows conversion
Test the bug with builds: virt-v2v-1.42.0-11.module+el8.5.0+10793+d881d728.x86_64 Steps: 1.Convert a windows guest to rhv # virt-v2v -i vmx -it ssh ssh://root.75.219/vmfs/volumes/esx6.7-matrix/esx6.7-win10-x86_64-efi/esx6.7-win10-x86_64-efi.vmx -ip /home/esxpw [ 0.0] Opening the source -i vmx ssh://root.75.219/vmfs/volumes/esx6.7-matrix/esx6.7-win10-x86_64-efi/esx6.7-win10-x86_64-efi.vmx Password: Password: [ 8.1] Creating an overlay to protect the source from being modified [ 8.4] Opening the overlay [ 12.7] Inspecting the overlay [ 21.4] Checking for sufficient free disk space in the guest [ 21.4] Estimating space required on target for each disk [ 21.4] Converting Windows 10 Enterprise to run on KVM ** (process:188888): WARNING **: 10:11:13.789: Entity http://pcisig.com/pci/1B36/0100 referenced but not defined virt-v2v: This guest has virtio drivers installed. [ 26.8] Mapping filesystem data to avoid copying unused and blank areas virt-v2v: warning: fstrim on guest filesystem /dev/sda2 failed. Usually you can ignore this message. To find out more read "Trimming" in virt-v2v(1). Original message: fstrim: fstrim: /sysroot/: the discard operation is not supported [ 27.4] Closing the overlay [ 27.6] Assigning disks to buses [ 27.6] Checking if the guest needs BIOS or UEFI to boot virt-v2v: This guest requires UEFI on the target to boot. [ 27.6] Initializing the target -o libvirt -os default [ 27.6] Copying disk 1/1 to /var/lib/libvirt/images/esx6.7-win10-x86_64-efi-sda (raw) (100.00/100%) [ 870.2] Creating output metadata virt-v2v: warning: could not define libvirt domain: unsupported configuration: IDE controllers are unsupported for this QEMU binary or machine type. The libvirt XML is still available in ‘/tmp/v2vlibvirt26dcb0.xml’. Try running ‘virsh -c qemu:///system define /tmp/v2vlibvirt26dcb0.xml’ yourself instead. [ 870.2] Finishing off Result: There is no warning info like: "virt-v2v: warning: /usr/share/virt-tools/pnp_wait.exe is missing.."during windows conversion
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 (virt:av bug fix and enhancement update), 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-2021:4684