Hide Forgot
+++ 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.
Fix included in qemu-kvm-1.5.3-7.el7
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.
(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.
(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!
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.