Proxmox Host freeze when running Windows (10) VM

[seji]

Hi,

is setup proxmox this weekend and have a weierd issue. I'am currently running 2 VM's (not running the same time, just switching between them). One MacOS HS and one Windows 10 (for gaming).

The issue i expirence is, that the proxmox Host freezes when i am running a Windows 10 VM and i'am just using the browser or something like that. While i running a game this this is not happening. Also while i am running the macos VM i have none of these freeze issues.

In the syslog file is sadly not much to see:

Mar 29 18:53:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 29 18:53:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 29 18:53:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 29 18:53:21 pve autosuspend[8716]: 2020-03-29 18:53:21,516 - autosuspend.Processor - INFO - Starting new check iteration
Mar 29 18:53:21 pve autosuspend[8716]: Checking status of VM 100
Mar 29 18:53:21 pve autosuspend[8716]: VM 100 is NOT running
Mar 29 18:53:21 pve autosuspend[8716]: Checking status of VM 101
Mar 29 18:53:22 pve autosuspend[8716]: VM 101 is running
Mar 29 18:53:22 pve autosuspend[8716]: 2020-03-29 18:53:22,209 - autosuspend.Processor - INFO - Check ExternalCommand matched. Reason: Command /etc/autos$
Mar 29 18:53:22 pve autosuspend[8716]: 2020-03-29 18:53:22,210 - autosuspend.Processor - INFO - System is active. Resetting state
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^$
Mar 29 18:56:26 pve dmeventd[585]: dmeventd ready for processing.
Mar 29 18:56:26 pve systemd-modules-load[561]: Inserted module 'iscsi_tcp'
Mar 29 18:56:26 pve lvm[585]: Monitoring thin pool pve-data-tpool.
Mar 29 18:56:26 pve systemd-modules-load[561]: Inserted module 'ib_iser'
Mar 29 18:56:26 pve systemd-modules-load[561]: Inserted module 'vhost_net'
Mar 29 18:56:26 pve systemd[1]: Starting Flush Journal to Persistent Storage...
Mar 29 18:56:26 pve lvm[567]:   7 logical volume(s) in volume group "pve" monitored
Mar 29 18:56:26 pve lvm[585]: Monitoring thin pool nvme_data-nvme_data-tpool.

My Windows VM config looks like this:

root@pve:~# cat /etc/pve/qemu-server/101.conf
agent: 1
args: -machine type=pc-q35-4.0.1,kernel_irqchip=on -cpu host,topoext=on,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=proxmox,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,hv_synic,hv_stimer,hv_ipi,kvm=off -smp 8,sockets=1,cores=4,threads=2
balloon: 0
bios: ovmf
boot: cd
bootdisk: scsi0
cores: 8
cpu: host
efidisk0: nvme_data:vm-101-disk-1,size=4M
hookscript: local:snippets/windows10.sh
hostpci0: 0a:00.0,pcie=1,x-vga=1,romfile=Asus.GTX1080.8192.patched.rom
hostpci1: 0a:00.1,pcie=1
hostpci2: 0c:00.4,pcie=1
hostpci3: 0c:00.3,pcie=1
hugepages: 1024
machine: pc-q35-4.0.1
memory: 8192
name: Windows10
net0: virtio=B6:67:F0:6E:73:50,bridge=vmbr0
numa: 1
ostype: win10
scsi0: nvme_data:vm-101-disk-0,discard=on,iothread=1,size=80G,ssd=1
scsi1: /dev/disk/by-id/ata-Samsung_SSD_840_PRO_Series_S1ATNEAD708632X,iothread=1,size=250059096K,ssd=1
scsi2: /dev/disk/by-id/ata-Crucial_CT256MX100SSD1_14440DAC90AE,iothread=1,size=250059096K,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=1281d909-f09f-4cb5-829e-1193a9895e76
sockets: 1
usb0: host=4-2.4.2
usb1: host=2-3
usb2: host=2-4
vga: none
vmgenid: e30a094b-ea02-44d5-93d6-c56afd11dac0

Does anyone have the same issue or a tip whats the problem here?

Thanks in advance.

PS:
My PVE Version:

ve-manager/6.1-8/806edfe1 (running kernel: 5.4.27-1-pve-noamdflr)

PPS:
I already disable the C6 state with zenstates.py
My Hardware:
CPU: AMD Ryzen 3600
Mainboard: ASUS X370-Pro

 

[aaron]

What is that autosuspend in the logs? AFAICT nothing that is installed by default.

How does the "freeze" of the PVE host show itself?

 

[eminempt]

Any news about that? same problem here.

I have a windows 10 vm that when using KVM64 type CPU, all it's working fine, but when i go to "host" CPU type, it freezes right after logon into windows (my best guess would be some interference w/ Windows and ProxMox)

Whats interesting is that, i think that does not happen w/ a newly generated VM.
This particular VM im using now is booting directly from an SSD (it was my older Windows that was running on this Hardware) so, "Host type CPU" should not be a problem, since it recognizes this hardware (CPU) from before.

whats really odd is that w/ kvm64 it works but with host it doesn't.


My current spec is a Ryzen 5990x 16-core.