From: Markus Frank <m.frank@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] passthrough: viommu: replace host requirement with reference to pcie passthrough
Date: Fri, 26 Jul 2024 10:21:12 +0200 [thread overview]
Message-ID: <20240726082112.288403-1-m.frank@proxmox.com> (raw)
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.csapak@proxmox.com>
Signed-off-by: Markus Frank <m.frank@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
next reply other threads:[~2024-07-26 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 8:21 Markus Frank [this message]
2024-09-06 11:55 ` [pve-devel] applied: " Fiona Ebner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240726082112.288403-1-m.frank@proxmox.com \
--to=m.frank@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.