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:
------------------------
win8 64 guest s4 fails with qxl, guest restart instead of recovering from s4. This is an known issue, but in RHEL6, we don't have a bug to track this problem. Btw, with default vga and vnc, s4 works correctly.
I fail to locate qxl component name, report under qemu-kvm, feel free to change it.
Version-Release number of selected component (if applicable):
---------------------------------------------------------------
virtio-win-1.6.6-1.el6
qxlwddm-0.2-1
qemu-kvm-rhev-0.12.1.2-2.406.el6.x86_64
How reproducible:
------------------
100%
Steps to Reproduce:
--------------------
1.CMD:
/usr/libexec/qemu-kvm -enable-kvm -M rhel6.5.0 -smp 4 -m 4G -name rhel6.3-64 -uuid 3f2ea5cd-3d29-48ff-aab2-23df1b6ae213 -drive file=win8-64-virtio.qcow2,cache=none,if=none,rerror=stop,werror=stop,id=drive-virtio-disk0,format=qcow2,aio=native -device virtio-blk-pci,drive=drive-virtio-disk0,id=device-virtio-disk0,bootindex=1 -netdev tap,script=/etc/qemu-ifup,id=netdev0 -device virtio-net-pci,netdev=netdev0,id=device-net0,mac=aa:54:00:11:22:33 -boot order=cd -monitor stdio -readconfig ich9-ehci-uhci.cfg -device usb-tablet,id=input0 -chardev socket,id=s1,path=/tmp/s1,server,nowait -device isa-serial,chardev=s1 -monitor tcp::1234,server,nowait -device usb-hub,id=hub -device usb-storage,drive=drive-usb1,id=device-usb1,removable=on -drive file=disk1,if=none,id=drive-usb1,media=disk,format=qcow2,cache=none,aio=threads -device usb-kbd,id=usb-kbd -device usb-mouse,id=usb-mouse -vga qxl -global qxl-vga.revision=3 -spice port=5920,disable-ticketing -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0
2.
(qemu) system_powerdown
Actual results:
------------------
re-run qemu-kvm with same CMD, guest restart instead of recovering from s4.
As default vga and vnc works well for s4, so please help move to correct component if we are wrong. Filed to qemu-kvm first because we need bz to track the issue and we are not sure which is the proper component for the new qxlwddm build. Thanks.