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:
Version-Release number of selected component (if applicable):
3.10.0-50.el7.x86_64
qemu-kvm-rhev-1.5.3-19.el7.x86_64
seabios-1.7.2.2-4.el7.x86_64
seabios-bin-1.7.2.2-4.el7.noarch
virito-win-1.6.7-2
How reproducible:
100%
Steps to Reproduce:
1.Start VM with -global PIIX4_PM.disable_s3=0 -global PIIX_PM.disable_s4=0
CLI: /usr/libexec/qemu-kvm -M pc-i440fx-rhel7.0.0 -cpu SandyBridge -enable-kvm -m 2G -smp 2,cores=2 -name bcao_win-7-32-netkvm -uuid `uuidgen` -rtc base=localtime,clock=host,driftfix=slew -drive file=win7-32.qcow2,if=none,media=disk,werror=stop,rerror=stop,cache=none,format=qcow2,id=drive-disk0 -device ide-drive,drive=drive-disk0,id=disk0 -cdrom en_windows_7_ultimate_with_sp1_x86_dvd_u_677460.iso -fda /usr/share/virtio-win/virtio-win_x86.vfd -netdev tap,vhost=on,queues=4,id=netdev0 -device virtio-net-pci,netdev=netdev0,id=nic1,mq=on,vectors=17,mac=00:52:00:00:51:12 -spice port=5931,disable-ticketing -vga qxl -monitor stdio -usb -device usb-tablet,id=tablet0 -global PIIX4_PM.disable_s3=0 -global PIIX_PM.disable_s4=0
2.in the guest #powercfg -h on
Actual results:
It prompts system firmware does not support hibernation
Expected results:
no error prompts ,s4 should be enabled
Additional info:
s3 works fine
I cannot reproduce this bug with the same OS(win7-32).
package info:
virtio-win-1.6.7-2.el7.noarch
kernel-3.10.0-53.el7.x86_64
qemu-kvm-rhev-1.5.3-19.el7.x86_64
seabios-1.7.2.2-4.el7.x86_64
steps as comment 0
Actual result:
"powercfg -h on" can be executed correctly,and win7-32 guest can do S4 successfully.
(In reply to Gerd Hoffmann from comment #3)
> Most likely a acpi table issue.
> High chance that bug 1034876 (+bug 1034877) fix this.
> Michael?
Does it related to specified hosts ?all the guests can not do s4 on my hosts
> Does it related to specified hosts ?all the guests can not do s4 on my hosts
linux guests affected?
windows guests affected?
Unlikely that it is something in the host.
With command line, qemu-kvm and seabios being identical it most likely
something in the guest, such as different guest driver versions.
lijin? Mike? Can you try work out what the difference is?
(In reply to Gerd Hoffmann from comment #6)
> > Does it related to specified hosts ?all the guests can not do s4 on my hosts
>
> linux guests affected?
> windows guests affected?
>
> Unlikely that it is something in the host.
> With command line, qemu-kvm and seabios being identical it most likely
> something in the guest, such as different guest driver versions.
>
> lijin? Mike? Can you try work out what the difference is?
Seems there is a mistake in comment0's qemu-kvm command:
"-global PIIX_PM.disable_s4=0" should be "-global PIIX4_PM.disable_s4=0".
After change to the right command,guest can do S4.
It's weird that qemu-kvm can boot up even with a mistake command,why qemu-kvm didnot pop up some warning?
> > lijin? Mike? Can you try work out what the difference is?
>
> Seems there is a mistake in comment0's qemu-kvm command:
> "-global PIIX_PM.disable_s4=0" should be "-global PIIX4_PM.disable_s4=0".
> After change to the right command,guest can do S4.
Ok, good. So this isn't a bug.
> It's weird that qemu-kvm can boot up even with a mistake command,why
> qemu-kvm didnot pop up some warning?
-global settings simply go into global device configuration, basically same space where the compat properties for older machine types are living too. It is a perfectly valid thing for for compat properties to exist for devices not actually present in the virtual machine, or even devices not supported by rhel7 qemu-kvm binary. Which makes it difficult to catch that kind of error.