Intel NUC i5 10. Gen GVT-g

D

DpunktS

Member
Feb 16, 2021
14
0
21
34
I have a problem with GVT-g on the Intel NUC i5 10th Gen. Windows 10 runs with this setting about 7 days until the virtual machine crashes and a CPU core shows 100%. If I increase the resolution, the time with V5_4 is about 3-4 days. If the virtual machine crashes, Proxmox can no longer shut down normally, I then have to perform a hard reset.
Can someone help me please. I'm still a beginner with Proxmox.

I gave the GVT activated according to the instructions:

intel_iommu=on i915.enable_gvt=1 kvm.ignore_msrs=1

vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd
kvmgt
vfio-mdev

Screenshot 2021-06-07 101007.png
proxmox-ve: 6.4-1 (running kernel: 5.4.114-1-pve) pve-manager: 6.4-6 (running version: 6.4-6/be2fa32c) pve-kernel-5.4: 6.4-2 pve-kernel-helper: 6.4-2 pve-kernel-5.4.114-1-pve: 5.4.114-1 pve-kernel-5.4.106-1-pve: 5.4.106-1 pve-kernel-5.4.78-2-pve: 5.4.78-2 pve-kernel-5.4.73-1-pve: 5.4.73-1 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.1.2-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: 0.8.35+pve1 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.20-pve1 libproxmox-acme-perl: 1.1.0 libproxmox-backup-qemu0: 1.0.3-1 libpve-access-control: 6.4-1 libpve-apiclient-perl: 3.1-3 libpve-common-perl: 6.4-3 libpve-guest-common-perl: 3.1-5 libpve-http-server-perl: 3.2-2 libpve-storage-perl: 6.4-1 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 4.0.6-2 lxcfs: 4.0.6-pve1 novnc-pve: 1.1.0-1 proxmox-backup-client: 1.1.6-2 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.5-5 pve-cluster: 6.4-1 pve-container: 3.3-5 pve-docs: 6.4-2 pve-edk2-firmware: 2.20200531-1 pve-firewall: 4.1-3 pve-firmware: 3.2-3 pve-ha-manager: 3.1-1 pve-i18n: 2.3-1 pve-qemu-kvm: 5.2.0-6 pve-xtermjs: 4.7.0-3 qemu-server: 6.4-2 smartmontools: 7.2-pve2 spiceterm: 3.1-1 vncterm: 1.6-2 zfsutils-linux: 2.0.4-pve1
 
Last edited:
Are there any logs from the time of the crash? Both on the host ('journalctl -e' and 'dmesg') and potentially from the guest (Event Viewer).

Can you test if this also occurs with a Linux Guest? (it should still work with Windows too, but may help identify the issue)
 
i can't test this problem with linux because i don't have a linux machine. I saved the log of a crash. the next time the machine crashes I'll post the log here.
 

Attachments

DpunktS said:
i can't test this problem with linux because i don't have a linux machine.
Click to expand...
There's always the option of making one ;)

But truthfully, I doubt it'd make a difference. The log you posted would indicate a kernel or hardware error (potentially related to this GitHub issue?). You could try updating to our 5.11 kernel by running apt install pve-kernel-5.11, then reboot the host. Check you got it right with uname -a - it should show '5.11.21-1-pve' (at the time of writing).
 
I have now updated the kernel. let's see how long the Windows 10 machine runs.
root@intelnuc:~# uname -a Linux intelnuc 5.11.17-1-pve #1 SMP PVE 5.11.17-1~bpo10 (Mi, 12. Mai 2021 12:45:37 +0200) x86_64 GNU/Linux
 
I am also surprised that when I restart Proxmox I have used a working memory of 18GB. The memory also grows up to 26GB until the VM crashes. I installed 31gb Ram and I also deactivated balloon. My 3 VMs only got 16gb assigned.
 
If you did not set a maximum, ZFS can use upto 50% of your systems memory. I believe VMs with device passthrough cannot give memory back to the host (ballooning), which might also be the case with GVT-g.
 
ok there the question is clarified with the memory. I deactivated ballooning anyway. It would be nice if the VM would still run now.
 
I have now kvm.ignore_msrs=1deactivated but proxmox crashes completely after 2 days. I was able to do this in such a way that this always happens when the memory reaches the 26 GB limit.
 
There is no one who can help me to get an intel nuc 10 i5 (Intel 10210U) with gvt-g to work. Proxmox 7.0 with cores 5.11 did not solve the problem either.
 
You must log in or register to reply here.
Top Bottom