Created attachment 1696674 [details] conversion log Description of problem: qemu-img: /var/tmp/v2vovl56bced.qcow2: CURL: Error opening file: Server does not support 'range' (byte ranges) with HTTP/2 server in VMware ESXi 7 Version-Release number of selected component (if applicable): virt-v2v-1.40.2-9.el7.x86_64 libguestfs-1.40.2-9.el7.x86_64 qemu-kvm-1.5.3-174.el7.x86_64 nbdkit-1.8.0-4.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.# virt-v2v -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 esx7.0-rhel8.2-x86_64 -o rhv -os 10.66.144.40:/home/nfs_export -ip /home/passwd [ 0.0] Opening the source -i libvirt -ic vpx://root.198.169/data/10.73.199.217/?no_verify=1 esx7.0-rhel8.2-x86_64 [ 1.8] Creating an overlay to protect the source from being modified qemu-img: /var/tmp/v2vovl5fa299.qcow2: CURL: Error opening file: Server does not support 'range' (byte ranges). Could not open backing image to determine size. virt-v2v: error: qemu-img command failed, see earlier errors If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [...] Actual results: As above Expected results: Virt-v2v can convert guest from ESXI7.0 server without vddk
This is the RHEL 7 equivalent of bug 1841038. In practice, the curl block driver: - does not handle extra whitespaces between header names and values - does not check header names in a case-insensitive way (which is allowed) This was fixed upstream with commits: 7788a319399f17476ff1dd43164c869e320820a2 69032253c33ae1774233c63cedf36d32242a85fc
Considering RHEL 7 is currently in Maintenance Support 2 Phase, and that this issue was fixed on RHEL-AV 8.3, I'm tentatively closing this as NEXTRELEASE. Please reopen with a solid business justification of why this needs to be brought to RHEL 7.9.z-stream otherwise.