From 027bbe9a2904f972587544a8ab870167579ef0ec Mon Sep 17 00:00:00 2001 From: Thomas Lamprecht Date: Tue, 26 Apr 2022 11:57:46 +0200 Subject: [PATCH] sysadmin: rework boot kernel pinning section Signed-off-by: Thomas Lamprecht --- system-booting.adoc | 55 +++++++++++++++++++++++++++------------------ 1 file changed, 33 insertions(+), 22 deletions(-) diff --git a/system-booting.adoc b/system-booting.adoc index 7d8ff47..30621a6 100644 --- a/system-booting.adoc +++ b/system-booting.adoc @@ -290,33 +290,40 @@ To apply your changes, run `proxmox-boot-tool refresh`, which sets it as the [[sysboot_kernel_pin]] -Selecting the kernel-version for booting -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -In addition to actively watching the boot process to select an older kernel -version to boot into, you can also use `proxmox-boot-tool` to `pin` the kernel -version the system should use. This should help you to work around -incompatibilities between a newer kernel version and the hardware. Such a -`pin` should be removed as soon as possible in order to have all the latest -security patches in place. - -NOTE: The pinning functionality works for all {pve} systems, not only those -using `proxmox-boot-tool` to synchronize the contents of the ESPs, if your -system does not use `proxmox-boot-tool` for synchronizing you can also skip the -`proxmox-boot-tool refresh` call in the end. +Override the Kernel-Version for next Boot +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +To select a kernel that is not currently the default kernel, you can either: + +* use the boot loader menu that is displayed at the beginning of the boot + process +* use the `proxmox-boot-tool` to `pin` the system to a kernel version either + once or permanently (until pin is reset). + +This should help you work around incompatibilities between a newer kernel +version and the hardware. -To permanently select the version `5.15.30-1-pve` for booting run: +NOTE: Such a pin should be removed as soon as possible so that all current +security patches of the latest kernel are also applied to the system. + +For example: To permanently select the version `5.15.30-1-pve` for booting you +would run: ---- # proxmox-boot-tool kernel pin 5.15.30-1-pve ---- -You can also set a kernel version to be booted on the next system boot only -(e.g. to test if an updated kernel has resolved an issue, which caused you -to `pin` a version in the first place): +TIP: The pinning functionality works for all {pve} systems, not only those using +`proxmox-boot-tool` to synchronize the contents of the ESPs, if your system +does not use `proxmox-boot-tool` for synchronizing you can also skip the +`proxmox-boot-tool refresh` call in the end. + +You can also set a kernel version to be booted on the next system boot only. +This is for example useful to test if an updated kernel has resolved an issue, +which caused you to `pin` a version in the first place: ---- -# proxmox-boot-tool kernel pin 5.15.31-1-pve --next-boot +# proxmox-boot-tool kernel pin 5.15.30-1-pve --next-boot ---- To remove any pinned version configuration use the `unpin` subcommand: @@ -326,10 +333,14 @@ To remove any pinned version configuration use the `unpin` subcommand: ---- While `unpin` has a `--next-boot` option as well, it is used to clear a pinned -version set with `--next-boot` and manually invoking is of little use. +version set with `--next-boot`. As that happens already automatically on boot, +invonking it manually is of little use. + +After setting, or clearing pinned versions you also need to synchronize the +content and configuration on the ESPs by running the `refresh` subcommand. -After setting or clearing pinned versions you also need to synchronize the -content and configuration on the ESPs by running the `refresh` subcommand: +TIP: You will be prompted to automatically do for `proxmox-boot-tool` managed +systems if you call the tool interactively. ---- # proxmox-boot-tool refresh -- 2.39.2