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.
Clone this bug for track the issue on rhel7.
HOst:
[root@amd-9600b-8-2 ~]# uname -r
3.8.0-0.40.el7.x86_64
[root@amd-9600b-8-2 ~]# rpm -q qemu-kvm
qemu-kvm-1.4.0-1.el7.x86_64
Guest:win2012
CLI:/usr/libexec/qemu-kvm -M q35 -enable-kvm -m 2G -smp 2 -uuid `uuidgen` -no-user-config -nodefaults -rtc base=utc -drive file=/home/win2012-64.qcow2,serial=QEMU-DISK1,if=none,id=drive-system-disk,format=qcow2,cache=none,serial=QEMU-DISK1 -device ide-drive,drive=drive-system-disk,id=system-disk,ver=langfang -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:60:3f:29,addr=0x4 -monitor stdio -boot menu=on,order=c -usb -device usb-tablet,id=input0 -drive if=none,id=drive-system-disk-1,format=raw,media=cdrom -device ide-drive,drive=drive-system-disk-1,id=system-disk-1,bootindex=0 -acpitable file=/home/seabios/out/q35-acpi-dsdt.aml -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -vnc :10 -vga std
+++ This bug was initially created as a clone of Bug #895362 +++
Description of problem:
Win8 32/64 s3 state block by graphics, but qxl driver doesn't support win8, so file this bug to trace qxl driver will support win8 or not.
Version-Release number of selected component (if applicable):
kernel:2.6.32-352.el6.x86_64
qemu-kvm:qemu-kvm-0.12.1.2-2.349.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Boot up guest with follow command line:
#/usr/libexec/qemu-kvm -M rhel6.4.0 -cpu SandyBridge,+sep -m 8G -smp 4,sockets=2,cores=2,threads=1,maxcpus=16 -enable-kvm -name win8-32 -uuid 990ea161-6b67-47b2-b803-19fb01d30d12 -smbios type=1,manufacturer='Red Hat',product='RHEV Hypervisor',version=el6,serial=koTUXQrb,uuid=feebc8fd-f8b0-4e75-abc3-e63fcdb67170 -k en-us -rtc base=localtime,clock=host,driftfix=slew -no-kvm-pit-reinjection -monitor stdio -qmp tcp:0:6666,server,nowait -boot menu=on -bios /usr/share/seabios/bios.bin -drive file=/home/win8-32-backup.qcow2,if=none,id=drive-scsi-disk,format=qcow2,cache=none,werror=stop,rerror=stop -device virtio-scsi-pci,id=scsi0,addr=0x3 -device scsi-hd,drive=drive-scsi-disk,bus=scsi0.0,scsi-id=0,lun=0,id=scsi-disk,bootindex=1 -chardev socket,path=/tmp/isa-serial,server,nowait,id=isa1 -device isa-serial,chardev=isa1,id=isa-serial1 -vga qxl -spice port=5900,disable-ticketing -device virtio-balloon-pci,id=balloon1,bus=pci.0,addr=0x4 -netdev tap,id=hostnet0,downscript=no -device e1000,netdev=hostnet0,id=net0,mac=00:1d:45:0d:3a:fe,bus=pci.0,addr=0x5,bootindex=2 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0
2.execute "powercfg -a" in cmd.
Result:
...
Standby (S3)
An internal system component has disabled this standby state.
Graphics
...
Actual results:
s3 state disable by graphics
Expected results:
s3 state enabled
Additional info:
--- Additional comment from mazhang on 2013-01-15 01:43:20 EST ---
*** This bug has been marked as a duplicate of bug 895356 ***
--- Additional comment from langfang on 2013-03-07 22:11:53 EST ---
Test the same steps use windows2012 guest ,have same problem.
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.