Date: Sat, 19 Dec 2020 16:20:01 -0700 From: Warner Losh <imp@bsdimp.com> To: Graham Perrin <grahamperrin@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: FreeBSD-CURRENT VirtualBox guest: EFI: lost the ability to boot Message-ID: <CANCZdfo7-R96zEAObjr%2BPNTFVYFp_H-d31XGEtWT11udy1iPkw@mail.gmail.com> In-Reply-To: <e0a39b2f-df6a-cc67-b302-00c0f35e1fbc@gmail.com> References: <e0a39b2f-df6a-cc67-b302-00c0f35e1fbc@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 19, 2020 at 2:21 PM Graham Perrin <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>; > 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>; > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfo7-R96zEAObjr%2BPNTFVYFp_H-d31XGEtWT11udy1iPkw>