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.
(In reply to Vadim Rozenfeld from comment #6)
> Could you confirm that Hibernation is enabled in Power options?
It should blocked guest hibernation with "the firmware do not support hibernate(s4)" even it is enabled in Power options
(In reply to Mike Cao from comment #7)
> (In reply to Vadim Rozenfeld from comment #6)
> > Could you confirm that Hibernation is enabled in Power options?
>
> It should blocked guest hibernation with "the firmware do not support
> hibernate(s4)" even it is enabled in Power options
Hi Mike,
I mean, if the hibernate option is enabled and S4 is enabled in qemu line
like "global PIIX4_PM.disable_s4=0", can you hibernate the VM in this case?
Thanks,
Vadim.
(In reply to Vadim Rozenfeld from comment #8)
> (In reply to Mike Cao from comment #7)
> > (In reply to Vadim Rozenfeld from comment #6)
> > > Could you confirm that Hibernation is enabled in Power options?
> >
> > It should blocked guest hibernation with "the firmware do not support
> > hibernate(s4)" even it is enabled in Power options
>
> Hi Mike,
> I mean, if the hibernate option is enabled and S4 is enabled in qemu line
> like "global PIIX4_PM.disable_s4=0", can you hibernate the VM in this case?
>
> Thanks,
> Vadim.
Hi Vadim,
Hibernation is enabled in power options and could do hibernate with "-gloaal PIIX4_PM.disable_s4=0" in qemu line.
Jiang
Description of problem: winxp guest could do hibernate with "-global PIIX4_PM.disable_s4=1" on rhel6 host. Version-Release number of selected component (if applicable): Red Hat Enterprise Linux Server release 6.4 (Santiago) kernel-2.6.32-414.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.397.el6.x86_64 virtio-win-prewhql-0.1-68 spice-server-0.12.4-2.el6.x86_64 seabios-0.6.1.2-28.el6.x86_64 vgabios-0.6b-3.7.el6.noarch How reproducible: always Steps to Reproduce: 1.Boot guest /w "-global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1" /usr/libexec/qemu-kvm \ -M rhel6.5.0 \ -m 2G \ -smp 2,cores=2 \ -cpu cpu64-rhel6 \ -usb \ -device usb-tablet \ -drive file=winxp-32.raw,format=raw,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none \ -device virtio-blk-pci,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 \ -netdev tap,sndbuf=0,id=hostnet0,script=/etc/qemu-ifup,downscript=no \ -device rtl8139,netdev=hostnet0,mac=00:53:55:51:3c:a0,bus=pci.0,addr=0x6 \ -netdev tap,sndbuf=0,id=hostnet1,script=/etc/qemu-ifup0,downscript=no \ -device rtl8139,netdev=hostnet1,mac=00:53:45:51:3c:10,bus=pci.0,addr=0x7 \ -uuid 179270aa-45bb-4394-a9cf-3e8114d8556e \ -no-kvm-pit-reinjection \ -drive file=disk1.raw,if=none,id=drive-virtio1,cache=none,werror=stop,rerror=stop,format=raw \ -device virtio-blk-pci,drive=drive-virtio1,id=virtio-blk-pci1 \ -drive file=disk2.raw,if=none,id=drive-virtio2,cache=none,werror=stop,rerror=stop,format=raw \ -device virtio-blk-pci,drive=drive-virtio2,id=virtio-blk-pci2 \ -drive file=disk3.raw,if=none,id=drive-virtio3,cache=none,werror=stop,rerror=stop,format=raw \ -device virtio-blk-pci,drive=drive-virtio3,id=virtio-blk-pci3 \ -drive file=disk4.raw,if=none,id=drive-virtio4,cache=none,werror=stop,rerror=stop,format=raw \ -device virtio-blk-pci,drive=drive-virtio4,id=virtio-blk-pci4 \ -chardev socket,id=111a,path=/tmp/monitor-winxp-32-block,server,nowait \ -mon chardev=111a,mode=readline \ -name winxp32-block-48 \ -vnc :1 \ -vga cirrus \ -rtc base=localtime,clock=host,driftfix=slew \ -global PIIX4_PM.disable_s3=1 \ -global PIIX4_PM.disable_s4=1 \ -monitor stdio 2.do s4 3. Actual results: 1.in guest >powercfg -a The following sleep states are available on this system:Hiberate The following sleep states are not available on this system: standby (S1) standby (S2) standby (S3) 2.guest could do hibernate Expected results: guest could no do hibernate with "-global PIIX4_PM.disable_s4=1" Additional info: