all lists on lists.proxmox.com
 help / color / mirror / Atom feed
* [pve-devel] [PATCH kernel-helper] grub-install: provide --removable to grub-install
@ 2023-11-21 16:56 Stoiko Ivanov
  2023-11-21 17:41 ` [pve-devel] applied: " Thomas Lamprecht
  0 siblings, 1 reply; 2+ messages in thread
From: Stoiko Ivanov @ 2023-11-21 16:56 UTC (permalink / raw)
  To: pve-devel

noticed while installing with secure-boot enabled on ZFS RAID1:
The system has no entry to boot from in the efi-vars and
the entry for the first disk simply does not boot (I assume OVMF tries
the default bootx64.efi.

Since `proxmox-boot-tool init` should only be done for ESPs, which are
dedicated to proxmox products I don't think that this will cause many
regressions

For comparison - our installer has done the manual equivalent of the
--removable option for installs on ext4 for quite a while.

minimally tested on a VM during install.

Reported-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
---
ftr: In Mira's tests a RAID1 install on ZFS booted fine as long as both
disks were added to the boot-options (which I cannot explain)

 src/bin/proxmox-boot-tool | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/bin/proxmox-boot-tool b/src/bin/proxmox-boot-tool
index befa2fb..e70850a 100755
--- a/src/bin/proxmox-boot-tool
+++ b/src/bin/proxmox-boot-tool
@@ -166,6 +166,7 @@ init_bootloader() {
 				--target x86_64-efi \
 				--no-floppy \
 				--efi-directory "${esp_mp}" \
+				--removable \
 				--bootloader-id 'proxmox' \
 				"/dev/$PKNAME"
 		else
-- 
2.39.2





^ permalink raw reply	[flat|nested] 2+ messages in thread

* [pve-devel] applied: [PATCH kernel-helper] grub-install: provide --removable to grub-install
  2023-11-21 16:56 [pve-devel] [PATCH kernel-helper] grub-install: provide --removable to grub-install Stoiko Ivanov
@ 2023-11-21 17:41 ` Thomas Lamprecht
  0 siblings, 0 replies; 2+ messages in thread
From: Thomas Lamprecht @ 2023-11-21 17:41 UTC (permalink / raw)
  To: Proxmox VE development discussion, Stoiko Ivanov

Am 21/11/2023 um 17:56 schrieb Stoiko Ivanov:
> noticed while installing with secure-boot enabled on ZFS RAID1:
> The system has no entry to boot from in the efi-vars and
> the entry for the first disk simply does not boot (I assume OVMF tries
> the default bootx64.efi.
> 
> Since `proxmox-boot-tool init` should only be done for ESPs, which are
> dedicated to proxmox products I don't think that this will cause many
> regressions
> 
> For comparison - our installer has done the manual equivalent of the
> --removable option for installs on ext4 for quite a while.
> 
> minimally tested on a VM during install.
> 
> Reported-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> ftr: In Mira's tests a RAID1 install on ZFS booted fine as long as both
> disks were added to the boot-options (which I cannot explain)
> 
>  src/bin/proxmox-boot-tool | 1 +
>  1 file changed, 1 insertion(+)
> 
>

applied, thanks!




^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-11-21 17:41 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-11-21 16:56 [pve-devel] [PATCH kernel-helper] grub-install: provide --removable to grub-install Stoiko Ivanov
2023-11-21 17:41 ` [pve-devel] applied: " Thomas Lamprecht

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal