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.
+++ This bug was initially created as a clone of Bug #1079162 +++
Description of problem:
The guest will be destroyed abnormally while revert the guest's snapshot which took in "pmsuspended" status
Version-Release number of selected component (if applicable):
kernel-3.10.0-112.el7.x86_64
libvirt-1.1.1-28.el7.x86_64
qemu-kvm-rhev-1.5.3-53.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Prepare a running guest with qemu-guest-agent installed
# virsh list
Id Name State
----------------------------------------------------
2 rhel7 running
2.Do S3 with the guest
# virsh dompmsuspend rhel7 --target mem
Domain rhel7 successfully suspended
[root@rhel6 ~]# virsh list
Id Name State
----------------------------------------------------
2 rhel7 pmsuspended
3.Take the internal snapshot for the guest
#virsh snapshot-create-as rhel7 sp1
Domain snapshot sp1 created
# virsh snapshot-list rhel7
Name Creation Time State
------------------------------------------------------------
sp1 2014-03-18 22:10:19 -0400 pmsuspended
4.Wakeup the guest
#virsh dompmwakeup rhel7
Domain rhel7 successfully woken up
# virsh list
Id Name State
----------------------------------------------------
2 rhel7 running
5.Revert the snapshot for the guest
# virsh list --all
Id Name State
----------------------------------------------------
- rhel7 shut off
# ps aux|grep qemu
root 25663 0.0 0.0 103252 840 pts/0 S+ 22:45 0:00 grep qemu
6.Both rhel7 and rhel6 can hit this issue
Actual results:
The guest was destroyed abnormally while revert the guest's snapshot which took in "pmsuspended" status
Expected results:
If we support take and revert snapshot while guest in pmsuspend status, the guest should be in "pmsuspended" status
in step 5 and shouldn't be destroyed abnormally. if we didn't support take and revert snapshot while guest in pmsuspended
status, it should give a clear error
Additional info:
Comment 3RHEL Program Management
2014-04-04 21:26:23 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.