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.

Two suggestions for output improvements

1) When creating a brand new guest there's typically no nvram yet. AAVMF reports this as an error, but then corrects it and moves on fine. I.e.

ValidateFvHeader: Variable Store Guid non-compatible
NorFlashFvbInitialize: ERROR - The FVB Header is not valid. Installing a correct one for this volume.
Ftw: Work block header check error
Ftw: Work block header check error
Ftw: Both are invalid, init workspace

Status messages that don't say "error" might be nicer, as this is standard new guest behavior.

2) I once requested quieting AAVMF's output messages, so we now have the default (quiet) and also a verbose version that can be used. Now I'd like to suggest that the quiet one output at least one message though, something like "Starting UEFI...", because currently several seconds go by with no output - long enough to start suspecting a hang.

I posted a patch set

[edk2] [PATCH 0/3] soften some (non-)ERROR messages
http://thread.gmane.org/gmane.comp.bios.edk2.devel/2902

that should take care of the annoying messages in the current state of upstream.

With regard to the "Starting UEFI..." message, to be printed early in SEC, I think we should do that in downstream only.

Based on further discussion, I'll try to log a "Starting UEFI..."-like message in upstream too, on DEBUG_INFO level, and in downstream we could flip that to DEBUG_ERROR.

Posted v2:
http://thread.gmane.org/gmane.comp.bios.edk2.devel/2996

The first four patches of v2 have been committed.

The second half seems to be generally ignored, so we should carry those three of said four patches that we actually need in downstream only.

Fixed in RHEL-ALT-7.3.