Red Hat Bugzilla – Bug 1270279
AAVMF: output improvements
Last modified: 2017-10-10 06:58:37 EDT
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.