Enabling IOMMU on the host is not a requirement for vIOMMU. It is only a requirement for passthrough. Add a sentence to clarify the need for a configured PCI(e) passthrough on the host for passthrough to nested VMs.
Suggested-by: Dominik Csapak <d.csa...@proxmox.com> Signed-off-by: Markus Frank <m.fr...@proxmox.com> --- This patch replaces the "[PATCH docs] passthrough: viommu: remove 'amd_iommu=on' from the docs" patch: https://lists.proxmox.com/pipermail/pve-devel/2024-April/063688.html qm-pci-passthrough.adoc | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/qm-pci-passthrough.adoc b/qm-pci-passthrough.adoc index bbd6b85..fd0872e 100644 --- a/qm-pci-passthrough.adoc +++ b/qm-pci-passthrough.adoc @@ -505,14 +505,12 @@ vIOMMU (emulated IOMMU) vIOMMU is the emulation of a hardware IOMMU within a virtual machine, providing improved memory access control and security for virtualized I/O devices. Using -the vIOMMU option also allows you to pass through PCI devices to level-2 VMs in -level-1 VMs via https://pve.proxmox.com/wiki/Nested_Virtualization[Nested Virtualization]. -There are currently two vIOMMU implementations available: Intel and VirtIO. - -Host requirement: +the vIOMMU option also allows you to pass through PCI(e) devices to level-2 VMs +in level-1 VMs via https://pve.proxmox.com/wiki/Nested_Virtualization[Nested Virtualization]. +To pass through physical PCI(e) devices from the host to nested VMs, follow the +PCI(e) passthrough instructions. -* Add `intel_iommu=on` or `amd_iommu=on` depending on your CPU to your kernel -command line. +There are currently two vIOMMU implementations available: Intel and VirtIO. Intel vIOMMU ^^^^^^^^^^^^ -- 2.39.2 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
