On Wed, Feb 19, 2014 at 04:10:15PM +0100, Laszlo Ersek wrote:
> The phenomenon described in
>
> https://fedoraproject.org/wiki/Unified_Extensible_Firmware_Interface#You_have_failed_to_provide_all_existing_bootloader_entries_when_changing_the_boot_order
>
> is what I witness under OVMF too (and have been, for a long time).
>
> Apparently this should be a bug somewhere in
> "IntelFrameworkModulePkg/Universal/BdsDxe", which we trigger very
> heavily in OVMF, because OVMF always rewrites the BootOrder variable and
> always drops at least some of the auto-generated options from it. (This
> is done to serve the boot order specs on the qemu command line.)
>
> I used to think this was some obscure problem related to OVMF that we
> didn't find the time (or motivation) to track down. But Adam's paragraph
> in the Fedora wiki article suggests that the bug is present in UEFI
> firmwares shipping on real hardware, which to me implies the bug is in
> IntelFrameworkModulePkg.
Yeah, that sounds likely enough. FWIW I added "--keep" to upstream
efibootmgr last week to help people work around this problem. Testing
would be appreciated.
--
Peter
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
