From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 1BB9A726CB for ; Wed, 6 Oct 2021 17:52:55 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0AA3DF807 for ; Wed, 6 Oct 2021 17:52:25 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id DDB5FF7F3 for ; Wed, 6 Oct 2021 17:52:23 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id AED2E4585A for ; Wed, 6 Oct 2021 17:52:23 +0200 (CEST) From: Stefan Reiter To: pve-devel@lists.proxmox.com Date: Wed, 6 Oct 2021 17:52:11 +0200 Message-Id: <20211006155211.992254-2-s.reiter@proxmox.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20211006155211.992254-1-s.reiter@proxmox.com> References: <20211006155211.992254-1-s.reiter@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.529 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH docs 2/2] qm: add section about TPM X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Oct 2021 15:52:55 -0000 Signed-off-by: Stefan Reiter --- qm.adoc | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/qm.adoc b/qm.adoc index 93576c7..b9f4269 100644 --- a/qm.adoc +++ b/qm.adoc @@ -775,6 +775,36 @@ you need to set the client resolution in the OVMF menu (which you can reach with a press of the ESC button during boot), or you have to choose SPICE as the display type. +[[qm_tpm]] +Trusted Platform Module (TPM) +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +A *Trusted Platform Module* is a device which stores secret data - such as +encryption keys - securely and provides tamper-resistance functions for +validating system boot. + +Certain operating systems (e.g. Windows 11) require such a device to be attached +to a machine (be it physical or virtual). + +A TPM is added by specifying a *tpmstate* volume. This works similar to an +efidisk, in that it cannot be changed (only removed) once created. You can add +one via the following command: + + qm set -tpmstate0 :1,version= + +Where ** is the storage you want to put the state on, and ** +is either 'v1.2' or 'v2.0'. You can also add one via the web interface, by +choosing 'Add' -> 'TPM State' in the hardware section of a VM. + +The 'v2.0' TPM spec is newer and better supported, so unless you have a specific +implementation that requires a 'v1.2' TPM, it should be preferred. + +NOTE: Compared to a physical TPM, an emulated one does *not* provide any real +security benefits. The point of a TPM is that the data on it cannot be modified +easily, except via commands specified as part of the TPM spec. Since with an +emulated device the data storage happens on a regular volume, it can potentially +be edited by anyone with access to it. + [[qm_ivshmem]] Inter-VM shared memory ~~~~~~~~~~~~~~~~~~~~~~ -- 2.30.2