[SOLVED] Proxmox LXC Jellyfin Intel QSV unable to transcode with kernel (6.8.12-5-pve)

ern.xyz

New Member
Dec 20, 2024
2
0
1
Recently I had updated my kernel to 6.8.12-5-pve from 6.5.13-6-pve. I had previously pinned my kernel to 6.5.13-6-pve because I was having stability issues with 6.8 initially. I was able to fix the stability issue, but I noticed my LXC container that has Jellyfin and hardware acceleration using Intel Quick Sync (QSV) broke with the kernel update. I am therefore unable to transcode using QSV. I tried pinning the kernel back to 6.5.13-6-pve, but I am still unable to transcode.

With the 6.8.12-5-pve kernel update, looking at the Jellyfin FFmepg log file, I noticed that the iGPU isn't even found:
Code:
[AVHWDeviceContext @ 0x5d4b28181280] No VA display found for any default device. Device creation failed: -22.
Failed to set value 'vaapi=va:,kernel_driver=i915,driver=iHD' for option 'init_hw_device': Invalid argument
Error parsing global options: Invalid argument

Digging deeper, looking at the LXC /dev/dri I noticed that the permissions and GID/UID for renderD128 changed and has no access.

Code:
root@Jellyfin-LXC:~# ls -l /dev/dri
total 0
crw-rw---- 1 root video 226, 0 Dec 20 15:24 card0
---------- 1 root root       0 Dec 20 16:12 renderD128

When I originally created the LXC container, I had properly passed the iGPU and made sure that my Proxmox Node had the proper configuration within the /etc/pve/lxc/<CONTAINER_ID>.conf as written in Jellyfin's guide Link

One thing I noticed on my Proxmox Node, renderD128 does not show up:

Code:
root@darkrook:~# ls -l /dev/dri
total 0
drwxr-xr-x 2 root root      60 Dec 20 10:24 by-path
crw-rw---- 1 root video 226, 0 Dec 20 10:24 card0

At this point I am at a lost. On the LXC, As a test I tried chmod -R 777 on renderD128 to see if Jellyfin would be able to utilize the iGPU, but no luck. I also tried following this solution, but until I get Jellyfin with the correct permissions for renderD128 it has not been able to work. Link.

I also tried following this thread to resolve the missing iGPU issue on my Proxmox node, but no luck here. Proxmox Thread

Specs:
Proxmox: 8.3.2
Kernel 6.8.12-5
LXC: Ubuntu 22.04.5 LTS
Jellyfin: 10.10.1
 
It was the simplest oversight. I have a Supermicro X11SCH-LN4F motherboard. When I updated the BIOS, it had reset my previous BIOS settings and forced the onboard graphics. I had to re-enable the iGPU passthrough at the BIOS level.

Followed these steps to resolve issue:

Happy to report that on the newer X12 series with ASPEED IPMI, you can also use the iGPU alongside the KVM when you set the following options:
- "Advanced -> Chipset Configuration -> System Agent (SA) Configuration -> Graphics -> Primary video to PCI (this selects the ASPEED iKVM GPU as primary)
- "Advanced -> Chipset Configuration -> System Agent (SA) Configuration -> Graphic -> Internal Graphics to Enabled (this force enables the iGPU on the Intel CPU)
- "Advanced -> Chipset Configuration -> System Agent (SA) Configuration -> Memory Configuration -> Max TOLUD" to "1GB" (2GB can also work, 3GB does not as it will hang in POST code 19)

Link to solution
 

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!