Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
As subject
Version-Release number of selected component (if applicable):
curl-7.29.0-35.el7.x86_64
qemu-kvm-rhev-2.6.0-22.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Prepare a tftp server and a image on the tftp dir.
2. Check if the tftp server works well
# curl tftp://10.66.6.236/tftp -o /tmp/tftp
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 100M 100 100M 0 0 2673k 0 0:00:38 0:00:38 --:--:-- 2679k
100 100M 100 100M 0 0 2673k 0 0:00:38 0:00:38 --:--:-- 2673k
3. Try to create json backing image via tftp
# qemu-img create -f qcow2 -b 'json:{"file.driver":"tftp", "file.url":"tftp://10.66.6.236/tftp"}' /var/lib/libvirt/images/tftp.img
qemu-img: /var/lib/libvirt/images/tftp.img: CURL: Error opening file: getpeername() failed with errno 107: Transport endpoint is not connected
Actual results:
As step3
Expected results:
Backing image created.
Additional info:
Hi,
It turns out that our curl block driver's TFTP support is completely broken by design: For rather obvious reasons, all network protocols that we support in the block layer need to offer some functionality to read only a range of the image file. However, TFTP does not have this functionality, and therefore, it was always basically completely unusable.
This is probably not the immediate reason behind the error message you are seeing, but it does mean that QEMU basically has no support for reading image files over TFTP and the only thing we can do is to stop pretending that we do.
Sorry,
Max
Since the TFTP is completely unusable in qemu, I think it should be highlighted from upstream codes in case of mistakenly using.
Maybe we should write 'tftp: deprecated' in qapi/block-core.json and docs/qmp-commands.txt
Description of problem: As subject Version-Release number of selected component (if applicable): curl-7.29.0-35.el7.x86_64 qemu-kvm-rhev-2.6.0-22.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Prepare a tftp server and a image on the tftp dir. 2. Check if the tftp server works well # curl tftp://10.66.6.236/tftp -o /tmp/tftp % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 100M 100 100M 0 0 2673k 0 0:00:38 0:00:38 --:--:-- 2679k 100 100M 100 100M 0 0 2673k 0 0:00:38 0:00:38 --:--:-- 2673k 3. Try to create json backing image via tftp # qemu-img create -f qcow2 -b 'json:{"file.driver":"tftp", "file.url":"tftp://10.66.6.236/tftp"}' /var/lib/libvirt/images/tftp.img qemu-img: /var/lib/libvirt/images/tftp.img: CURL: Error opening file: getpeername() failed with errno 107: Transport endpoint is not connected Actual results: As step3 Expected results: Backing image created. Additional info: