SOLVED: Transcoding not working after migrating VM in the same host

SOLVED: Transcoding not working after migrating VM in the same host - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: Transcoding not working after migrating VM in the same host (/t-solved-transcoding-not-working-after-migrating-vm-in-the-same-host)

Transcoding not working after migrating VM in the same host - paaradiso - 2025-07-01

I have a machine with a 10400 running PVE. I used to run jellyfin with podman in an alma LXC, but I've been moving everything over to a NixOS VM with podman.

The configuration is the exact same, but it now refuses to transcode anything.

Old configuration: https://sourceb.in/v0E1LNCTPO
New configuration: https://sourceb.in/7AAy3PD2DC - I have tried adding just /dev/dri/renderD128 and adding the user to a group, but nothing works.

Inside the container, the permissions are correct:



alpha@3a084e236d37:/dev/dri$ ls -la

total 0

drwxr-xr-x 2 root root      100 Jun 30 15:12 .

drwxr-xr-x 6 root root      360 Jun 30 15:12 ..

crw-rw---- 1 root tape 226,  0 Jun 30 15:12 card0

crw-rw---- 1 root tape 226,  1 Jun 30 15:12 card1

crw-rw-rw- 1 root  303 226, 128 Jun 30 15:12 renderD128

alpha@3a084e236d37:/dev/dri$ test -r renderD128

alpha@3a084e236d37:/dev/dri$ echo $?

0

alpha@3a084e236d37:/dev/dri$ test -w renderD128

alpha@3a084e236d37:/dev/dri$ echo $?

0

vainfo also works and outputs correct information: https://sourceb.in/9kA2Gy52t6

ffmpeg error with QSV, VPP off and regular tonemapping on:



[AVHWDeviceContext @ 0x6537ff70ae40] No VA display found for device /dev/dri/renderD128.

Device creation failed: -22.

Failed to set value 'vaapi=va:/dev/dri/renderD128,driver=iHD' for option 'init_hw_device': Invalid argument

Error parsing global options: Invalid argument

VAAPI, VPP off, regular tonemapping on:



[AVHWDeviceContext @ 0x57225032db00] Failed to get number of OpenCL platforms: -1001.

Device creation failed: -19.

Failed to set value 'opencl=ocl:0.0' for option 'init_hw_device': No such device

Error parsing global options: No such device

VAAPI, VPP on and regular tonemapping off:



Device creation failed: -542398533.

[vist#0:0/hevc @ 0x62d6f742b440] [dec:hevc @ 0x62d6f7427bc0] No device available for decoder: device type vaapi needed for codec hevc.

[vist#0:0/hevc @ 0x62d6f742b440] [dec:hevc @ 0x62d6f7427bc0] Hardware device setup failed for decoder: Generic error in an external library

[vost#0:0/h264_vaapi @ 0x62d6f73f52c0] Error initializing a simple filtergraph

Another container (immich) is transcoding media normally, so the iGPU is properly passed through to the VM.

Does anyone know what's wrong?

RE: Transcoding not working after migrating VM in the same host - bitmap - 2025-07-01

Looks like the iGPU hasn't been passed to the VM to be passed into Docker. Could be a driver issue, but the hardware doesn't appear to be valid.

RE: Transcoding not working after migrating VM in the same host - paaradiso - 2025-07-01

(2025-07-01, 02:47 AM)bitmap Wrote: Looks like the iGPU hasn't been passed to the VM to be passed into Docker. Could be a driver issue, but the hardware doesn't appear to be valid.

It has been passed through, and vainfo recognises it: https://sourceb.in/hdMi9oVbSi

[Image: sOT4OMl.png]

RE: Transcoding not working after migrating VM in the same host - paaradiso - 2025-07-01

I fixed it, I think by installing drivers on the host VM.