backup: refer to our hosted prune simulator

[pve-docs.git] / qm.adoc

diff --git a/qm.adoc b/qm.adoc
index cd6641f89c4c02f5adaac54120129934ec1b4402..d30672e4658206dc7aabbad450bb398e0fa90c74 100644 (file)
--- a/qm.adoc
+++ b/qm.adoc
@@ -253,8 +253,8 @@ The option *IO Thread* can only be used when using a disk with the
 *VirtIO* controller, or with the *SCSI* controller, when the emulated controller
  type is  *VirtIO SCSI single*.
 With this enabled, Qemu creates one I/O thread per storage controller,
-instead of a single thread for all I/O, so it can increase performance when
-multiple isks are used and each disk has its own storage controller.
+rather than a single thread for all I/O. This can increase performance when
+multiple disks are used and each disk has its own storage controller.
 
 
 [[qm_cpu]]
@@ -352,6 +352,17 @@ the kvm64 default. If you don’t care about live migration or have a homogeneou
 cluster where all nodes have the same CPU, set the CPU type to host, as in
 theory this will give your guests maximum performance.
 
+Custom CPU Types
+^^^^^^^^^^^^^^^^
+
+You can specify custom CPU types with a configurable set of features. These are
+maintained in the configuration file `/etc/pve/virtual-guest/cpu-models.conf` by
+an administrator. See `man cpu-models.conf` for format details.
+
+Specified custom types can be selected by any user with the `Sys.Audit`
+privilege on `/nodes`. When configuring a custom CPU type for a VM via the CLI
+or API, the name needs to be prefixed with 'custom-'.
+
 Meltdown / Spectre related CPU flags
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^