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

Add ability to delete all Linux Boot Manager entries #111

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

leivos-unikie
Copy link
Collaborator

@leivos-unikie leivos-unikie commented May 8, 2024

PR#585 'Change internal installation approach' is going to change the installation method so that it does not anymore just flash the ghaf image on nvme but builds it with nixos-installer. After PR#585 is merged ghaf-installer will create always a new Linux Boot Manager entry to UEFI boot order list and thus set the machine to boot from nvme regardless if USB SSD is connected or not.

With the introduced efiboot-mod test all Linux Boot Manager entries can be automatically removed from the UEFI boot order list. Wiping nvme clear can force to boot from USB but it is not possible to clear nvme if machine is locked to boot from nvme. Also it is not good to let the UEFI boot order list be flooded endlessly with Linux Boot Manager entries.

There is still a risk that the ghaf which the ghaf-installer has installed is broken and unbootable and new Linux Boot Manager entry is active. This would cause ci-test-automation not being able to boot automatically from nvme nor from USB SSD. That situation would need to be fixed manually via booting to UEFI BIOS and deactivating Linux Boot Manager entries. To avoid this happening plain ghaf image test should be ran first and only if the ghaf image is bootable then proceed to ghaf-installer tests.

Running efiboot-mod test while there is no Linux Boot Manager entries present in UEFI Boot order list does no harm.

Requirement for this PR to work is that efibootmgr is added to ghaf. This was done in tiiuae/ghaf#605

@leivos-unikie leivos-unikie changed the base branch from SP-4385 to main May 14, 2024 09:15
azbeleva and others added 5 commits August 21, 2024 08:51
Signed-off-by: Mariia Azbeleva <[email protected]>
Signed-off-by: Mariia Azbeleva <[email protected]>
Signed-off-by: Mariia Azbeleva <[email protected]>
Incoming ghaf PR#585 Change internal installation approach
is going to change the installation method significantly.
After the merge of PR#585 ghaf-installer will create always a new
Linux Boot Manager entry to UEFI boot order list and thus set the
machine to boot from nvme regardless if USB SSD is connected.

Here introduced efiboot-mod test will automatically remove all
Linux entries from the UEFI boot order list. Wiping nvme
clear could do the same but it is not possible to automatically
clear nvme if boot is locked to nvme. Also it is good to not let
the UEFI boot order list be flooded endlessly with Linux Boot
Manager entries.

There is still a risk that the ghaf which the ghaf-installer
has installed is broken and unbootable and new Linux Boot Manager
entry is active. This would cause ci-test-automation not being
able to boot automatically from nvme nor from USB SSD, and the
system should be fixed manually (Linux Boot Manager removed). To
avoid this happening plain ghaf image test should be ran first
and only if the ghaf image is bootable then proceed to
ghaf-installer tests.

Signed-off-by: Samuli Leivo <[email protected]>
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

Successfully merging this pull request may close these issues.

2 participants