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.

Bug 839674

Summary:	Revert back to a single seabios binary once s3/s4 configuration is in
Product:	Red Hat Enterprise Linux 6	Reporter:	Amit Shah <amit.shah>
Component:	seabios	Assignee:	Michal Novotny <minovotn>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	areis, flang, juzhang, michen, qzhang, shuang, virt-maint
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	seabios-0.6.1.2-25.el6	Doc Type:	Bug Fix
Doc Text:	Cause: Two copies of seabios, the BIOS for VMs, were built earlier. One (default) with s3/s4 support disabled, and second with the support enabled. Bug 827500 added a way to configure per-VM S3/S4 advertisement to guests, invalidating the need for two binaries. Consequence: There were two seabios binaries, with the non-default one enabling S3/S4 advertisement to guests. Fix: Create only one seabios binary that supports both, S3/S4 enabled and disabled modes via configuration parameters. Result: The non-default binary has been removed and the functionality for per-VM power management has been added.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-21 08:16:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	827500
Bug Blocks:	761491

Description Amit Shah 2012-07-12 14:20:35 UTC

Description of problem:

We disabled S3 and S4 advertisement in the default BIOS for RHEL6.3 (bug 809797), and had a separate bios binary that enabled that functionality.

With the ability to configure the s3/s4 advertisement per-VM (bug 827500), we can do away with the extra binary and have the feature enabled by default.

This bug ensures we revert back to a single binary, which is capable of enabling as well as disabling s3/s4 advertisement.

Comment 4 juzhang 2012-10-19 02:14:36 UTC

Verified this bug by using seabios-0.6.1.2-25.el6.x86_64

#rpm -ql seabios-0.6.1.2-25.el6.x86_64
/usr/share/doc/seabios-0.6.1.2
/usr/share/doc/seabios-0.6.1.2/COPYING
/usr/share/doc/seabios-0.6.1.2/COPYING.LESSER
/usr/share/doc/seabios-0.6.1.2/README
/usr/share/doc/seabios-0.6.1.2/TODO
/usr/share/seabios
/usr/share/seabios/bios.bin


Results:
Just one bin(/usr/share/seabios/bios.bin) left

Additional infos:
KVM QE will also run s3/s4 functional testing during rhel6.4 testing range, will report new bug if find new issues.

Comment 8 errata-xmlrpc 2013-02-21 08:16:08 UTC

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.

http://rhn.redhat.com/errata/RHBA-2013-0307.html