Search results

here's what we found out: when the Windows vm is running and the guest agent is enabled, but not installed on the system - at this moment, there are problems with access to sockets of agents of other virtual machines on the same host on which this Windows vm is running.

hmm, interestingly, this behavior is observed in Linux guests when a Windows machine is started on the same host with an incorrectly set OS type. The Windows VM also behaves the same way - it freezes and timeouts for any action in the GUI Proxmox. By disabling the guest's Windows, the problem...

similar problem, no solution? root@glsv-px-2:~# pveversion -v proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve) pve-manager: 6.3-4 (running version: 6.3-4/0a38c56f) pve-kernel-5.4: 6.3-6 pve-kernel-helper: 6.3-6 pve-kernel-5.4.101-1-pve: 5.4.101-1 pve-kernel-5.4.78-2-pve: 5.4.78-2...