Red Hat Bugzilla – Bug 1342342
RHEL Doc error about S3/S4 operations for guest
Last modified: 2016-11-03 14:46:21 EDT
Description of problem: RHEL Doc error about S3/S4 operations for guest Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1.Check the RHEL doc /usr/share/doc/libvirt-docs-1.3.2/html/formatdomain.html [root@localhost html]# cat /usr/share/doc/libvirt-docs-1.3.2/html/formatdomain.html | grep S3 -A3 for S3 (suspend-to-disk) and S4 (suspend-to-mem) ACPI sleep states. If nothing is specified, then the hypervisor will be left with its default value.</dd></dl> <h3> 2.Also check the libvirt.org, it is also the same with the RHEL doc Actual results: the Doc error is that S3 (suspend-to-disk) and S4 (suspend-to-mem) Expected results: S3 (suspend-to-mem) and S4 (suspend-to-disk) Additional info: N/A
Fixed upstream: commit 442cdb817e0d29c94f98bf9c534d609f7d10380a Author: Jingjing Shao <jishao@redhat.com> Date: Wed Jun 15 11:14:32 2016 +0800 doc: Fix explanation of S3 and S4 states Explanation of S3 and S4 states was swapped.
Reproduce this bug with libvirt-1.3.2-1.el7.x86_64 Steps to reproduce: 1.Check the RHEL doc #cat /usr/share/doc/libvirt-docs-1.3.2/html/formatdomain.html |grep 'S3 ' -A3 for S3 (suspend-to-disk) and S4 (suspend-to-mem) ACPI sleep states. If nothing is specified, then the hypervisor will be left with its default value.</dd></dl> <h3> ---------------------- Verirfy this bug with libvirt-2.0.0-1.el7.x86_64 Steps to verify: 1.Check the RHEL doc #cat /usr/share/doc/libvirt-docs-2.0.0/html/formatdomain.html|grep 'S3 ' -A3 for S3 (suspend-to-mem) and S4 (suspend-to-disk) ACPI sleep states. If nothing is specified, then the hypervisor will be left with its default value.</dd></dl> <h3> 2.Also check the libvirt.org : http://libvirt.org/formatdomain.html#elementsPowerManagement : Power Management pm These elements enable ('yes') or disable ('no') BIOS support for S3 (suspend-to-mem) and S4 (suspend-to-disk) ACPI sleep states. If nothing is specified, then the hypervisor will be left with its default value. Since the result is as expected, mark this bug verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-2577.html