|
@@ -434,6 +434,31 @@ Stream ``reconnect`` (since 9.2)
|
|
The ``reconnect`` option only allows specifiying second granularity timeouts,
|
|
The ``reconnect`` option only allows specifiying second granularity timeouts,
|
|
which is not enough for all types of use cases, use ``reconnect-ms`` instead.
|
|
which is not enough for all types of use cases, use ``reconnect-ms`` instead.
|
|
|
|
|
|
|
|
+VFIO device options
|
|
|
|
+'''''''''''''''''''
|
|
|
|
+
|
|
|
|
+``-device vfio-calxeda-xgmac`` (since 10.0)
|
|
|
|
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
+The vfio-calxeda-xgmac device allows to assign a host Calxeda Highbank
|
|
|
|
+10Gb XGMAC Ethernet controller device ("calxeda,hb-xgmac" compatibility
|
|
|
|
+string) to a guest. Calxeda HW has been ewasted now and there is no point
|
|
|
|
+keeping that device.
|
|
|
|
+
|
|
|
|
+``-device vfio-amd-xgbe`` (since 10.0)
|
|
|
|
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
+The vfio-amd-xgbe device allows to assign a host AMD 10GbE controller
|
|
|
|
+to a guest ("amd,xgbe-seattle-v1a" compatibility string). AMD "Seattle"
|
|
|
|
+is not supported anymore and there is no point keeping that device.
|
|
|
|
+
|
|
|
|
+``-device vfio-platform`` (since 10.0)
|
|
|
|
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
+The vfio-platform device allows to assign a host platform device
|
|
|
|
+to a guest in a generic manner. Integrating a new device into
|
|
|
|
+the vfio-platform infrastructure requires some adaptation at
|
|
|
|
+both kernel and qemu level. No such attempt has been done for years
|
|
|
|
+and the conclusion is that vfio-platform has not got any traction.
|
|
|
|
+PCIe passthrough shall be the mainline solution.
|
|
|
|
+
|
|
CPU device properties
|
|
CPU device properties
|
|
'''''''''''''''''''''
|
|
'''''''''''''''''''''
|
|
|
|
|