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.
+++ This bug was initially created as a clone of Bug #1283116 +++
Cloning for qemu-kvm in RHEL 7.3. The bug is fixed by upstream commit f4a769aba
("raw-posix: Fix .bdrv_co_get_block_status() for unaligned image size").
+++ This bug was initially created as a clone of Bug #1229394 +++
Description of problem:
$ truncate -s 1G test_sparse
$ echo "a" >> test_sparse
$ qemu-img map test_sparse
Version-Release number of selected component:
qemu-img-2.3.0-4.fc22
Additional info:
reporter: libreport-2.5.1
backtrace_rating: 4
cmdline: qemu-img map test_sparse
crash_function: get_block_status
executable: /usr/bin/qemu-img
global_pid: 70309
kernel: 4.0.4-303.fc22.x86_64
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (2 frames)
#4 get_block_status at qemu-img.c:2190
#5 img_map at qemu-img.c:2286
--- Additional comment from Cole Robinson on 2015-06-08 22:52:53 CEST ---
Thanks for the simple reproducer! The assertion reproduces for me with qemu-2.1 up to current qemu.git
CCing some block layer folks
--- Additional comment from Kevin Wolf on 2015-06-09 11:26:23 CEST ---
Sent an upstream patch to fix this:
http://lists.nongnu.org/archive/html/qemu-devel/2015-06/msg02505.html
--- Additional comment from Cole Robinson on 2015-06-09 16:17:22 CEST ---
Thanks Kevin!
--- Additional comment from Fedora Update System on 2015-08-12 00:10:47 CEST ---
qemu-2.3.0-7.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/qemu-2.3.0-7.fc22
--- Additional comment from Fedora Update System on 2015-08-12 15:36:11 CEST ---
qemu-2.3.1-1.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/qemu-2.3.1-1.fc22
--- Additional comment from Fedora Update System on 2015-08-13 18:57:16 CEST ---
Package qemu-2.3.1-1.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing qemu-2.3.1-1.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-13402/qemu-2.3.1-1.fc22
then log in and leave karma (feedback).
--- Additional comment from Fedora Update System on 2015-08-18 07:15:53 CEST ---
qemu-2.3.1-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
--- Additional comment from Daniel Erez on 2015-11-26 11:59:22 CET ---
Hi Max,
Should this bug be cloned in order to get it in qemu-kvm-rhev 7.2.z?
Thanks!
Daniel
--- Additional comment from Max Reitz on 2015-11-27 17:15:49 CET ---
Hi Daniel,
I do not know the exact process, but I think it does indeed make sense to have one BZ per target version.
Thank you,
Max
rhel-7.2.z clone will be created from Bug 1283116 once the 1283116 is fully approved for zstream. For more information about the ZStream process, please follow the link: https://mojo.redhat.com/docs/DOC-1021938