Date: Sat, 19 Dec 2020 23:29:52 +0200 From: Toomas Soome <tsoome@me.com> To: Graham Perrin <grahamperrin@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD-CURRENT VirtualBox guest: EFI: lost the ability to boot Message-ID: <34449A43-79AD-4644-8A9A-ACA693E01287@me.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 19. Dec 2020, at 23:21, Graham Perrin <grahamperrin@gmail.com> = wrote: >=20 > 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. >=20 > 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. >=20 > Is this maybe another case of bug 251866? = <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251866>; >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org=E2=80=9D Do You mean the screenshot with UEFI shell? You usually do drop to UEFI = shell when firmware did decide it can not start your efi application. = Other option is, we got failure and did exit loader.efi. it may help if you attempt to start loader.efi manually from ESP, by = entering: FS0:/efi/boot/bootx64.efi =E2=80=94 there may appear some = messages... rgds, toomas=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34449A43-79AD-4644-8A9A-ACA693E01287>