• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting SOLVED: Transcoding not working after migrating VM in the same host

     
    • 0 Vote(s) - 0 Average

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

    paaradiso
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2025 Jun
    Reputation: 0
    #1
    Yesterday, 12:41 AM (This post was last modified: Yesterday, 03:34 AM by paaradiso. Edited 2 times in total.)
    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?
    Go to solution
    bitmap
    Offline

    Community Moderator

    Posts: 915
    Threads: 9
    Joined: 2023 Jul
    Reputation: 30
    #2
    Yesterday, 02:47 AM
    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.
    Jellyfin 10.10.7 LSIO Docker | Ubuntu 24.04 LTS | i7-13700K | Arc A380 6 GB | 64 GB RAM | 79 TB Storage

    [Image: AIL4fc84QG6uSnTDEZiCCtosg7uAA8x9j1myFaFs...qL0Q=w2400]
    paaradiso
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2025 Jun
    Reputation: 0
    #3
    Yesterday, 03:23 AM (This post was last modified: Yesterday, 03:24 AM by paaradiso. Edited 1 time in total.)
    (Yesterday, 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]
    paaradiso
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2025 Jun
    Reputation: 0
    #4
    Yesterday, 03:34 AM (This post was last modified: Yesterday, 03:34 AM by paaradiso.)
    I fixed it, I think by installing drivers on the host VM.
    « Next Oldest | Next Newest »

    Users browsing this thread: 2 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode