Hide Forgot
Description of problem: Boot win8 with "-vga cirrus -vnc :3" in qemu-kvm command line, then can not support s4 in guest. But use this order "-vnc :3 -vga cirrus" to boot guest, then s4 is successful. Version-Release number of selected component (if applicable): host kernel: 2.6.32-419.el6.x86_64 qemu-kvm: qemu-kvm-0.12.1.2-2.404.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Boot win8 guest with the following command line: /usr/libexec/qemu-kvm -M pc -enable-kvm -m 4G -smp 4,sockets=1,cores=4,threads=1 -name test -rtc base=localtime,clock=host,driftfix=slew -k en-us -boot menu=on -vga cirrus -vnc :3 -usb -device usb-tablet -global PIIX4_PM.disable_s3=0 -global PIIX3_PM.disable_s4=0 -monitor stdio -drive file=/home/win8-32.raw,if=none,id=drive-system-disk,media=disk,format=raw,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,drive=drive-system-disk,id=system-disk,addr=0x9 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=00:22:15:27:54:8d,bus=pci.0,addr=0x8 2. In win8 guest: powercfg -a 3. Actual results: With "-vga cirrus -vnc :3" order, can not support s4 Expected results: It should be support s4 Additional info: With "-vnc :3 -vga cirrus" order: It can support s4.
How about RHEL7 host?
(In reply to Amit Shah from comment #2) > How about RHEL7 host? Test this issue with RHEL7 host: kernel: 3.10.0-22.el7.x86_64 qemu-kvm: qemu-kvm-rhev-1.5.3-3.el7.x86_64 Actual Results: Boot win8 with "-vga cirrus -vnc :3" in qemu-kvm command line, then can not support s4 in guest. But use this order "-vnc :3 -vga cirrus" to boot guest, then s4 is successful.
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.