Re: FreeBSD-CURRENT VirtualBox guest: EFI: lost the ability to boot

[Graham Perrin]

On 20/12/2020 00:31, Graham Perrin wrote:


… With the boot maintenance manager of VirtualBox, I 
 navigated to loader.efi, added it as a 
boot option (I lazily named it 'loader.efi') then set it as primary 
 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).


 and  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 :-)

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: FreeBSD-CURRENT VirtualBox guest: EFI: lost the ability to boot

[Toomas Soome]

> On 19. Dec 2020, at 23:21, Graham Perrin  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 ; scroll down to 
> 17:49:06 for a shot of a failure.
> 
> Is this maybe another case of bug 251866? 
> 
> 
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org”


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  — there may appear some messages...

rgds,
toomas
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: FreeBSD-CURRENT VirtualBox guest: EFI: lost the ability to boot

[Graham Perrin]

On 19/12/2020 23:20, Warner Losh wrote:



On Sat, Dec 19, 2020 at 2:21 PM Graham Perrin > 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 >;
scroll down to 17:49:06 for a shot of a failure.

Is this maybe another case of bug 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  
navigated to loader.efi, added it as a boot option (I lazily named it 
'loader.efi') then set it as primary  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).


 and  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

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: FreeBSD-CURRENT VirtualBox guest: EFI: lost the ability to boot

[Warner Losh]

On Sat, Dec 19, 2020 at 2:21 PM Graham Perrin 
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 ;
> scroll down to 17:49:06 for a shot of a failure.
>
> Is this maybe another case of bug 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
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"