Bug 920567
| Summary: | Win8 32/64 and win2012 s3 state block by graphics | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | langfang <flang> |
| Component: | qemu-kvm | Assignee: | Vadim Rozenfeld <vrozenfe> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 | CC: | acathrow, bsarathy, dblechte, flang, hhuang, huding, juzhang, lmiksik, mazhang, mkenneth, mkrcmari, mrezanin, qzhang, rhod, virt-maint, xwei |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 895362 | Environment: | |
| Last Closed: | 2014-06-13 12:23:23 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 895362 | ||
| Bug Blocks: | 923626 | ||
|
Description
langfang
2013-03-12 11:21:41 UTC
Moving to Vadim, as he is the developer of Win8 qxl display-only driver. Could you please try the latest qxl driver available for download here: https://brewweb.devel.redhat.com/buildinfo?buildID=323507 Thanks, Vadim. Reproduce this bug using the following version:
qemu-kvm-1.5.3-50.el7.x86_64
3.10.0-101.el7.x86_64
Steps to Reproduce:
1. boot a windows guest (win8 32/64 and win2012 guests were tested)
/usr/libexec/qemu-kvm -M pc -cpu SandyBridge -enable-kvm -m 2048 -smp 2,sockets=1,cores=2,threads=1 -name rhel7 -uuid 6afa5f93-2d4f-420f-81c6-e5fdddbd1c83 -drive file=/home/win2012-64-virtio.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,serial=40c061dd-5d60-4fc5-865f-55db700407f0,cache=none,werror=stop,rerror=stop,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,id=hostnet0,vhost=on -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:42:0a:00,bus=pci.0,addr=0x3 -vnc :2 -monitor stdio -spice port=5900,disable-ticketing -global qxl-vga.vram_size=67108864 -vga qxl -boot menu=on -device virtio-balloon-pci,id=balloon1 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0
2. inside guest, execute "powercfg -a" in cmd.
Actual results:
after step2, s3 is disabled by graphics:
...
Standby (S3)
An internal system component has disabled this standby state.
Graphics
...
Verify this bug using the following version:
qemu-kvm-1.5.3-50.el7.x86_64
kernel-3.10.0-101.el7.x86_64
qxlwddm-0.3
Steps to Reproduce:
1. boot a windows guest (win8 32/64 and win2012 guests were tested)
/usr/libexec/qemu-kvm -M pc -cpu SandyBridge -enable-kvm -m 2048 -smp 2,sockets=1,cores=2,threads=1 -name rhel7 -uuid 6afa5f93-2d4f-420f-81c6-e5fdddbd1c83 -drive file=/home/win2012-64-virtio.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,serial=40c061dd-5d60-4fc5-865f-55db700407f0,cache=none,werror=stop,rerror=stop,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,id=hostnet0,vhost=on -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:42:0a:00,bus=pci.0,addr=0x3 -vnc :2 -monitor stdio -spice port=5900,disable-ticketing -global qxl-vga.vram_size=67108864 -vga qxl -boot menu=on -device virtio-balloon-pci,id=balloon1 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -cdrom qxlwddm.iso
2. inside guest, execute "powercfg -a" in cmd.
3. inside guest, update the driver of "Display adapters" to qxlwddm
4. inside guest, execute "powercfg -a" in cmd.
Actual results:
after step2, s3 is disabled by graphics:
...
Standby (S3)
An internal system component has disabled this standby state.
Graphics
...
after step4, s3 is enabled
Based on the above results, I think this bug has been fixed.
This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request. |