public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-kernel-meta 0/5] proxmox-boot: add kernel pinning functionality (#3761)
Date: Tue, 1 Feb 2022 10:58:58 +0100	[thread overview]
Message-ID: <2ed841ff-3b30-30d2-da72-061686deb9d5@proxmox.com> (raw)
In-Reply-To: <20220131175918.2099575-1-s.ivanov@proxmox.com>

Tested systemd-boot (uefi) on physical hardware with PVE and grub in a PMG VM.

(un)Pinning and setting next-boot worked fine.

Tested-By: Aaron Lauterer <a.lauterer@proxmox.com>

On 1/31/22 18:59, Stoiko Ivanov wrote:
> The following series adds:
> * proxmox-boot-tool kernel pin <kabi-version> (to permanently set the
>    default entry of the respective bootloader)
> * proxmox-boot-tool kernel unpin (to undo a previous pin)
> * proxmox-boot-tool kernel next-boot (to do a pin+touch a file, which causes
>    an unpin on next boot)
> 
> This is the first functionality which is available for 'regular grub-setups'
> (i.e. systems setup with lvm-thin with our ISO or systems installed on top
> of plain debian) as well.
> 
> The first two patches are cleanup+refactoring (and should not change any
> functionality)
> 
> The choices (those I think might benefit from a bit of feedback) for this
> implementation were:
> * for grub - automaticially rewrite '/etc/default/grub' (as this is where
>    I'd look to check whether some default is set)
> * for systemd - set the entry in the loader.conf and not in the efivars
>    (`bootctl set-default/set-once`) - mostly from my bias towards config
>    files instead of UEFI vars (depending on implementation quality of the
>    UEFI) - another reason was to keep the implementation close for both
>    boot-loaders
> * for p-b-t booted systems the need to run `p-b-t refresh` manually
>    afterwards (following the behavior of `p-b-t kernel add/remove`) could
>    be changed to invoking the refresh directly (as with non-p-b-t booted
>    systems). Especially since it might make sense to 'add' multiple kernels
>    and then do the mount+copy+configupdate only once, whereas you can only
>    pin on version anyways
> 
> Tested on three VMs installed from the 7.1 ISO (UEFI+ZFS, legacy+ZFS,
> UEFI+lvm-thin).
> 
> Stoiko Ivanov (5):
>    proxmox-boot: drop unused potential_esps function
>    proxmox-boot: add get_first_line_from_file helper and use it
>    proxmox-boot: fix #3671 add pin/unpin for kernel-version
>    proxmox-boot: add kernel next-boot command
>    proxmox-boot: add pin/unpin functionality for non-p-b-t systems
> 
>   bin/proxmox-boot-tool                     | 65 +++++++++++++++++++++--
>   debian/pve-kernel-helper.install          |  1 +
>   debian/rules                              |  3 ++
>   proxmox-boot/Makefile                     |  4 ++
>   proxmox-boot/functions                    | 46 ++++++++++++++++
>   proxmox-boot/proxmox-boot-cleanup.service | 15 ++++++
>   proxmox-boot/zz-proxmox-boot              | 15 +++---
>   7 files changed, 137 insertions(+), 12 deletions(-)
>   create mode 100644 proxmox-boot/proxmox-boot-cleanup.service
> 




      parent reply	other threads:[~2022-02-01  9:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 17:59 Stoiko Ivanov
2022-01-31 17:59 ` [pve-devel] [PATCH pve-kernel-meta 1/5] proxmox-boot: drop unused potential_esps function Stoiko Ivanov
2022-02-04 16:47   ` [pve-devel] applied: " Thomas Lamprecht
2022-01-31 17:59 ` [pve-devel] [PATCH pve-kernel-meta 2/5] proxmox-boot: add get_first_line_from_file helper and use it Stoiko Ivanov
2022-02-04 16:47   ` [pve-devel] applied: " Thomas Lamprecht
2022-01-31 17:59 ` [pve-devel] [PATCH pve-kernel-meta 3/5] proxmox-boot: fix #3671 add pin/unpin for kernel-version Stoiko Ivanov
     [not found]   ` <<20220131175918.2099575-4-s.ivanov@proxmox.com>
2022-02-01 11:35     ` Fabian Grünbichler
2022-01-31 17:59 ` [pve-devel] [PATCH pve-kernel-meta 4/5] proxmox-boot: add kernel next-boot command Stoiko Ivanov
2022-02-01  9:56   ` Aaron Lauterer
     [not found]   ` <<20220131175918.2099575-5-s.ivanov@proxmox.com>
2022-02-01 11:34     ` Fabian Grünbichler
2022-01-31 17:59 ` [pve-devel] [PATCH pve-kernel-meta 5/5] proxmox-boot: add pin/unpin functionality for non-p-b-t systems Stoiko Ivanov
2022-02-01  9:58 ` Aaron Lauterer [this message]

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=2ed841ff-3b30-30d2-da72-061686deb9d5@proxmox.com \
    --to=a.lauterer@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.ivanov@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal