I'm not sure when/how this started, but I've just been dealing with it. The problem is this:
When I go to Proxmox and click on Console > Spice to get to my VM (Any VM, but mostly Windows-based VMs) from my Windows 11 machine, it works like normal. But - sometimes those windows just close. If, for example, I take a dog for a walk for 25 minutes - I will come back and have to re-launch the spice client. This did not used to happen - so it is confusing to me. I have 4 monitors and have seen a client close while I'm working on something else on another monitor. So - it is not PC activity that seems to be at play. I'm only guessing that it is inactivity in the VM? The power settings in the VM seem to be never/never for 'turn off display' / 'Put the computer to sleep'. The Spice Guest Tools on the VM are 0.141, which appears to be the latest. I also have the same guest tools on my Windows 11 machine.
Has anyone seen this before? Was there maybe an update to the spice guest tools that created some sort of inactivity setting? Is there a log somewhere I can look at that might tell me why this is happening?
Thanks in advance!
When I go to Proxmox and click on Console > Spice to get to my VM (Any VM, but mostly Windows-based VMs) from my Windows 11 machine, it works like normal. But - sometimes those windows just close. If, for example, I take a dog for a walk for 25 minutes - I will come back and have to re-launch the spice client. This did not used to happen - so it is confusing to me. I have 4 monitors and have seen a client close while I'm working on something else on another monitor. So - it is not PC activity that seems to be at play. I'm only guessing that it is inactivity in the VM? The power settings in the VM seem to be never/never for 'turn off display' / 'Put the computer to sleep'. The Spice Guest Tools on the VM are 0.141, which appears to be the latest. I also have the same guest tools on my Windows 11 machine.
Has anyone seen this before? Was there maybe an update to the spice guest tools that created some sort of inactivity setting? Is there a log somewhere I can look at that might tell me why this is happening?
Thanks in advance!