buildsys: switch upload dist over to buster

[pve-docs.git] / qm-pci-passthrough.adoc

diff --git a/qm-pci-passthrough.adoc b/qm-pci-passthrough.adoc
index 7e00e2e531529b1572b380e8b2d83de02c57b7dd..a347e31a5e4b277028e767190d513583b8d76435 100644 (file)
--- a/qm-pci-passthrough.adoc
+++ b/qm-pci-passthrough.adoc
@@ -1,6 +1,9 @@
 [[qm_pci_passthrough]]
 PCI(e) Passthrough
 ------------------
+ifdef::wiki[]
+:pve-toplevel:
+endif::wiki[]
 
 PCI(e) passthrough is a mechanism to give a virtual machine control over
 a PCI device from the host. This can have some advantages over using
@@ -90,7 +93,7 @@ Finally reboot to bring the changes into effect and check that it is indeed
 enabled.
 
 ----
-# dmesg -e DMAR -e IOMMU -e AMD-Vi
+# dmesg | grep -e DMAR -e IOMMU -e AMD-Vi
 ----
 
 should display that `IOMMU`, `Directed I/O` or `Interrupt Remapping` is
@@ -128,20 +131,18 @@ For this add  the following line in a file ending with `.conf' file in
 Please be aware that this option can make your system unstable.
 ====
 
-Notes for GPU passthrough
-^^^^^^^^^^^^^^^^^^^^^^^^^
+GPU Passthrough Notes
+^^^^^^^^^^^^^^^^^^^^^
 
-When passing through a GPU (be it a full device, or a vGPU), if you want to use
-it for displaying, you have to either physically connect a monitor to the
-card (if possible), or configure a remote desktop software (e.g., VNC, RDP)
-inside the guest and use that.
+It is not possible to display the frame buffer of the GPU via NoVNC or SPICE on
+the {pve} web interface.
 
-It is not possible to display the content of the GPU via NoVNC/SPICE on the
-{pve} web interface.
+When passing through a whole GPU or a vGPU and graphic output is wanted, one
+has to either physically connect a monitor to the card, or configure a remote
+desktop software (for example, VNC or RDP) inside the guest.
 
-If you want to use the GPU for things like OpenCL or CUDA, this is not an issue,
-since the application should be able to choose the hardware without using
-it as a display.
+If you want to use the GPU as a hardware accelerator, for example, for
+programs using OpenCL or CUDA, this is not required.
 
 Host Device Passthrough
 ~~~~~~~~~~~~~~~~~~~~~~~
@@ -192,7 +193,7 @@ configuration, for example by executing:
 # qm set VMID -hostpci0 00:02.0
 ----
 
-If your device has multiple functions (e.g., ``00:02.0`' and ``00:02.1`'),
+If your device has multiple functions (e.g., ``00:02.0`' and ``00:02.1`' ),
 you can pass them through all together with the shortened syntax ``00:02`'
 
 There are some options to which may be necessary, depending on the device
@@ -358,3 +359,12 @@ 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.
+
+ifdef::wiki[]
+
+See Also
+~~~~~~~~
+
+* link:/wiki/Pci_passthrough[PCI Passthrough Examples]
+
+endif::wiki[]