Date: Sun, 20 Dec 2020 00:31:08 +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: <874b669a-9b8f-a457-653b-05b888419aae@gmail.com> In-Reply-To: <CANCZdfo7-R96zEAObjr%2BPNTFVYFp_H-d31XGEtWT11udy1iPkw@mail.gmail.com> References: <e0a39b2f-df6a-cc67-b302-00c0f35e1fbc@gmail.com> <CANCZdfo7-R96zEAObjr%2BPNTFVYFp_H-d31XGEtWT11udy1iPkw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19/12/2020 23:20, Warner Losh wrote: > > > On Sat, Dec 19, 2020 at 2:21 PM Graham Perrin <grahamperrin@gmail.com > <mailto:grahamperrin@gmail.com>> wrote: > > With VirtualBox on an r368589 host I installed the latest (17th > December) snapshot of 13.0-CURRENT in a guest machine. I set the > guest > to EFI before installation, and chose GPT (UEFI) during installation. > > After installing KDE Plasma etc., the guest worked for a short > while but > then failed to boot. Screenshots at <https://imgur.com/a/xoYHwbT > <https://imgur.com/a/xoYHwbT>>; > scroll down to 17:49:06 for a shot of a failure. > > Is this maybe another case of bug 251866? > <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251866 > <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251866>>; > > > Try the next snapshot... I just fixed this in -current... or so I > claim. Please validate my claim. :) > > Though unless there's a bunch of stuff where the boot loader fails and > then loads the shell, maybe not... > > You need to check you ESP to make sure there's a bootx64.efi in > \efi\boot\ as well... that would also kick you into the shell... > > Warner Thanks, will the next snapshot be on/around 24th December? Or later, with the festive season? In the meantime I added four shots to the album. 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. Graham
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?874b669a-9b8f-a457-653b-05b888419aae>