Keine VM startet mehr über Graka

[chap10]

Hey

vor 1 Tag noch ganz normal kurz bißchen gezockt und die VM normal runter gefahren, Heute bekomme ich die folgende Meldung wenn ich die VMs starten will über Graka.

Ohne Graka gibts kein Problem, mit kommt die Meldung.
Egal welches Betriebssystem usw.

Proxmox natürlich auf der Aktuellsten Version vor 2 Tagen upgegradet.

Wenns hilft

CPU(s) 32 x AMD Ryzen 9 5950X 16-Core Processor (1 Socket)

Kernelversion Linux 5.15.35-1-pve #1 SMP PVE 5.15.35-3 (Wed, 11 May 2022 07:57:51 +0200)

PVE-Manager-Version pve-manager/7.2-4/

 

[Dunuin]

PVE wurde vor Kurzem von 7.1 auf 7.2 gebracht. Unter anderem gab es da einen Wechsel von Kernel 5.13 auf 5.15 und einige "Known Issues" bezüglich PCI passthrough:

Known Issues

• Setups mounting a QNAP NFS share could not be mounted with NFS version 4.1 with kernel pve-kernel-5.15.30-2-pve - the issue has been mitigated in kernels pve-kernel-5.15.35-2 and above.If your QNAP NFS share cannot be mounted upgrade the kernel and reboot.As an alternative mitigation you can explicitly set the NFS version to 4 (not 4.1 or auto).
• PCI(e) pass through related:
  • Systems passing through a GPU may be affected from the switch to the SYS_FB (system frame buffer) KConfig build options using the simplefb module as driver in the new default 5.15 based kernel.The sys-fb allows taking over the FB from the firmware/earlier boot stages. Note that Proxmox VE uses the legacy simplefb driver over the modern simpledrm one due to regressions and issues we encountered on testing with the latter.Most of those issues are already fixed in newer kernels and Proxmox VE may try to switch to the modern, DRM based FB driver once it moves to 5.17, or newer, as its default kernel.If your systems is configured to pass through the (i)GPU, and you had to avoid the host kernel claiming the device, you may now need to also add video=simplefb:off to the kernel boot command line.
  • Setups using vendor-reset for PCIe pass through need to adapt to changes of the new default 5.15 based kernel, see For details see this issue.They must run the command echo 'device_specific' > /sys/bus/pci/devices/<PCI-ID>/reset_method before the VM is started. This can be automated by using a systemd service or using a on-boot cron script.Alternatively one can also use a VM hook script with the pre-start hook.
• intel_iommu now defaults to on. The kernel config of the new 5.15 series enables the intel_iommu parameter by default - this can cause problems with older hardware (issues were reported with e.g. HP DL380 g8 servers, and Dell R610 servers - so hardware older than 10 years)The issue can be fixed by explicitly disabling intel_iommu on the kernel commandline (intel_iommu=off) following the reference documentation - https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysboot_edit_kernel_cmdline
• Certain systems may need to explicitly enable iommu=pt (SR-IOV pass-through) on the kernel command line.There are some reports for this to solve issues with Avago/LSI RAID controllers, for example in a Dell R340 Server booted in legacy mode.

Ggf mal zurück zu Kernel 5.13 und testen ob es dann geht und außerdem prüfen ob dich die "Known Issues" betreffen.