Passthrough to VM crashes Proxmox

deniax

New Member
Jan 23, 2023
15
0
1
Hi,

I am having a problem with trying to passthrough the iGPU of my Intel i7-13700 to a VM.
But when I do that, it crashes the whole Proxmox and I need to restart it again.

Because it's a fairly new CPU, I updated Proxmox to pve-kernel-6.1.
But as shown in the screenshot, the vendor is detected, but the device is still empty.

Nevertheless, I found out which deviceID was the VGA one and I passed that through to the VM.

Does Proxmox crash because of missing driver support (Although in the lspci it says Kernel driver in use: i915), or because the VGA device I passthrough, is actually used by Proxmox itself and cant be used for passthrough?

GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt initcall_blacklist=sysfb_init"
lspci is attahed as well :)
Code:
root@pve:~# vainfo
error: can't connect to X server!
libva info: VA-API version 1.10.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_10
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
root@pve:~# /dev/dri# ls
-bash: /dev/dri#: No such file or directory
 

Attachments

  • Monosnap pve - Proxmox Virtual Environment 2023-01-26 21-38-18.png
    Monosnap pve - Proxmox Virtual Environment 2023-01-26 21-38-18.png
    156.2 KB · Views: 7
  • lspci.txt
    lspci.txt
    19.4 KB · Views: 3
Last edited:
Hey Den,

I cannt even do a proper install PVE on the the device yet with 17-13700

How do you do that?

It said something the frame buffer