--- Comment #28 from lists dev <lists(a)ssl-mail.com> ---
startup.nsh is for UEFI shell, and it only works when
BDS boots UEFI shell.
For the one-time boot, enter the "Boot
Maintenance Manager" and choose "Boot
From File" to find the specific efi image. To create a permanent boot
option, choose "Boot Options" -> "Add Boot Option". You can change
order with "Boot Options" -> "Change Boot Order". But it seems
has problem to save NvVars correctly, I'm not sure if the boot option will
In Dom0, I can (still) easily set 'EFI Shell' to Boot Order == 0000.
With startup.nsh in place, on boot it does -- as you explain -- fall through to
startup.nsh after ~4 sec delay. Works well if needed.
In the Guest, I am not able to get the boot option to stick.
Is it possible, from within chroot, to write a correct set of NvVars directly,
and get the guest-boot process to use them?
I can certainly use efibootmgr to write to file, but am not clear if that's
sufficient, or what the recommended options should be.
You are receiving this mail because:
You are on the CC list for the bug.