From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 203221FF0AA for ; Tue, 17 Nov 2026 23:43:21 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id EF15D21961; Tue, 17 Nov 2026 23:40:58 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com Subject: [PATCH docs v2 35/36] qm: configuration: describe the read-only meta property Date: Tue, 17 Nov 2026 23:34:45 +0100 Message-ID: <20261117223945.862914-36-t.lamprecht@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261117223945.862914-1-t.lamprecht@proxmox.com> References: <20261117223945.862914-1-t.lamprecht@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794955193354 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.195 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: 62GXHETSA7M6YT2AHOLASR5IV74ACJQI X-Message-ID-Hash: 62GXHETSA7M6YT2AHOLASR5IV74ACJQI X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: The 'meta' property of VMs was not documented anywhere, as the generated option reference leaves it out for being read-only. Since Proxmox VE 9.3, it also holds the guest identity, and it matters for upgrades: older versions drop the whole property, including 'creation-qemu', which keeps the machine version of Windows VMs and some other hardware defaults stable. Describe its members next to the snapshot properties, refer to the guest identity section for 'uid' and 'rtime', and state why migrations and clones to nodes with older versions are refused. Signed-off-by: Thomas Lamprecht --- no changes since v1 qm.adoc | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) diff --git a/qm.adoc b/qm.adoc index 350c6ef..487673b 100644 --- a/qm.adoc +++ b/qm.adoc @@ -2441,6 +2441,44 @@ For details about how the target storage gets chosen for the VM state, see xref:qm_vmstatestorage[State storage selection] in the chapter xref:qm_hibernate[Hibernation]. +[[qm_meta_info]] +Meta Information +~~~~~~~~~~~~~~~~ + +The read-only `meta` property contains information that {pve} records +automatically about the VM: + +`ctime`:: + +The time the VM was created, in seconds since the UNIX epoch. + +`creation-qemu`:: + +The QEMU version that the VM was created with. For VMs without a fixed machine +version, {pve} uses it to keep parts of the virtual hardware as they were at +creation, for example the machine version of Windows VMs, see +xref:qm_machine_type[Machine Type]. + +`uid` and `rtime`:: + +The guest identity of the VM, available since {pve} 9.3, see +xref:guest_identity[Guest Identity]. + +.Example `meta` property of a VM +---- +meta: creation-qemu=10.1.2,ctime=1772444467,rtime=1794320571482,uid=w5qczgiem26qnwzwsoil +---- + +A clone keeps its source VM's `ctime` and `creation-qemu` values. A restored VM +uses the values from the backup. VMs created with older versions of {pve} can +lack these values. + +{pve} versions older than 9.3 ignore the whole `meta` property of a VM with a +guest identity, including `creation-qemu`, and drop it when they write the +configuration. A VM started on a node running such a version can therefore get +different virtual hardware. Migrating or cloning a VM to such a node is refused, +see xref:guest_identity_mixed_versions[Mixed Versions in a Cluster]. + [[qm_options]] Options ~~~~~~~ -- 2.47.3