Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 612508

Summary: Backport qcow2 fixes to RHEL 5
Product: Red Hat Enterprise Linux 5 Reporter: RHEL Program Management <pm-rhel>
Component: kvmAssignee: Virtualization Maintenance <virt-maint>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: high    
Version: 5.5CC: cpelland, ehabkost, hateya, kwolf, michen, mjenner, mkenneth, ndai, plyons, pm-eus, tburke, virt-maint, ykaul
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: kvm-83-164.el5_5.15 Doc Type: Bug Fix
Doc Text:
When using QCOW2 disk images, certain I/O operation or disk space depletion errors could potentially have caused image corruption or a virtual guest to stop running. This was due to the improper error-handling code for QCOW2 disk images. This has been fixed with this update so that the aforementioned types of errors are handled correctly, thus increasing QCOW2 disk integrity in such situations.
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-29 05:49:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 605701    
Bug Blocks:    

Description RHEL Program Management 2010-07-08 12:09:55 UTC
This bug has been copied from bug #605701 and has been proposed
to be backported to 5.5 z-stream (EUS).

Comment 10 Eduardo Habkost 2010-07-23 19:14:51 UTC
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.

New Contents:
Cause:

1) error handling of the qcow2 code didn't properly check the returned error codes or didn't propagate the error code to the callers so errors could be properly handled;
2) other smaller bugs on qcow2 code.

Consequence:

1) certain error situations (such as I/O errors or Out Of Space errors) were ignored or reported incorrectly by qemu-kvm, risking image corruption or stopping the guests without reporting the right error conditions;
2) risk of qcow2 image corruption.


Fix: backport error handling fixes from upstream qemu.

Result: improved qcow2 reliability and better error handling and reporting.

Comment 11 Douglas Silas 2010-07-28 15:42:34 UTC
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.

Diffed Contents:
@@ -1,14 +1 @@
-Cause:
+When using QCOW2 disk images, certain I/O operation or disk space depletion errors could potentially have caused image corruption or a virtual guest to stop running. This was due to the improper error-handling code for QCOW2 disk images. This has been fixed with this update so that the aforementioned types of errors are handled correctly, thus increasing QCOW2 disk integrity in such situations.-
-1) error handling of the qcow2 code didn't properly check the returned error codes or didn't propagate the error code to the callers so errors could be properly handled;
-2) other smaller bugs on qcow2 code.
-
-Consequence:
-
-1) certain error situations (such as I/O errors or Out Of Space errors) were ignored or reported incorrectly by qemu-kvm, risking image corruption or stopping the guests without reporting the right error conditions;
-2) risk of qcow2 image corruption.
-
-
-Fix: backport error handling fixes from upstream qemu.
-
-Result: improved qcow2 reliability and better error handling and reporting.

Comment 12 errata-xmlrpc 2010-07-29 05:49:55 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0536.html