Bug 1161582
Summary: | Should improve error info when can't find backing file for snapshot | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Jun Li <juli> |
Component: | qemu-kvm-rhev | Assignee: | Jeff Cody <jcody> |
Status: | CLOSED ERRATA | QA Contact: | Qianqian Zhu <qizhu> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | chayang, eblake, hhuang, jcody, juzhang, knoel, michen, mkenneth, mrezanin, qguo, qizhu, qzhang, rbalakri, rpacheco, virt-bugs, virt-maint, xfu, xuhan |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | QEMU 2.4.0 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1084302 | Environment: | |
Last Closed: | 2016-11-07 20:16:34 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: | |||
Bug Depends On: | 1028276, 1084302 | ||
Bug Blocks: |
Comment 2
Jun Li
2014-11-07 11:52:29 UTC
The error message has been cleaned up again upstream, so I don't believe this should be an issue anymore, the error message is clear enough now. Verified with: qemu-img-rhev-2.6.0-20.el7.x86_64 qemu-kvm-rhev-2.6.0-20.el7.x86_64 kernel-3.10.0-491.el7.x86_64 Steps: 1. Create image: # qemu-img create -f qcow2 test.qcow2 5G 2. Create snapshot of the image: # qemu-img create -f qcow2 /home/snapshot1.qcow2 -b /home/test.qcow2 3. Remove the backing file: # rm -f test.qcow2 4. Launch guest with the snapshot: # /usr/libexec/qemu-kvm -drive file=snapshot1.qcow2,if=none,id=img -monitor stdio -qmp tcp::8888,server,nowait Result: Prompt error 'Could not open backing file'. qemu-kvm: -drive file=snapshot1.qcow2,if=none,id=img: Could not open backing file: Could not open 'test.qcow2': No such file or directory 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-2016-2673.html |