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) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id F3928BB49 for ; Fri, 25 Nov 2022 15:09:26 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id DFA761D020 for ; Fri, 25 Nov 2022 15:09:26 +0100 (CET) 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 for ; Fri, 25 Nov 2022 15:09:25 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id ACD0F44C03 for ; Fri, 25 Nov 2022 15:09:25 +0100 (CET) From: Markus Frank To: pve-devel@lists.proxmox.com Date: Fri, 25 Nov 2022 15:08:56 +0100 Message-Id: <20221125140857.121622-5-m.frank@proxmox.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20221125140857.121622-1-m.frank@proxmox.com> References: <20221125140857.121622-1-m.frank@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.042 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 v4 4/5] added vIOMMU documentation 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: Fri, 25 Nov 2022 14:09:27 -0000 Signed-off-by: Markus Frank --- qm-pci-passthrough.adoc | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/qm-pci-passthrough.adoc b/qm-pci-passthrough.adoc index fa6ba35..7ed4d49 100644 --- a/qm-pci-passthrough.adoc +++ b/qm-pci-passthrough.adoc @@ -389,6 +389,31 @@ Example configuration with an `Intel GVT-g vGPU` (`Intel Skylake 6700k`): With this set, {pve} automatically creates such a device on VM start, and cleans it up again when the VM stops. +[[qm_pci_viommu]] +vIOMMU +~~~~~~ + +vIOMMU enables the option to passthrough pci devices to Level-2 VMs +in Level-1 VMs via Nested Virtualisation. + +Host-Requirement: Set `intel_iommu=on` or `amd_iommu=on` depending on your +CPU. + +VM-Requirement: For both Intel and AMD CPUs you will have to set +`intel_iommu=on` as a Linux boot parameter in the vIOMMU-enabled-VM, because +Qemu implements the Intel variant. + +To enable vIOMMU you have to add `viommu=1` to the machine-parameter in the +VM-Configuration, of the VM that you want to be able to passthrough pci devices. + +---- +# qm set VMID -machine q35,viommu=1 +---- + +Guest vIOMMU only works with the *q35* machine type and with *kvm* enabled. + +https://wiki.qemu.org/Features/VT-d + ifdef::wiki[] See Also -- 2.30.2