Bug 1203119
Summary: | 2nd active commit after snapshot triggers qemu failure | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Jan Kurik <jkurik> |
Component: | libvirt | Assignee: | Eric Blake <eblake> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | 7.1 | CC: | alitke, areis, bmcclain, dyuan, eblake, gklein, jcody, jdenemar, juzhang, knoel, mst, mzhan, pm-eus, rbalakri, sherold, shu, shyu, snagar, xuzhang, yanyang |
Target Milestone: | rc | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | libvirt-1.2.8-16.el7_1.2 | Doc Type: | Bug Fix |
Doc Text: |
Cause: qemu uses strcmp() instead of inode comparison when searching for a file name in a backing chain. However, it tracks a different initial string for a backing chain member when opening an existing chain than it does when creating a snapshot.
Consequence: If libvirt passes a different string than what qemu is expecting, even though that string resolves to the same file, then qemu is unable to perform blockpull and blockcommit actions involving that part of the chain.
Fix: Libvirt was taught to query qemu's notion of the string associated with a backing chain element.
Result: It is now possible to create multiple snapshots and then use consecutive blockcommit to clean them up without hitting an error message from qemu complaining about an unknown file name.
|
Story Points: | --- |
Clone Of: | 1199182 | Environment: | |
Last Closed: | 2015-03-26 17:54:35 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: | 1199182 | ||
Bug Blocks: |
Description
Jan Kurik
2015-03-18 07:28:42 UTC
Backport sent for review: http://post-office.corp.redhat.com/archives/rhvirt-patches/2015-March/msg00479.html 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. https://rhn.redhat.com/errata/RHBA-2015-0742.html |