Hello,
We are running a bunch of Windows VMs across several servers for building artifacts, and we discovered that some of the VMs have poor I/O performance. After extensive digging, we realized that those VMs that perform well all state in Windows Task Manager that it is a virtual machine, whereas those that perform poorly Windows seem to believe it's running on bare metal.
I understand that there are ways of tricking the VM into believing it's not a VM (by setting thing like `kvm=off` and `hidden=1`), but we have no such configuration in any of our Proxmoxes. So why would Windows fail to detect it's running as a VM? Does this ring a bell with anyone? For some VMs (but not all), we can detect a significant drop in performance after there was a power outage...
We are running both Windows 10 and 11 VMs, and on all poor-performing VMs we have VirtIO drivers installed. Reinstalling it does not appear to make a difference. Next step is to try to reinstall the VMs themselves, but it'd be good to know why this is happening in the first place.
We are running a bunch of Windows VMs across several servers for building artifacts, and we discovered that some of the VMs have poor I/O performance. After extensive digging, we realized that those VMs that perform well all state in Windows Task Manager that it is a virtual machine, whereas those that perform poorly Windows seem to believe it's running on bare metal.
I understand that there are ways of tricking the VM into believing it's not a VM (by setting thing like `kvm=off` and `hidden=1`), but we have no such configuration in any of our Proxmoxes. So why would Windows fail to detect it's running as a VM? Does this ring a bell with anyone? For some VMs (but not all), we can detect a significant drop in performance after there was a power outage...
We are running both Windows 10 and 11 VMs, and on all poor-performing VMs we have VirtIO drivers installed. Reinstalling it does not appear to make a difference. Next step is to try to reinstall the VMs themselves, but it'd be good to know why this is happening in the first place.