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.
Description of problem:
only machine type q35 support S3/S4 for win8 guest. other machine type don't support in RHEL7.0. I attached two snapshots.
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-1.5.3-10.el7.x86_64
3.10.0-35.el7.x86_64
qxl version:
qxlwddm-0.2
How reproducible:
100%
Steps to Reproduce:
1.qemu-kvm command line
/usr/libexec/qemu-kvm -M pc -cpu SandyBridge -enable-kvm -m 10G -smp 8,sockets=2,cores=4,threads=1 -usb -device usb-tablet,id=input0 -name sluo -uuid ec15da0a-e8a7-42f4-905a-78fed78fd8fd -rtc base=localtime,clock=host,driftfix=slew -device ahci,id=ahci0,addr=0x04 -drive file=/home/win8.1-64.qcow2,if=none,id=drive-sata-disk-0-0,format=qcow2 -device ide-drive,bus=ahci0.0,unit=0,drive=drive-sata-disk-0-0,id=sata-disk-0-0 -netdev tap,script=/etc/qemu-ifup,id=netdev0 -device rtl8139,netdev=netdev0,id=virtio-net-pci0,mac=e4:1f:13:eb:40:24,addr=0x5 -balloon virtio -vnc :1 -monitor stdio -boot menu=on -spice disable-ticketing,port=5931 -vga qxl -global qxl-vga.revision=3 -qmp tcp:0:4444,server,nowait -usb -device usb-mouse,id=mouse -sandbox on -drive file=/root/interface/virtio.qcow2,if=none,id=drive-sata-disk-0-1,format=qcow2 -device virtio-blk-pci,drive=drive-sata-disk-0-1,id=sata-disk-0-1 -drive file=/root/interface/scsi.qcow2,if=none,id=drive-scsi-disk,format=qcow2,aio=native -device virtio-scsi-pci,id=scsi0 -device scsi-hd,drive=drive-scsi-disk,id=data-disk -chardev socket,id=qmp_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1,server,nowait -mon chardev=qmp_id_qmpmonitor1,mode=control -drive file=qxl.iso,if=none,media=cdrom,format=raw,id=drive-ide1-0-2 -device ide-drive,drive=drive-ide1-0-2,id=ide1-0-2,bus=ide.0,unit=0
2.shutdown guest and restart guest with q35 machine type and the same command line as step1
3.
Actual results:
after step1
win8 guest can not do S3/S4(not support)
after step2
win8 guest can do S3/S4(support)
Expected results:
linux guest don't hit this issue. I only tested win8 64/32 bit guest. not test other windows guest.
Additional info:
Re-tested this issue with -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0. Before missing this option in cli.
result:
win8 guest support s3 & s4. but guest show black screen when doing s3/s4(As s3/s4 have more bugs, It is existing bug 1043379).