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.
Description of problem:
When doing external memory only snapshot, following error out
error: An error occurred, but the cause is unknown
Version-Release number of selected component (if applicable):
libvirt-0.10.2-55.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.481.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. prepare a running domain
2. do external memory only snapshot
# virsh snapshot-create-as vm1 --no-metadata --memspec /tmp/vm1-mem.img --diskspec hda,snapshot=no
error: An error occurred, but the cause is unknown
Actual results:
Expected results:
External memory only snapshot should be created without error
Additional info:
Fixed upstream by:
commit cb6681ff1de3d02e8d88ce3b391ba03f8dd612f4
Author: Peter Krempa <pkrempa>
Date: Tue May 20 15:22:14 2014 +0200
qemu: snapshot: Fix return value of external checkpoint with no disks
When doing an external checkpoint of a VM with no disk selected we'd
return failure but not set error code. This was a result of ret not
being set to 0 during walking of the disk array.
Rework early failure checking and set the error code to success before
iterating the array of disks so that we return success if no disks are
snapshotted.
Fixes the following symptom (or without --diskspec for diskless VMs)
$ virsh snapshot-create-as snapshot-test --memspec /tmp/asdf --diskspec hda,snapshot=no
error: An error occurred, but the cause is unknown
I can reproduce it on libvirt-0.10.2-55.el6.x86_64:
Verify it on libvirt-0.10.2-56.el6.x86_64:
1. Preparing a running guest:
# virsh list
Id Name State
----------------------------------------------------
11 n5 running
2. Do external memory only snapshot
# virsh snapshot-create-as n5 --no-metadata --memspec /tmp/n5.img --diskspec vda,snapshot=no
Domain snapshot 1454320680 created
# ll /tmp/n5.img
-rw-------. 1 root root 282M Feb 1 17:58 /tmp/n5.img
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-0738.html