Hi everyone,
I'm currently running Proxmox VE 8.2.4 with a Windows 11 23H2 VM on a Ryzen 7 3700X. In the past, I always set the CPU option to "host" in the VM's settings. This configuration worked fine: in the Windows Task Manager, I could see the host CPU, and it indicated "Virtual Machine: Yes".
However, for the past two weeks, without any changes to the VM or the Proxmox configuration, I noticed that Windows no longer detects the VM environment in Task Manager. It now shows the host CPU without the "Virtual Machine: Yes" label. This issue is significantly impacting the performance and responsiveness of the VM, and I'm also seeing high CPU usage.
Interestingly, I have a second Proxmox server running version 8.2.2 with a similar Windows 11 VM, and there, the Task Manager still properly shows "Virtual Machine: Yes". The configuration is identical on both servers.
Has there been any change in Proxmox or Windows that could explain this behavior? Or is there something I might need to adjust to restore proper detection of the hypervisor?
Thanks in advance for your help!
I'm currently running Proxmox VE 8.2.4 with a Windows 11 23H2 VM on a Ryzen 7 3700X. In the past, I always set the CPU option to "host" in the VM's settings. This configuration worked fine: in the Windows Task Manager, I could see the host CPU, and it indicated "Virtual Machine: Yes".
However, for the past two weeks, without any changes to the VM or the Proxmox configuration, I noticed that Windows no longer detects the VM environment in Task Manager. It now shows the host CPU without the "Virtual Machine: Yes" label. This issue is significantly impacting the performance and responsiveness of the VM, and I'm also seeing high CPU usage.
Interestingly, I have a second Proxmox server running version 8.2.2 with a similar Windows 11 VM, and there, the Task Manager still properly shows "Virtual Machine: Yes". The configuration is identical on both servers.
Has there been any change in Proxmox or Windows that could explain this behavior? Or is there something I might need to adjust to restore proper detection of the hypervisor?
Thanks in advance for your help!