Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UEFI boot support #26

Open
olevole opened this issue Nov 30, 2018 · 7 comments
Open

UEFI boot support #26

olevole opened this issue Nov 30, 2018 · 7 comments

Comments

@olevole
Copy link

olevole commented Nov 30, 2018

it would be useful to have UEFI boot mode

@mhalden
Copy link

mhalden commented Dec 3, 2018

AFAIK the efi loader still doesn't have support for bootme/bootonce or anything equivalent which is needed to select the image to boot. I have heard some talk about using nvvars for this, but I'm not sure if anything has happened.

Upstream bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201788

@olevole
Copy link
Author

olevole commented Dec 3, 2018

Got it. Just wondering in which case it is used. Secure/safe BSDRP/firmware update?

@mhalden
Copy link

mhalden commented Dec 3, 2018

Updates are done by writing a full system image to second inactive partition and then reboot to that partition, this makes rollbacks very easy. This is done with the bootme/bootonce flags when using gpt or an equivalent flag in mbr which I don't remember the name of. (I believe bsdrp uses mbr by default.) Without a way to signal to the loader what partition they should boot from the update functionality won't work as-is since you're stuck on one of the images.

@olevole
Copy link
Author

olevole commented Mar 6, 2022

FYI: efibootmgr can be used to manage boot device, also UEFI VARS support for bhyve was committed recently: https://reviews.freebsd.org/D19976

@f-andrey
Copy link

f-andrey commented Mar 6, 2022

stand/efi/boot1: Add boot partition selection 207940 another waiting bug

@mhalden
Copy link

mhalden commented Mar 6, 2022

We currently use gptboot.efi instead of loader.efi, which implements support for the bootme and bootonce flags.

@ocochard
Copy link
Owner

This depend of the framework migration (nanobsd -> poudriere), the new image generated with poudriere will be dual BIOS/EFI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants