all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [RFC pve-kernel-meta 0/5] unify boot-mode config
Date: Tue,  1 Feb 2022 23:03:26 +0100	[thread overview]
Message-ID: <20220201220331.3491615-1-s.ivanov@proxmox.com> (raw)

This patchset is based on top of the pin/unpin/next-boot series (in it's v1)

It contains changes I would consider breaking (in the sense that as a user I
would expect to read about them in some Upgrade-notes, e.g. for a minor
release)

The changes should make it possible to boot a system irrespective of the
current boot-mode (UEFI/legacy) in the bios. Users should be able to change
their boot-mode in the bios, and the system should come up cleanly (and with
the same kernel-version as with the other boot-mode)

(currently changing boot-modes with p-b-t requrires booting from a live-CD)

patch 3 drops systemd-boot and uses grub for both boot-modes, hopefully
unifying the boot-experience and causing less confusion (currently I suggest
to look at the screen while booting to find out which boot-loader is used)

(Sadly systemd-boot (which I would prefer, justifiably)
won't get support for legacy boot)

* patch 1/5 renames a config-file (forgotten during the
  pve-efiboot->proxmox-boot rename)
* sending as RFC - since it's really just and idea (and I'm not sure it
  won't cause even more confusion/breakage in practice)
* very roughly tested on 2 VMs (manually reformatting the ESP to clean out
  systemd-boot) - both booted fine when changing their BIOS mode

as is it's definitely missing:
* a plan for transitioning current systems
* cleanup of the code (the changes are minimal for a POC)
* updated documentation
* quite a bit more testing (especially on real hardware)

Stoiko Ivanov (5):
  rename pve-efiboot-manual-kernels to proxmox-boot-manual-kernels
  proxmox-boot: add reinit subcommand
  proxmox-boot: keep EFI and legacy bootloaders in sync
  proxmox-boot: use grub for UEFI boot
  proxmox-boot: install grub in esp/EFI/BOOT/BOOTX64.EFI

 bin/grub-install-wrapper          | 19 +-------
 bin/proxmox-boot-tool             | 68 +++++++++++++++++++---------
 debian/pve-kernel-helper.postinst |  4 ++
 proxmox-boot/functions            |  2 +-
 proxmox-boot/zz-proxmox-boot      | 73 +++++--------------------------
 5 files changed, 64 insertions(+), 102 deletions(-)

-- 
2.30.2





             reply	other threads:[~2022-02-01 22:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 22:03 Stoiko Ivanov [this message]
2022-02-01 22:03 ` [pve-devel] [RFC pve-kernel-meta 1/5] rename pve-efiboot-manual-kernels to proxmox-boot-manual-kernels Stoiko Ivanov
2022-02-01 22:03 ` [pve-devel] [RFC pve-kernel-meta 2/5] proxmox-boot: add reinit subcommand Stoiko Ivanov
2022-02-01 22:03 ` [pve-devel] [RFC pve-kernel-meta 3/5] proxmox-boot: keep EFI and legacy bootloaders in sync Stoiko Ivanov
2022-02-01 22:03 ` [pve-devel] [RFC pve-kernel-meta 4/5] proxmox-boot: use grub for UEFI boot Stoiko Ivanov
2022-02-01 22:03 ` [pve-devel] [RFC pve-kernel-meta 5/5] proxmox-boot: install grub in esp/EFI/BOOT/BOOTX64.EFI Stoiko Ivanov
2022-02-02  9:03 ` [pve-devel] [RFC pve-kernel-meta 0/5] unify boot-mode config Thomas Lamprecht
2022-02-02 14:28   ` Stoiko Ivanov
2022-02-02 14:42     ` Thomas Lamprecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220201220331.3491615-1-s.ivanov@proxmox.com \
    --to=s.ivanov@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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