Recent content by derMischka

In my Case the solution for change resolution was following command: xrandr --output Virtual-1 --mode 1920x1200 if it does not work try Virtual-0 instead of Virtual-1 der mischka

Till now, i found no solution. In my Proxmox configuration is still the kernel version 5.11.22-7 pinned.

Maybe someone have enough skills to use this information: https://github.com/intel/gvt-linux/commit/58586680ffadc37636120d9f59955aa5f7a32b7d

update: root@nas:~# qm start 110 kvm: -device vfio-pci,host=0000:00:02.0,id=hostpci0,bus=pci.0,addr=0x10: vfio 0000:00:02.0: error getting device from group 1: Invalid argument Verify all devices in group 1 are bound to vfio-<bus> or pci-stub and not already in use start failed: QEMU exited...

Currently I use the last kernel version that work for me (5.11.22-7). I select the Kernel at Start in the Boot-Menu.

The VM using the GPU runs Kodi. I think it wouldn't work as LXC because of the Peripherials and mounting stuff. But the real Problem is that the Configuration runs without any problems till Kernel 5.11.22-7. What happend after that Kernel version that this configuration doesn't work.

Hi, this problem seems to be present since Proxmox-Kernel > 5.11.22-7 visit this Thread https://forum.proxmox.com/threads/p...nel-5-13-19-1-upgrade-from-7-0-to-7-1.100961/ maybe we should bundle the cases (proxmox/kernel version and graphic version/model). Mischka

Hi, this problem seems to be present since Proxmox-Kernel > 5.11.22-7 visit this Thread https://forum.proxmox.com/threads/p...nel-5-13-19-1-upgrade-from-7-0-to-7-1.100961/ maybe we should bundle the cases (proxmox/kernel version and graphic version/model). Mischka

Hi, kann es sein, dass Du eine aktuelle Proxmox-Version mit Kernel > 5.11.22-7 (kannst du mit "uname -r" anzeigen lassen) mit einer Intel iGPU benutzt? Wir sind schon eine kleine Gruppe...

update: root@nas:~# uname -r 5.15.35-2-pve root@nas:~# qm start 110 kvm: -device vfio-pci,host=0000:00:02.0,id=hostpci0,bus=pci.0,addr=0x10: vfio 0000:00:02.0: error getting device from group 1: Invalid argument Verify all devices in group 1 are bound to vfio-<bus> or pci-stub and not already...

It should not really be a problem by the BIOS. All Kernel versions till 5.11.22 works fine. There must be a change in the kernel after 5.11.22 that raised that problem with passthrough. I think, it is specially the part of Intel iGPU driver because it seems to me that only some Intel iGPUs...

root@nas:~# lspci 00:00.0 Host bridge: Intel Corporation Gemini Lake Host Bridge (rev 03) 00:00.1 Signal processing controller: Intel Corporation Celeron/Pentium Silver Processor Dynamic Platform and Thermal Framework Processor Participant (rev 03) 00:02.0 VGA compatible controller: Intel...

I tested your fix, but it doesn't work. root@nas:~# echo 1 > /sys/bus/pci/devices/0000\:00\:02.0/remove root@nas:~# echo 1 > /sys/bus/pci/rescan root@nas:~# qm start 110 kvm: -device vfio-pci,host=0000:00:02.0,id=hostpci0,bus=pci.0,addr=0x10: vfio 0000:00:02.0: failed to setup container for...

The new Kernel 5.15.35-1-pve has also still the problem :-(

I tested also the Kernel Version 5.13.14-1-pve But also the error after qm start 110 kvm: -device vfio-pci,host=0000:00:02.0,id=hostpci0,bus=ich9-pcie-port-1,addr=0x0: vfio 0000:00:02.0: error getting device from group 1: Invalid argument Verify all devices in group 1 are bound to vfio-<bus>...