Commit 24dbbcd3 authored by intrigeri's avatar intrigeri
Browse files

Document how to troubleshoot graphics issues with virt-manager (refs: #14786)

parent 7d86d94f
......@@ -203,3 +203,30 @@ in the previous section|virt-manager#disconnect]].
Once you started from the virtual USB device you can [[create a persistent
volume|first_steps/persistence/configure]] on it.
# Troubleshooting
<a id="graphics-issues"></a>
## Graphics issues
Issues with graphics support in Tails running inside a virtual machine
with *virt-manager* are common. The best solution can vary depending
on the version of the virtualization solution and on the virtual
machine configuration. For example:
- The *Auto resize VM with window* feature does not work in all
- The video device that provides optimal graphics performance can be
different depending on the version of the host operating system.
To troubleshoot such issues:
1. Ensure the virtual machine has a *Spice* display and a *Spice*
channel configured, as opposed to *VNC* ones.
2. Try various virtual video device models.
Start with *Virtio* and *QXL* video devices: they generally give
the best results. If they don't perform well for you, try every
other video device model.
......@@ -345,6 +345,14 @@ adapters. If this happens to you:
[[report a bug|doc/first_steps/bug_reporting]]. Include the exact
model of your Intel graphics adapter.
Virtual machines with *virt-manager*, *libvirt* and *QEMU*
See the
[[dedicated troubleshooting documentation|doc/advanced_topics/virtualization/virt-manager#graphics-issues]]
about graphics issues in Tails running inside a virtual machine
with *virt-manager*.
<a id="wi-fi"></a>
Wi-Fi issues
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment