Bug 1047254
Summary: | qemu-img failed to commit image | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | xhan |
Component: | qemu-kvm | Assignee: | Jeff Cody <jcody> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | acathrow, famz, hhuang, juzhang, michen, shu, sluo, virt-maint, xwei |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-1.5.3-47.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-06-13 10:33:44 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
xhan
2013-12-30 07:01:39 UTC
The offline commit, and active layer live commits, did not resize the base image file if the top image file was larger. Patches submitted upstream. Patches for this are all in upstream master, but waiting on one final patch (removal of .bdrv_make_empty stubs in qcow2 and qed drivers) prior to posting this to rhvirt-patches. Fix included in qemu-kvm-1.5.3-47.el7 Reproduce and Verify this issue with the same steps as comment #0. #### Reproduce: host info: host info: # uname -r && rpm -q qemu-kvm-rhev 3.10.0-86.el7.x86_64 qemu-kvm-rhev-1.5.3-39.el7.x86_64 Results: after step 3, qemu-img: Error while committing image #### Verify: host info: # uname -r && rpm -q qemu-kvm-rhev 3.10.0-86.el7.x86_64 qemu-kvm-rhev-1.5.3-47.el7.x86_64 Results: after step 3, commit snapshot to backingfile work normally. # qemu-img commit -f qcow2 sn1.qcow2 Image committed. Base on above, this issue has been fixed correctly, move to VERIFIED status. Best Regards, sluo 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. |