From: "Gerd Hoffmann via groups.io" <kraxel=redhat.com@groups.io>
To: devel@edk2.groups.io, rebecca@bsdio.com
Cc: ardb+tianocore@kernel.org, Ruiyu Ni <ruiyu.ni@intel.com>,
Ray Ni <ray.ni@intel.com>
Subject: Re: [edk2-devel] OVMF vs ArmVirt: what to do when unable to boot (print a message or drop into UiApp)
Date: Mon, 16 Jun 2025 12:54:37 +0200 [thread overview]
Message-ID: <yxvoltqzxs5afz6j64p2fm3extn47ghecfuqlpjcadfon2ej2e@irdok5kgzmkj> (raw)
In-Reply-To: <13af1623-2925-4017-8eb4-2d8775e2b7ff@bsdio.com>
On Sat, Jun 14, 2025 at 08:44:35PM -0600, Rebecca Cran wrote:
> I've been testing some UI changes in OVMF and was surprised when instead of
> launching into the UiApp I got a message:
>
> BdsDxe: No bootable option or device was found
> BdsDxe: Press any key to enter the Boot Manager Menu
ovmf prints the boot attempts to the console, via
OvmfPkg/Library/PlatformBmPrintScLib/, for better diagnoses of boot
failures. This 'wait for keypress' allows to read those messages before
the screen gets overwritten by whatever is launched next.
recent update (new in 2025-05) is to launch the boot menu app instead of
efi shell or firmware setup app, so when something goes wrong the user
gets a menu with choices instead of being dropped somewhere
automatically. This also allows the host (i.e. qemu) to allow or deny
access to efi shell / firmware setup.
take care,
Gerd
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121419): https://edk2.groups.io/g/devel/message/121419
Mute This Topic: https://groups.io/mt/113649673/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2025-06-16 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-15 2:44 [edk2-devel] OVMF vs ArmVirt: what to do when unable to boot (print a message or drop into UiApp) Rebecca Cran
2025-06-16 10:54 ` Gerd Hoffmann via groups.io [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yxvoltqzxs5afz6j64p2fm3extn47ghecfuqlpjcadfon2ej2e@irdok5kgzmkj \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox