Date: Sun, 20 Dec 2020 23:10:22 +0000 From: Graham Perrin <grahamperrin@gmail.com> To: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: FreeBSD-CURRENT VirtualBox guest: EFI: lost the ability to boot Message-ID: <82854cb2-086c-f27d-d2e3-0681099b3bfe@gmail.com> In-Reply-To: <874b669a-9b8f-a457-653b-05b888419aae@gmail.com> References: <e0a39b2f-df6a-cc67-b302-00c0f35e1fbc@gmail.com> <CANCZdfo7-R96zEAObjr%2BPNTFVYFp_H-d31XGEtWT11udy1iPkw@mail.gmail.com> <874b669a-9b8f-a457-653b-05b888419aae@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 20/12/2020 00:31, Graham Perrin wrote: > > … With the boot maintenance manager of VirtualBox, I > <https://imgur.com/BTsj4zS>; navigated to loader.efi, added it as a > boot option (I lazily named it 'loader.efi') then set it as primary > <https://imgur.com/FYnHynr>; after which: > > * normal resets or restarts of the VM do successfully boot > > – and if I change the boot order to make 'EFI Hard Drive' primary and > 'loader.efi' last, boots fail (drop outs to the EFI shell). > > <https://imgur.com/MYLowDt>; and <https://imgur.com/G3SKMZh>; it appears > that 'EFI Hard Drive' and 'EFI DVD/CDROM' have the same path. Surely > wrong, I can think of nothing that might have caused this. > The boot manager of VirtualBox repeatedly lost the working boot option that I repeatedly added, leaving a non-working 'EFI Hard drive' option. I tried releasing the virtual disk, creating a new hard disk-less virtual machine with EFI enabled, then added the disk. First boot failed, dropped to EFI. It worked after I manually added a boot option to the boot manager but then again the working option was lost. Is this symptomatic of a bug with VirtualBox? This weekend I sort of lost the ability to think straight :-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?82854cb2-086c-f27d-d2e3-0681099b3bfe>