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 1007226 - Introduce bs->zero_beyond_eof
Summary: Introduce bs->zero_beyond_eof
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ademar Reis
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1007224
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-12 07:20 UTC by Asias He
Modified: 2014-06-18 03:36 UTC (History)
8 users (show)

Fixed In Version: qemu-kvm-1.5.3-7.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1007224
Environment:
Last Closed: 2014-06-13 09:38:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Asias He 2013-09-12 07:20:35 UTC 
+++ This bug was initially created as a clone of Bug #1007224 +++

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.
Comment 2 Miroslav Rezanina 2013-09-26 09:34:13 UTC 
Fix included in qemu-kvm-1.5.3-7.el7
Comment 6 Qunfang Zhang 2013-12-27 03:25:06 UTC 
This bug could not be reproduce on both the old qemu-kvm-1.5.3-6.el7.x86_64 and the latest qemu-kvm-1.5.3-30.el7.x86_64 with the reproducer in bug 1007224#c2.

Steps:
1. Boot up a guest with qcow2 format image.

2. savevm/loadvm

(qemu) savevm 1
(qemu) info snapshots 
ID        TAG                 VM SIZE                DATE       VM CLOCK
1          1                     11M 2013-12-27 11:05:02   00:00:04.804
(qemu) loadvm 1 (wait for a while)
(qemu) info status
VM status: running

Repeat step 2 when guest read/write data for several times, could not reproduce. 

Ademar, could we call this verify pass? Or any additional testing is required?  Thanks.
Comment 7 Ademar Reis 2013-12-27 13:16:03 UTC 
(In reply to Qunfang Zhang from comment #6)
> 
> Repeat step 2 when guest read/write data for several times, could not
> reproduce. 
> 
> Ademar, could we call this verify pass? Or any additional testing is
> required?  Thanks.

I investigated it and found that this is expected behavior. The broken patch was never added alone to a RHEL7 build: Stefan included both fixes together in the same build (the fix for the original bug, where this problem was introduced and the fix for this problem).

So yes, you can consider this verified. Thanks.
Comment 8 Qunfang Zhang 2013-12-29 06:16:08 UTC 
(In reply to Ademar de Souza Reis Jr. from comment #7)
> (In reply to Qunfang Zhang from comment #6)
> > 
> > Repeat step 2 when guest read/write data for several times, could not
> > reproduce. 
> > 
> > Ademar, could we call this verify pass? Or any additional testing is
> > required?  Thanks.
> 
> I investigated it and found that this is expected behavior. The broken patch
> was never added alone to a RHEL7 build: Stefan included both fixes together
> in the same build (the fix for the original bug, where this problem was
> introduced and the fix for this problem).
> 
> So yes, you can consider this verified. Thanks.

Okay, thanks a lot for your confirmation!
Comment 9 Ludek Smid 2014-06-13 09:38:26 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.