Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
Version of components: qemu-kvm-rhev-2.1.2-6.el7.x86_64 steps: 1,creat an image via qemu-img. # qemu-img create -f qcow2 test.qcow2 5G 2,boot qemu-kvm as followings: # /usr/libexec/qemu-kvm -drive file=./test.qcow2,if=none,id=img \ -monitor stdio -qmp tcp::8888,server,nowait 3,create another two qcow2 format files via qemu-img. # qemu-img create -f qcow2 /home/test1.qcow2 500M Formatting '/home/test1.qcow2', fmt=qcow2 size=524288000 encryption=off cluster_size=65536 lazy_refcounts=off # qemu-img create -f qcow2 /home/test2.qcow2 500M 4,do snapshot via qmp. { "execute": "blockdev-snapshot-sync", "arguments": { "device": "img", "snapshot-file": "/home/test1.qcow2", "format": "qcow2", "mode": "absolute-paths" } } { "execute": "blockdev-snapshot-sync", "arguments": { "device": "img", "snapshot-file": "/home/test2.qcow2", "format": "qcow2", "mode": "absolute-paths" } } Results: After step 4, {"execute":"qmp_capabilities"} {"return": {}} { "execute": "blockdev-snapshot-sync", "arguments": { "device": "img", "snapshot-file": "/home/test1.qcow2", "format": "qcow2", "mode": "absolute-paths" } } {"return": {}} { "execute": "blockdev-snapshot-sync", "arguments": { "device": "img", "snapshot-file": "/home/test2.qcow2", "format": "qcow2", "mode": "absolute-paths" } } {"error": {"class": "GenericError", "desc": "Could not open '/home/test1.qcow2': Could not open backing file: Could not open '/home/./test.qcow2': No such file or directory: No such file or directory"}}