Branch: refs/heads/master
Home: https://github.com/tianocore/edk2
Commit: 55832cf7a8c61d5a0864b22ed1a4192fc3cc8e02
https://github.com/tianocore/edk2/commit/55832cf7a8c61d5a0864b22ed1a4192fc3cc8e02
Author: Ashish Singhal <[email protected]>
Date: 2026-09-04 (Fri, 04 Sep 2026)
Changed paths:
M ArmVirtPkg/ArmVirtQemu.dsc
Log Message:
-----------
ArmVirtPkg/ArmVirtQemu: Default the boot timeout to 0 like OVMF
ArmVirtQemu.dsc sets PcdPlatformBootTimeOut to 3 seconds as a
PcdsDynamicDefault and to 5 seconds as the default of the HII-backed
"Timeout" variable. With a fresh variable store, and unless QEMU is
started with "-boot menu=on", an AArch64 guest therefore idles for
about 5 seconds in BDS on every boot. OVMF defaults the same PCD to
0 and boots immediately under the same conditions.
The timeout logic is otherwise identical on both platforms: the
PlatformBootManagerLib calls GetFrontPageTimeoutFromQemu(), which
honours "-boot menu=on[,splash-time=N]" and falls back to the platform
default, and hands the result to the common BdsDxe wait loop. Only
the DSC default differs.
The delay is a measurable penalty for short-lived AArch64 VMs. In a
time-to-ssh comparison a QEMU guest on an AArch64 host took 14.6s
versus 11.8s on x86; with the timeout at 0 the AArch64 guest came in
at 8s.
Set both defaults to 0 to match OVMF. Users who want the boot menu
prompt keep the same controls as on x86: "-boot menu=on" still yields
a 3 second (or splash-time) wait, and because the PCD remains backed
by the UEFI "Timeout" variable, "efibootmgr -t N" from the guest
continues to work.
Fixes: https://github.com/tianocore/edk2/issues/13068
Signed-off-by: Ashish Singhal <[email protected]>
To unsubscribe from these emails, change your notification settings at
https://github.com/tianocore/edk2/settings/notifications
_______________________________________________
edk2-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-commits
