[pve-devel] [PATCH docs v3 1/1] qm: pve machine version: add section to explain +pveX versions

From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs v3 1/1] qm: pve machine version: add section to explain +pveX versions
Date: Fri,  4 Apr 2025 14:53:45 +0200	[thread overview]
Message-ID: <20250404125345.3244659-10-d.csapak@proxmox.com> (raw)
In-Reply-To: <20250404125345.3244659-1-d.csapak@proxmox.com>

and clarify what windows guests will be pinned to.

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
changes from v2:
* mention that windows gets pinned during guest creation

 qm.adoc | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/qm.adoc b/qm.adoc
index 2617a7c..ff49c37 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -173,6 +173,21 @@ This means that after a fresh start, the newest machine version supported by the
 QEMU binary is used (e.g. the newest machine version QEMU 8.1 supports is
 version 8.1 for each machine type).
 
+PVE Machine Version
++++++++++++++++++++
+
+Sometimes it's necessary to introduce new defaults or change the existing
+hardware layout for new guests. For this, we have introduces an additional 'pve
+machine version'. This version begins with 0 with every new QEMU machine
+version, for example 'pc-q35-9.2+pve0'. When we want to change the hardware
+layout or a default option, we bump it to the next one (e.g.
+'pc-q35-9.2+pve1'), so older running guests are not impacted. When pinning a
+guest to a specific machine, this can be omitted. In that case it defaults to
+0.
+
+Windows guests get pinned to the most current version that is available for the
+specific machine version during guest creation.
+
 QEMU Machine Version Deprecation
 ++++++++++++++++++++++++++++++++
 
-- 
2.39.5



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

