-
Notifications
You must be signed in to change notification settings - Fork 540
Debugging VM graphical display issues
Cole Robinson edited this page Sep 8, 2024
·
4 revisions
Bugs related to the VM graphical display are often filed against virt-manager. Common reports describe problems with:
- Mouse: weird pointer look or behavior
- Graphical glitches or strange appearance
- Spice VM text copy+paste
- Spice USB redirection (the virt-manager
Redirect USB deviceoption) - Spice Guest autoresize behavior (the virt-manager
Auto resize VM with windowoption) - Spice GL/Virtio 3D support graphical issues
Often the true source of the issue lies in other projects, such as:
To help determine the true source of the problem, please try the following debugging steps:
-
Try to reproduce with
virt-viewer.- Start your VM in virt-manager, then close virt-manager
- From a terminal, run
sudo virt-viewer YOUR-VM-NAME - If you can't reproduce the problem, it may be virt-manager's fault. File a bug.
- If you see the same problem, it is likely not virt-manager OR virt-viewers fault.
- If the issue involves Spice specific functionality listed above, file an issue against
spicefor further triage. - If your VM is using VNC, file an issue against
gtk-vnc. - Otherwise continue to the next debugging steps to narrow it down more
- If the issue involves Spice specific functionality listed above, file an issue against
-
Try to reproduce after switching from
QXLtoVGA- In virt-manager VM details, select
Video QXL, changeModeltoVGA, click Apply, fully power off the VM, then start it. - If you can't reproduce the problem, it could be in a number of places, but file an issue against
spicefor further triage. - If you can still reproduce the problem, file a bug against virt-manager.
- If your problem affects a specific non-
QXLvideo model likeVirtio, file an issue against qemu.
- In virt-manager VM details, select
-
Try to reproduce after switching from Spice to VNC
- In virt-manager VM details, select
Display Spice, changeTypetoVNC server, click Apply, fully power off the VM, then start it. - If you can't reproduce the problem, file an issue against
spicefor further triage. - If you can still reproduce the problem, file a bug against virt-manager.
- In virt-manager VM details, select