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:
In 4146b46c42e0989cb5842e04d88ab6ccb1713a48 (block: Produce zeros when
protocols reading beyond end of file), we break qemu-iotests ./check
-qcow2 022. This happens because qcow2 temporarily sets ->growable = 1
for vmstate accesses (which are stored beyond the end of regular image
data).
We introduce the bs->zero_beyond_eof to allow qcow2_load_vmstate() to
disable ->zero_beyond_eof temporarily in addition to enable ->growable.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
Run the qemu-iotests ./check -qcow2 022 test
Actual results:
qemu-iotest does not pass
Expected results:
qemu-iotest should pass
Additional info:
The fix is in upstream now. I will backport to rhel shortly.
Confirmed with Asias, this bug could also be reproduce by 'savevm'/'loadvm'.
Reproduced on qemu-kvm-0.12.1.2-2.401.el6.x86_64. 'loadvm' failed and prompt error, guest paused.
(qemu) savevm 1
(qemu)
(qemu) info status
VM status: running
(qemu)
(qemu)
(qemu) info snapshots
Snapshot devices: drive-virtio-disk0
Snapshot list (from drive-virtio-disk0):
ID TAG VM SIZE DATE VM CLOCK
1 1 284M 2013-09-13 14:49:28 00:00:16.677
(qemu) lo
logfile log loadvm
(qemu) loadvm 1
Error -22 while loading VM state
(qemu)
(qemu) info status
VM status: paused (restore-vm)
(qemu)
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
Description of problem: In 4146b46c42e0989cb5842e04d88ab6ccb1713a48 (block: Produce zeros when protocols reading beyond end of file), we break qemu-iotests ./check -qcow2 022. This happens because qcow2 temporarily sets ->growable = 1 for vmstate accesses (which are stored beyond the end of regular image data). We introduce the bs->zero_beyond_eof to allow qcow2_load_vmstate() to disable ->zero_beyond_eof temporarily in addition to enable ->growable. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: Run the qemu-iotests ./check -qcow2 022 test Actual results: qemu-iotest does not pass Expected results: qemu-iotest should pass Additional info: The fix is in upstream now. I will backport to rhel shortly.