[SOLVED] Windows 10 VM locks up

ryanc1256

Member
Nov 1, 2020
5
0
6
61
I've recently upgraded to proxmox 7 and started noticing my windows based VM's "Stalling" where it looks like if they have a GPU passed through the GPU usage skyrockets to 100% (even though the VM is doing nothing except having task manager open)


I quickly did a 'dmesg' and looked at what was going on, and everytime this happened i was getting the same line showing up.

Code:
interrupt took too long (3136 > 3133), lowering kernel.perf_event_max_sample_rate to 63750

This never happened in proxmox 6 and only happens with windows vm's... works totally fine with the same GPU passed through to linux machines.

the IO usage of the overall system is very low too.


What could be the reason why an interrupt it taking too long?

DMESG
Code:
[77091.856111] fwbr116i0: port 2(tap116i0) entered disabled state
[77091.875350] fwbr116i0: port 1(fwln116i0) entered disabled state
[77091.875785] vmbr0: port 16(fwpr116p0) entered disabled state
[77091.875961] device fwln116i0 left promiscuous mode
[77091.875963] fwbr116i0: port 1(fwln116i0) entered disabled state
[77091.896979] device fwpr116p0 left promiscuous mode
[77091.896982] vmbr0: port 16(fwpr116p0) entered disabled state
[77141.463601]  sdk: sdk1 sdk2 sdk3 sdk4 sdk5
[77143.221103] device tap115i0 entered promiscuous mode
[77143.249076] fwbr115i0: port 1(fwln115i0) entered blocking state
[77143.249081] fwbr115i0: port 1(fwln115i0) entered disabled state
[77143.249144] device fwln115i0 entered promiscuous mode
[77143.249207] fwbr115i0: port 1(fwln115i0) entered blocking state
[77143.249210] fwbr115i0: port 1(fwln115i0) entered forwarding state
[77143.252306] vmbr0: port 16(fwpr115p0) entered blocking state
[77143.252310] vmbr0: port 16(fwpr115p0) entered disabled state
[77143.252387] device fwpr115p0 entered promiscuous mode
[77143.252437] vmbr0: port 16(fwpr115p0) entered blocking state
[77143.252439] vmbr0: port 16(fwpr115p0) entered forwarding state
[77143.255428] fwbr115i0: port 2(tap115i0) entered blocking state
[77143.255431] fwbr115i0: port 2(tap115i0) entered disabled state
[77143.255532] fwbr115i0: port 2(tap115i0) entered blocking state
[77143.255534] fwbr115i0: port 2(tap115i0) entered forwarding state
[77153.413521] vfio-pci 0000:85:00.0: vfio_ecap_init: hiding ecap 0x19@0x270
[77153.413529] vfio-pci 0000:85:00.0: vfio_ecap_init: hiding ecap 0x1b@0x2d0
[77153.413533] vfio-pci 0000:85:00.0: vfio_ecap_init: hiding ecap 0x26@0x410
[77153.413534] vfio-pci 0000:85:00.0: vfio_ecap_init: hiding ecap 0x27@0x440
[77863.116521] audit: type=1400 audit(1626575972.703:284): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-107_</var/lib/lxc>" name="/run/systemd/unit-root/" pid=1953149 comm="(ionclean)" srcname="/" flags="rw, rbind"
[78120.737604] perf: interrupt took too long (3952 > 3943), lowering kernel.perf_event_max_sample_rate to 50500
[79663.393511] audit: type=1400 audit(1626577772.703:285): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-107_</var/lib/lxc>" name="/run/systemd/unit-root/" pid=2083188 comm="(ionclean)" srcname="/" flags="rw, rbind"



PVEVERSION
Code:
proxmox-ve: 7.0-2 (running kernel: 5.11.22-2-pve)
pve-manager: 7.0-10 (running version: 7.0-10/d2f465d3)
pve-kernel-5.11: 7.0-5
pve-kernel-helper: 7.0-5
pve-kernel-5.11.22-2-pve: 5.11.22-3
pve-kernel-5.11.22-1-pve: 5.11.22-2
ceph-fuse: 15.2.13-pve1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx2
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.1.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-5
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-9
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-2
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.4-1
proxmox-backup-file-restore: 2.0.4-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-4
pve-cluster: 7.0-3
pve-container: 4.0-8
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.2-4
pve-ha-manager: 3.3-1
pve-i18n: 2.4-1
pve-qemu-kvm: 6.0.0-2
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-10
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1
 
Last edited:
Was something with the “+kvm” argument in the args property for the vm. Once removed it was solved and worked like normal again.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!