else this fails with secureboot, where the entry point must be shim and not
grub.
Signed-off-by: Fabian Grünbichler <f.gruenbich...@proxmox.com>
---
tested by using the "Hard Disk" boot option, instead of the (higher priority)
'proxmox' one when booting a freshly installed system using LVM and Secure Boot
Proxmox/Install.pm | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Proxmox/Install.pm b/Proxmox/Install.pm
index 8825699..c99748c 100644
--- a/Proxmox/Install.pm
+++ b/Proxmox/Install.pm
@@ -605,8 +605,10 @@ sub prepare_grub_efi_boot_esp {
}
# also install fallback boot file (OVMF does not boot without)
mkdir("$targetdir/boot/efi/EFI/BOOT");
- syscmd("cp $targetdir/boot/efi/EFI/proxmox/grubx64.efi
$targetdir/boot/efi/EFI/BOOT/BOOTx64.EFI") == 0 ||
+ syscmd("cp $targetdir/boot/efi/EFI/proxmox/*.efi
$targetdir/boot/efi/EFI/BOOT/") == 0 ||
die "unable to copy efi boot loader\n";
+ syscmd("mv $targetdir/boot/efi/EFI/BOOT/shimx64.efi
$targetdir/boot/efi/EFI/BOOT/BOOTx64.efi") == 0 ||
+ die "unable to setup default efi boot loader\n";
};
my $err = $@;
--
2.39.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
