Difference between revisions of "OVMF/UEFI Boot Entries"
|Line 62:||Line 62:|
Latest revision as of 07:26, 28 June 2022
If a VM boots via OVMF (UEFI), the firmware has to know which bootloader it has to start from the ESP.
When no boot entries exist in the EFIVARS store, it tries to load the fallback
$ESP/EFI/BOOT/BOOTX64.efi loader. Should that also fail, the VM gets booted into the EFI Shell
Add a Boot Option
- Start-up the VM and press ESC to get into the OVMF menu.
- Then "Boot Maintenance Manager" -> "Boot Options" -> "Add Boot Option" -> choose Disk with the Efi System Partition.
- Now find the EFI executable, for example for Debian:
EFI/debian/grubx64.efior for Fedora:
- Name it ("Input the description") and "Commit Change"
- Use "Change Boot Order" to order the new entry to the top.
To add an entry of an existing bootloader go into the OVMF Menu by pressing 'ESC' during boot. Then select 'Boot Maintenance Manager':
Select 'Boot Options':
Select 'Add Boot Option':
Choose the Hard Drive with the ESP:
Navigate the folder structure to your bootloader (EFI/debian/shimx64.efi in this example)
After that, enter a name and commit:
To make it the default boot entry, you now have to change the boot order:
Press enter, select the boot entry with the arrow keys and move it up and down with '+' and '-' respectively. Then press enter again and commit your changes:
The last step is to reset the VM via OVMF, after that it should boot using the just configured boot entry.