[SOLVED] Windows guest with hyper-v crashes

[Jrant]

Hi, I recently started learning Proxmox
i installed Windows 11Pro and managed to make RTX 3090 passthrough work.
When I open the AIDA64 program ,VM freezes and reported CPU usage rises to 100%.
AND the freeze will occur after 5~∞ minutes of being idle on the VM only, PVE itself is responsive.
use kernel5.13,vm freeze at startup
Can someone help me

host

CPU:Ryzen 5950x
MB:Msi MEG X570 GODLIKE
RAM:128GB
GPU:RTX3090,GTX960
BIOS:7C34v1G3(ComboAm4v2PI 1.2.0.6c)
iommu=on,svm=on

package version

proxmox-ve: 7.1-1 (running kernel: 5.15.30-1-pve)
pve-manager: 7.1-12 (running version: 7.1-12/b3c09de3)
pve-kernel-helper: 7.1-14
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.30-1-pve: 5.15.30-1
pve-kernel-5.13.19-6-pve: 5.13.19-15
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-7
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-5
libpve-guest-common-perl: 4.1-1
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.1-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-2
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-7
pve-cluster: 7.1-3
pve-container: 4.1-4
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-6
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-2
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on video=efifb:off,vesafb:off pcie_acs_override=downstream"

qm

agent: 1
args: -cpu 'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=AMD,hypervisor=off'
bios: ovmf
boot: order=scsi0
cores: 16
cpu: host,flags=+ibpb;+amd-no-ssb;+hv-tlbflush;+aes
cpulimit: 16
cpuunits: 2048
efidisk0: local:100/vm-100-disk-1.raw,efitype=4m,pre-enrolled-keys=1,size=528K
hostpci0: 0000:4e:00,pcie=1,x-vga=1
hostpci1: 0000:50:00.4,rombar=0
machine: pc-q35-6.1
memory: 32768
meta: creation-qemu=6.1.1,ctime=1648982956
name: Win11-0
net0: virtio=F2:C4:84:C6:AC:7B,bridge=vmbr0,firewall=0
numa: 0
ostype: win11
scsi0: local:100/vm-100-disk-0.raw,backup=0,iothread=1,size=120G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=72471fe3-7a62-4b82-b142-dc16cffd6eba
sockets: 1
tpmstate0: local:100/vm-100-disk-2.raw,size=4M,version=v2.0
vga: none
vmgenid: f52c321b-1244-499a-b3db-f953806486c6

Syslog

Apr 06 12:35:48 pve kernel: SVM: kvm [3870]: vcpu0, guest rIP: 0xfffff874e9d687d7 unimplemented wrmsr: 0xc0010115 data 0x0
Apr 06 12:35:49 pve kernel: SVM: kvm [3870]: vcpu1, guest rIP: 0xfffff874e9d687d7 unimplemented wrmsr: 0xc0010115 data 0x0
Apr 06 12:35:49 pve kernel: SVM: kvm [3870]: vcpu2, guest rIP: 0xfffff874e9d687d7 unimplemented wrmsr: 0xc0010115 data 0x0
Apr 06 12:35:49 pve kernel: SVM: kvm [3870]: vcpu3, guest rIP: 0xfffff874e9d687d7 unimplemented wrmsr: 0xc0010115 data 0x0
Apr 06 12:35:49 pve kernel: SVM: kvm [3870]: vcpu4, guest rIP: 0xfffff874e9d687d7 unimplemented wrmsr: 0xc0010115 data 0x0
Apr 06 12:35:49 pve kernel: SVM: kvm [3870]: vcpu5, guest rIP: 0xfffff874e9d687d7 unimplemented wrmsr: 0xc0010115 data 0x0
Apr 06 12:35:49 pve kernel: SVM: kvm [3870]: vcpu6, guest rIP: 0xfffff874e9d687d7 unimplemented wrmsr: 0xc0010115 data 0x0
Apr 06 12:35:49 pve kernel: SVM: kvm [3870]: vcpu7, guest rIP: 0xfffff874e9d687d7 unimplemented wrmsr: 0xc0010115 data 0x0
Apr 06 12:35:49 pve kernel: SVM: kvm [3870]: vcpu8, guest rIP: 0xfffff874e9d687d7 unimplemented wrmsr: 0xc0010115 data 0x0
Apr 06 12:35:50 pve kernel: SVM: kvm [3870]: vcpu9, guest rIP: 0xfffff874e9d687d7 unimplemented wrmsr: 0xc0010115 data 0x0
Apr 06 12:47:17 pve pvedaemon[1545]: VM 100 qmp command failed - VM 100 qmp command 'guest-ping' failed - got timeout

​

solved with update proxmox-ve: 7.2

 

[vaschthestampede]

You can try with the 5.15 kernel.
https://forum.proxmox.com/threads/opt-in-linux-kernel-5-15-for-proxmox-ve-7-x-available.100936/

The problem seems to be limited to nested Hyper-V on AMD environments.

 

[Jrant]

You can try with the 5.15 kernel.
https://forum.proxmox.com/threads/opt-in-linux-kernel-5-15-for-proxmox-ve-7-x-available.100936/

The problem seems to be limited to nested Hyper-V on AMD environments.

im already using 5.15

package version:
proxmox-ve: 7.1-1 (running kernel: 5.15.30-1-pve)

but still freeze

 

[vaschthestampede]

I've read wrong.