Troubleshooting vm freezes when using spice agent

whiggs

New Member
Dec 11, 2024
25
0
1
Hello Everyone. So, I am having an issue where my Windows vms freeze intermittently when I load them with the spice console. I was looking at the guest vm, I noticed that I had two windows services that are named very similarly: Spice Agent and Spice VDAgent. Looking I look at the properties for each service, I notice that they are both loading executables with the same name, but different paths: Spice vdagent's exectutable is located at "C:\Program Files (x86)\SPICE Guest Tools\64\vdservice.exe", and Spice agent's executable is located at "C:\Program Files\Spice Agent\vdservice.exe." I think this might be linked to why my vms are freezing when I load them using the spice console. I believe that one version of the spice agent service was installed as part of the virtio "win-guest-tools" installation for the virtio drivers, and the other version of the spice agent was installed as part of the spice guest tools installation. Based on my understanding of proxmox and spice, both the virtio drivers and the spice guest tools are required to for spice to work correctly, so I wanted to ask the following questions:
1) Am I correct in my assumption that both of these services perform the same function? Should one of them be removed?
2) What exactly needs to be installed in the vm for it and the spice console to run correctly? The virtio drivers? The virtio guest tools? The spice guest tools?
3) What services/drivers should I see installed on the windows vms to know that that the prerequisites for spice have been met?