[pve-devel] applied: [PATCH docs] add documentation for display types and memory configuration
Thomas Lamprecht
t.lamprecht at proxmox.com
Mon Nov 12 14:38:59 CET 2018
On 11/12/18 11:14 AM, Dominik Csapak wrote:
> Signed-off-by: Dominik Csapak <d.csapak at proxmox.com>
> ---
> qm.adoc | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
> diff --git a/qm.adoc b/qm.adoc
> index c752900..343dfee 100644
> --- a/qm.adoc
> +++ b/qm.adoc
> @@ -595,6 +595,34 @@ traffic increases. We recommend to set this option only when the VM has to
> process a great number of incoming connections, such as when the VM is running
> as a router, reverse proxy or a busy HTTP server doing long polling.
>
> +[[qm_display]]
> +Display
> +~~~~~~~
> +
> +QEMU can virtualize a few types of VGA hardware. Some examples are:
> +
> +* *std*, the default, emulates a card with Bochs VBE extensions.
> +* *vmware*, is a VMWare SVGA-II compatible adapter.
> +* *qxl*, is the QXL paravirtualized graphics card. Selecting this also
> +enables SPICE for the VM.
> +
> +You can edit the amount of memory given to the virtual GPU, by setting
> +the *memory* option. This can enable higher resolutions inside the VM,
> +especially with SPICE/QXL.
> +
> +Selecting Multi-Monitor mode for SPICE (e.g., qxl2 for dual monitors) has
> +some implications:
> +
> +* Windows needs a device for each monitor, so if your ostype is some
> +version of windows, {pve} gives the VM an extra device per monitor.
> +Each device gets the specified amount of memory.
> +* Linux VMs, can always enable more virtual monitors, but selecting
> +a Multi-Monitor mode multiplies the memory given to the device with
> +the number of monitors.
> +
> +Selecting *serialX* as display disables the VGA output, and redirects
> +the Web Console to the selected serial port. A configured memory setting
> +will be ignored in that case.
>
> [[qm_usb_passthrough]]
> USB Passthrough
>
applied thanks, added a point for Cirrus, noting that should not used, not that people
see it and think that it's so new and fancy that we didn't even added it to the docs ;-)
More information about the pve-devel
mailing list