Hello world!
In the past months I have built two home servers to host a few VDI guests.
I chose Proxmox due its easy to use interface, but I have to say I not an expert on the matter.
These are my Hosts:
On both hosts I am noticing a single Windows 10 guest "misbehaving".
On idle, when the VM starts and the user does not login, the CPU Load on host varies between 3~7%, in order with all other Windows 10 guests.
After login, when the Win10 guest is idling, the CPU Load on host varies between 15~35%.
This issue happens on both AMD and Intel.
The method used for login is irrelevant. (Proxmox VNC; GPU Passtrough; or RDP)
The AMD host have two Win10 guests, just one misbehave. (All AMD RX550)
The Intel host have three Win10 guests, just one misbehave. (All Nvidia GTX 1070)
All are up-to-date, and have very similar configurations.
I have faced this issue trying to fine-tune the Intel host, when this misbehaved guest would induce lag on the others VM's when running some CPU intensive task.
Out of curiosity I went to look at the AMD host, and saw the same issue with CPU load.
From what I have read online, it could be an issue with clock configuration.
However Proxmox staff mentions this issue was solved with a former update.
Other posts online mentions about editing Libvirt XML (which I am unable to find in Proxmox), but results varies (some people says it works, some doesn't).
I also have read that it cloud be caused for excessive interruptions generated by the Host on the Guest.
However I don't know where to begin with to track this path...
I noticed the misbehaved guests have a visible "kernel time" in the task manager, ranging 3~5%.
Good guests shows a flat line for "kernel time", which leads me to believe this is an issue with excessive interruptions (wake/sleep).
I wouldn't know if it is related to the clock issue mentioned.
Assuming that all VM's were created following the same steps, I don't understand why just a couple of them misbehaves.
I am trying to benchmark the effect on the host when the guest is under load.
Generally I am seeing a higher load on host from these bad guests.
Effect on Host is a higher CPU load and power consuption.
I noticed sometimes input lag (mouse freezing, dropped frames), but don't know if it is related.
Somewhere else I have read that enabling Message Signaled Interruptions could help.
On the AMD guest I have tried to enable it on all PCI devices.
Tried to pass through the GPU ROM as a line parameter, and hide it from guest.
Tried to play with "localtime" and "OS type" option in Proxmox GUI.
Tried to change q35 machine versions.
My last attempt was the "args: -no-hpet".
AMD HOST
INTEL HOST
In the past months I have built two home servers to host a few VDI guests.
I chose Proxmox due its easy to use interface, but I have to say I not an expert on the matter.
These are my Hosts:
On both hosts I am noticing a single Windows 10 guest "misbehaving".
On idle, when the VM starts and the user does not login, the CPU Load on host varies between 3~7%, in order with all other Windows 10 guests.
After login, when the Win10 guest is idling, the CPU Load on host varies between 15~35%.
This issue happens on both AMD and Intel.
The method used for login is irrelevant. (Proxmox VNC; GPU Passtrough; or RDP)
The AMD host have two Win10 guests, just one misbehave. (All AMD RX550)
The Intel host have three Win10 guests, just one misbehave. (All Nvidia GTX 1070)
All are up-to-date, and have very similar configurations.
I have faced this issue trying to fine-tune the Intel host, when this misbehaved guest would induce lag on the others VM's when running some CPU intensive task.
Out of curiosity I went to look at the AMD host, and saw the same issue with CPU load.
From what I have read online, it could be an issue with clock configuration.
However Proxmox staff mentions this issue was solved with a former update.
Other posts online mentions about editing Libvirt XML (which I am unable to find in Proxmox), but results varies (some people says it works, some doesn't).
I also have read that it cloud be caused for excessive interruptions generated by the Host on the Guest.
However I don't know where to begin with to track this path...
I noticed the misbehaved guests have a visible "kernel time" in the task manager, ranging 3~5%.
Good guests shows a flat line for "kernel time", which leads me to believe this is an issue with excessive interruptions (wake/sleep).
I wouldn't know if it is related to the clock issue mentioned.
Assuming that all VM's were created following the same steps, I don't understand why just a couple of them misbehaves.
I am trying to benchmark the effect on the host when the guest is under load.
Generally I am seeing a higher load on host from these bad guests.
Effect on Host is a higher CPU load and power consuption.
I noticed sometimes input lag (mouse freezing, dropped frames), but don't know if it is related.
Somewhere else I have read that enabling Message Signaled Interruptions could help.
On the AMD guest I have tried to enable it on all PCI devices.
Tried to pass through the GPU ROM as a line parameter, and hide it from guest.
Tried to play with "localtime" and "OS type" option in Proxmox GUI.
Tried to change q35 machine versions.
My last attempt was the "args: -no-hpet".
AMD HOST
Code:
~# qm config 101
acpi: 1
agent: 1
args: -no-hpet
balloon: 0
bios: ovmf
boot: order=scsi0;ide0;net0
cores: 8
cpu: host
efidisk0: hdd:vm-101-disk-0,size=1M
hostpci0: 0000:01:00,pcie=1,x-vga=1
hotplug: disk,network,usb
hugepages: 1024
ide0: none,media=cdrom
ide2: none,media=cdrom
localtime: 1
machine: pc-q35-6.0
memory: 8192
name: VM-Glauco
net0: virtio=9A:7B:24:FF:57:5C,bridge=vmbr0,firewall=1
numa: 1
onboot: 1
ostype: win10
parent: gerenciador
scsi0: hdd:vm-101-disk-1,cache=writeback,discard=on,iothread=1,size=1T,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=05604224-4150-4c97-b39e-3a9ba8702d2c
sockets: 1
usb0: host=7-2.1
usb1: host=7-2.2
usb2: host=7-2.3
usb3: host=7-2.4
vga: none
vmgenid: 4b0ac261-ea9c-46fa-9722-1a3544a07796INTEL HOST
Code:
~# qm config 102
agent: 1
balloon: 0
bios: ovmf
boot: order=scsi0;ide2;net0
cores: 8
cpu: host
efidisk0: hdd:vm-102-disk-0,size=1M
hostpci0: 0000:02:00,pcie=1,x-vga=1
hugepages: 1024
ide2: local:iso/virtio-win-0.1.204.iso,media=cdrom,size=543272K
localtime: 1
machine: pc-q35-6.0
memory: 24576
name: Win10-GPU2
net0: virtio=8E:DC:C5:6A:57:78,bridge=vmbr0,firewall=1
numa: 1
onboot: 1
ostype: win10
parent: MSI1
scsi0: hdd:vm-102-disk-1,cache=writeback,discard=on,iothread=1,size=1T,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=d61e4b65-ef7c-4d3e-b64c-70a2dba82bbf
sockets: 1
startup: order=2
tablet: 1
usb0: host=1-11
usb1: host=1-13
vga: none
vmgenid: 9affe86a-7568-4216-8fb2-22298a59e5ef
vmstatestorage: hdd