Will do the right thing, but the intial grub2-install creates an entry which needs to be removed which means finding the entry, deleting and recreating one. Additionally while we do know the disk (it's the grub target disk we get passed) it's not immediately clear what partition EFI is on, efibootmgr defaults to 1 but in curtin we could have this anywhere on the GPT layout.
it's a real shame that grub2-install can't take a loader parameter when it's updating nvram.
We could pass the no-nvram update to grub2-install which would prevent creating the entry; but we still need to look up the right disk and partition values.
This will take a bit more time to sort out a clean way to do this.
Not super happy about this. Shim-x64 is installed and provides the efi file.
grub2-install on centos/redhat doesn't automatically select the shimx64.efi file as the loader.
AFAICT, the only way to make this happen is to do this via efibootmgr:
% efibootmgr -c -w -L centos -d /dev/vda -p 1 -l \\EFI\\ centos\ \shimx64. efi
Will do the right thing, but the intial grub2-install creates an entry which needs to be removed which means finding the entry, deleting and recreating one. Additionally while we do know the disk (it's the grub target disk we get passed) it's not immediately clear what partition EFI is on, efibootmgr defaults to 1 but in curtin we could have this anywhere on the GPT layout.
it's a real shame that grub2-install can't take a loader parameter when it's updating nvram.
We could pass the no-nvram update to grub2-install which would prevent creating the entry; but we still need to look up the right disk and partition values.
This will take a bit more time to sort out a clean way to do this.