[pve-devel] applied: [PATCH docs] sysadmin: revise firmware chapter, add firmware repo section

Thomas Lamprecht t.lamprecht at proxmox.com
Mon Oct 30 14:13:48 CET 2023

Am 30/10/2023 um 13:10 schrieb Alexander Zeidler:
> Chapter "Firmware Updates":
> * improve the structure and clarity of information provided
> * mention which update methods are when available/recommended
> * add information about the already pre-installed pve-firmware package
> * emphasise the importance of CPU microcode updates, how to interpret
>   versions and how to recover a possibly unbootable system
> * move info about non-free-firmware repo to "Package Repositories"
> Chapter "Package Repositories":
> * add new section "Debian Firmware Repository"
> Signed-off-by: Alexander Zeidler <a.zeidler at proxmox.com>
> ---
> Depends on "[PATCH docs] ha-manager, software updates: add useful BlockIds"
> (https://lists.proxmox.com/pipermail/pve-devel/2023-October/059710.html)
>  firmware-updates.adoc  | 233 ++++++++++++++++++++++++++++-------------
>  pve-package-repos.adoc |  18 ++++
>  2 files changed, 179 insertions(+), 72 deletions(-)

applied, thanks!

but I restructured the "set up early os µcode updates" section to a actionable
list, and dropped the subtle link to the HA maintenance mode there, such links
are rather odd and for users it's not really clear what they want to tell them
here, especially as it's only specific to HA for now (and how is the maintenance
mode safe, but a normal reboot isn't?)

If, you'd need to add a chapter/section about (safe) host reboot, that describes
how things work, what one might want to look out for to ensure guest uptime,
and in the future also things like full cluster poweroff (can be very tricky,
e.g., with ceph and/or HA).

I also reworded the part about detecting the version, and that not every update
will necessarily include a update for one's CPU - feel free to follow-up if
something got lost.

More information about the pve-devel mailing list