I can say with 100% confidence that the virtio drivers/spice agent install media included in the latest version of the virtio iso that is linked to in the proxmox wiki is the source of my vm freezes. While investigating this issue, I came across another open source vdi solution that utilized the spice protocol to connect to deployed vms, Ravada VDI. So, out of curiosity, I deployed this solution to another server to see if I ran into the same reliability issues that I was experiencing with proxmox. After deploying a test instance of windows 10 in Ravada, I noticed that Ravada had automatically mounted an older version of the exact same virtio driver iso that proxmox uses, so I installed the drivers in the Ravada vm, and it worked perfectly without crashing. I then copied the iso with the older version of the drivers from the Ravada server and uploaded it to the Proxmox server, deployed a test vm, installed the virtio drivers/spice agent using the older version of the iso, and the test vm has not crashed once even after prolonged use. This seems to be a pretty clear indicator to me that the issue is with the latest version of the virtio iso, and I would like to inform the developers of the issue so that the issue can be fixed, so I hope that someone can help me in that endeavor:
the virtio-win-guest-tools installer (which is the installer I run on the iso) installs the virtio drivers, the spice agent, and the qemu agent all at once, right? Do the virtio drivers have any impact on the spice protocol, or is the spice agent the software that only software that impacts the spice protocol? I am trying to identify the components that are potentially responsible for the problem so that I know who to reach out to. Or, if someone could just provide me a direct link(s) to the page(s) where I can submit the bug report(s), that would be immensely helpful. Thanks.
the virtio-win-guest-tools installer (which is the installer I run on the iso) installs the virtio drivers, the spice agent, and the qemu agent all at once, right? Do the virtio drivers have any impact on the spice protocol, or is the spice agent the software that only software that impacts the spice protocol? I am trying to identify the components that are potentially responsible for the problem so that I know who to reach out to. Or, if someone could just provide me a direct link(s) to the page(s) where I can submit the bug report(s), that would be immensely helpful. Thanks.
