This is the easiest to implement and it works well enough. Personally, the solution I most often use is to rename the boot loader from the OS's default to EFI\BOOT\boot圆4.efi. It's likely to be frustrating without precise instructions because there are a lot of non-obvious pitfalls you must avoid. I don't know of a concise description of how to do this on the web, offhand, and I don't have time to write it up here. Register the boot loader with the VirtualBox firmware by using the shell's tools.Type cd EFI\ is the boot loader's name, such as grub圆4.efi for most Linux installations.Type fs0: to access the first filesystem, which is usually the ESP.
You can launch the boot loader manually by using the EFI shell:.There are several ways to deal with this problem, including: The result is that the VM boots up into the EFI shell by default. One quirk of VirtualBox is that it usually forgets these boot manager entries.
Most OSes register these boot loaders with the firmware, which remembers them and boots them automatically.
If you've installed an OS in your VirtualBox session, chances are it installed a boot loader on the EFI System Partition (ESP). You can exit from the shell by typing exit however, in the case of VirtualBox, this will probably bring you to an EFI menu that can be just as confusing. It lets you view, delete, edit, and rename files, to update EFI boot manager entries, and so on. The EFI shell is a command-line tool similar in concept to bash in Linux/Unix/OS X or a Command Prompt window in Windows.
0 kommentar(er)
