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 <ashishsingha@nvidia.com>

0 files changed, 0 insertions, 0 deletions