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:
If your raw source image happens to be zero length then qemu-img convert fails with a floating point exception
Version-Release number of selected component (if applicable):
Version : 0.12.1.2
Release : 2.295.el6_3.2
How reproducible:
Steps to Reproduce:
1. touch zero-image
2. qemu-img convert zero-image /tmp/fred
Actual results:
$ qemu-img convert zero-image /tmp/fred
Floating point exception
Expected results:
qemu-img should copy the zero length file
Additional info:
qemu-img info works fine on a zero length file
$ qemu-img info zero-image
image: zero-image
file format: raw
virtual size: 0 (0 bytes)
disk size: 0
Thank you for taking the time to enter a bug report with us. We appreciate the feedback and look to use reports such as this to guide our efforts at improving our products. That being said, this bug tracking system is not a mechanism for requesting support, and we are not able to guarantee the timeliness or suitability of a resolution.
If this issue is critical or in any way time sensitive, please raise a ticket through your regular Red Hat support channels to make certain it receives the proper attention and prioritization to assure a timely resolution.
For information on how to contact the Red Hat production support team, please visit: https://www.redhat.com/support/process/production/#howto
Reproduce this bug as follow version:
Host:
# uname -r
2.6.32-393.el6.x86_64
# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.356.el6.x86_64
Steps:
1.# qemu-img create -f raw test1.raw 0K
Formatting 'test1.raw', fmt=raw size=0
2.# qemu-img info test1.raw
image: test1.raw
file format: raw
virtual size: 0 (0 bytes)
disk size: 0
3.# qemu-img convert -f raw -O qcow2 test1.raw test1.qcow2
Resutls:After step3
Floating point exception (core dumped)
Verify this bug as follow version:
Host
# uname -r
2.6.32-393.el6.x86_64
# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.377.el6.x86_64
Steps as same as reproduce
Results:After step 3
no core dump,and error info
# qemu-img convert -f raw -O qcow2 test1.raw test1.qcow2
# qemu-img info test1.qcow2
image: test1.qcow2
file format: qcow2
virtual size: 0 (0 bytes)
disk size: 132K
cluster_size: 65536
Addtional info:
1)I also tried to convert a qcow2 img(0K) to a raw format img. Work well.
According to above test ,this bug fixed.
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2013-1553.html