RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1846238 - 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
Summary: qemu-img: /var/tmp/v2vovl56bced.qcow2: CURL: Error opening file: Server does ...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.9
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: Virtualization Bugs
URL:
Whiteboard: V2V
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-11 07:46 UTC by liuzi
Modified: 2021-08-31 18:56 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-31 18:56:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
conversion log (4.73 KB, text/plain)
2020-06-11 07:46 UTC, liuzi
no flags Details

Description liuzi 2020-06-11 07:46:16 UTC
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

Comment 4 Pino Toscano 2020-06-17 07:43:26 UTC
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

Comment 11 Klaus Heinrich Kiwi 2021-08-31 18:56:15 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.