VM display freezes with QXL

CreeperKong

Member
May 16, 2021
6
0
21
23
VM display may suddenly freeze when GPU is selected to QXL.
Just the display freezes, I can still access the VM with serial console or SSH.
 
I've seen this happen once in a while with VMs running LMDE7 (and the remote-viewer running on Mint22.3) but it did not happen with older VMs. I don't think it's related to recent Proxmox updates. I don't know who maintains SPICE/qxl or what could be the exact cause. I might happen more often on VMs with spice_enhancements: videostreaming=filter but I'm not sure.
Do you see any possibly related messages in the system log (inside the VM) after the freeze?
 
I've seen this happen once in a while with VMs running LMDE7 (and the remote-viewer running on Mint22.3) but it did not happen with older VMs. I don't think it's related to recent Proxmox updates. I don't know who maintains SPICE/qxl or what could be the exact cause. I might happen more often on VMs with spice_enhancements: videostreaming=filter but I'm not sure.
Do you see any possibly related messages in the system log (inside the VM) after the freeze?
I have tried all none filter, it seems not the culprit.
Can you ping VM or connect with SSH when this happens?
 
Last edited:
What operating system is running inside your VM? On what operating system do your run the viewer? Do you have the same issues when using VirtIO-GPU instead? Does it happen less often when you increase the memory for SPICE?
I use Alpine 3.23, Ubuntu 24.04, RHEL 10.1. Have the issue when QXL is selected.
VirtIO-GPU and VGA works fine. I have no GPU so I am not able to test out VirGL.
 
In the past I've seen guests freeze from not having enough video memory (VRAM) for whatever resolution is being used.
 
  • Like
Reactions: leesteken
In the past I've seen guests freeze from not having enough video memory (VRAM) for whatever resolution is being used.
Thank you. Freezes started occurring when I changed my VMs from 128MiB for SPICE(qxl) to 64 MiB, in retrospect. After changing it back to the maximum of 128MiB the problem went away. The resolution is only 1280x1393 but it does appear to be helping (or delaying the issue long enough that the VM is restarted/recreated).
 
  • Like
Reactions: richardm