MAAS

  1. Bug #2022084
  2. Comment #15

Comment 15 for bug 2022084

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Note that

10156333884e130e115c1089c9b15a02 ./EFI/BOOT/BOOTX64.EFI
10156333884e130e115c1089c9b15a02 ./EFI/redhat/shimx64.efi

behave and boot differently.

because shim when booted from /efi/boot/boox64.efi tries to lookup defaullt boot binary (uasualy grubx64.efi) and fails to find it, and then triggers /EFI/BOOT/fbx64.efi which then tries to create boot entries and boot them.

whereas ./EFI/redhat/shimx64.efi (which must be the RHEL shim, not ubuntu shim) will load and execute /EFI/redhat/grubx64.efi correctly.

Thus statements like "which maas tries anyway directly" is probably not right either, as maas should inspect boot entries and try to load the correct shim directly.