Bug 1079163

+++ 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: