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:
Found this bug when replied bug 949900.
According to Bug 1111107 that Q35 is no longer "tech preview" in RHEL7.x and is simply now unsupported (it will only be in qemu-kvm-rhev). And checked with Amit in IRC that both (q35 and s3/s4) are techpreview.
Version-Release number of selected component (if applicable):
# uname -r && rpm -q qemu-kvm-rhev
3.10.0-211.el7.x86_64
qemu-kvm-rhev-2.1.2-14.el7.x86_64
guest info:
3.10.0-211.el7.x86_64
How reproducible:
3/3
Steps to Reproduce:
1.boot up a rhel guest with "spcie+ qxl" under Q35 chipset without "-global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0" specified in command line.
2.do S3 and resume it, check the VM status and guest kernel log.
3.do second S3.
Actual results:
after step 2, do s3 and resume it successfully.
after step 3, it fail to s3 again and the vm status still running.
Expected results:
it can repeat do s3 and resume it successfully.
Additional info:
# /usr/libexec/qemu-kvm -S -M q35 -cpu SandyBridge -enable-kvm -m 4096 -smp 2,sockets=2,cores=1,threads=1 -no-kvm-pit-reinjection -name sluo-test -uuid ed09fa10-6ffe-4811-a42f-0294afcb5a42 -rtc base=localtime,clock=host,driftfix=slew -drive file=/home/rhel7-64.qcow2,if=none,id=drive-system-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop,serial=QEMU-DISK1 -device virtio-blk-pci,drive=drive-system-disk,id=system-disk,bus=pcie.0,addr=0x04,bootindex=1 -netdev tap,id=hostnet0,vhost=off,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=08:2e:5f:0a:0d:b1,bus=pcie.0,addr=0x5,bootindex=2 -balloon none -usb -device usb-tablet,id=input0 -serial unix:/tmp/ttyS0,server,nowait -qmp tcp:0:4444,server,nowait -k en-us -boot menu=on -spice disable-ticketing,port=5931 -vga qxl -monitor stdio