Bug 1022855

rhel6.5 host and guest also hit such issue that guest resume automatically from S3 after re-connent the closed spice windows. 
BTW, if use the vnc that did not hit such issue.

host info:
# uname -r && rpm -q qemu-kvm
2.6.32-424.el6.x86_64
qemu-kvm-0.12.1.2-2.414.el6.x86_64
# rpm -qa | grep spice
spice-gtk-0.20-9.el6.x86_64
spice-server-0.12.4-6.el6.x86_64
spice-vdagent-0.14.0-2.el6.x86_64
spice-glib-0.20-9.el6.x86_64
# rpm -qa | grep virt-viewer
virt-viewer-0.5.6-8.el6.x86_64
# rpm -qa | grep vnc
gtk-vnc-0.3.10-3.el6.x86_64
tigervnc-1.1.0-5.el6_4.1.x86_64
guest info:
2.6.32-424.el6.x86_64

Steps:
1. boot guest with spice/vnc and enable S3.
# /usr/libexec/qemu-kvm -M pc -S -cpu host -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -no-kvm-pit-reinjection -usb -device usb-tablet,id=input0 -name sluo -uuid 990ea161-6b67-47b2-b803-19fb01d30d30 -rtc base=localtime,clock=host,driftfix=slew -device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=0,bus=pci.0,addr=0x3 -chardev socket,id=channel1,path=/tmp/helloworld1,server,nowait -device virtserialport,chardev=channel1,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port1 -chardev socket,id=channel2,path=/tmp/helloworld2,server,nowait -device virtserialport,chardev=channel2,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port2 -drive file=/home/RHEL-6.5-Snapshot-4-Server-x86_64.qcow2,if=none,id=drive-virtio-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop -device ide-drive,bus=ide.0,unit=0,drive=drive-virtio-disk,id=virtio-disk,bootindex=1 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=00:01:02:B6:40:21,bus=pci.0,addr=0x5 -device virtio-balloon-pci,id=ballooning,bus=pci.0,addr=0x6 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -k en-us -boot menu=on -qmp tcp:0:4444,server,nowait -serial unix:/tmp/ttyS0,server,nowait -vnc :1 -spice disable-ticketing,port=5931 -monitor stdio
2. use remote-viewer with spice to connect guest.
# remote-viewer spice:$host_ip:5931
3. suspend guest.
# pm-suspend
4. close spice window.
5. re-connect the spice window.

Actual results:
after step5, guest will resume automatically from S3 after re-connent the closed spice windows.

Expected results:
guest should still in suspend status.

S3/S4 support is tech-preview in RHEL6 and it'll be promoted to fully supported
at some point, but only in RHEL7.

Therefore we're closing all S3/S4 related bugs in RHEL6. New bugs will be
considered only if they're regressions or break some important use-case or
certification.

RHEL7 is being more extensively tested and effort from QE is underway in
certifying that this particular bug is not present there.

Please reopen with a justification if you believe this bug should not be
closed. We'll consider them on a case-by-case basis following a best effort
approach.


Thank you.