Search results

Let me know how you go with that. Also did you try with a container other than Jellyfin? Because it works for me with frigate.

@James Crook you replied to my post on Reddit regarding this issue. The thread you refer to above is useful. In my case, I can pass through the iGPU and it works for another container (frigate) but is still dying on Jellyfin. I’ve got an issue open with jellyfin and also the mesa team (see link...

Sorry to hear you had a similar issue. Been there and done that. The good news is you should be able to recover everything if the images are still there. I don’t have the exact command I used any longer. However, you would use dd and refer to the lvm volume you want to backup. A guide for using...

My understanding is that if you get the output you see from vainfo then the GPU pass-through has worked. Which means the remaining issue is within the tool/application you are trying to configure. I haven’t used Plex for many years so I can’t speak for it. According to the logs, it’s looking to...

From here it looks like Plex doesn’t support AMD for transcoding. Can you try with Jellyfin via docker container perhaps to see if you have the pass through working?

hmm also looking at the logs again, the errors are about loading cuda which is incorrect for AMD integrated graphics. Did you configure transcoding to use VAAPI rather than nvenc (which is for nvidia)?

Try this for the permissions (run it on the Proxmox host): sudo chmod g+rw /dev/dri/renderD128 sudo chmod g+rw /dev/dri/card0

Getting integrated GPU's to pass through can be especially tricky. It could also depend on IOMMU groupings from your motherboard and CPU. On the software side, kernel and mesa libraries are the more important. While you are trying to get it working, you could install docker on your Proxmox...

Yes it could be different because you have a 5x series with integrated GPU. I'm not sure on what the kernel and new library compatibility requirements are for it. A quick Google seems to suggest others have passed through the igpu successfully.

Hmm if you can see card0 etc. then it is passing the GPU through. What happens if you run vainfo? Also, can you make the container privileged?

It might be worth sharing your configuration for the lxc container and also the version of Proxmox you are running, including kernel. Also, any error messages you are getting or where it is not working. As an example, for lxc, you need to have special entries for passing through the GPU in the...

After spending hours googling and looking at logs, I ended up finding a similar issue reported in Ubuntu forums. After rebooting my router, everything magically started working again. Must have been a weird network/routing issue.

Hi, I'm using the latest Proxmox on a Ryzen 2700. I've been running two Windows VM's very stable for a long while now. I suddenly noticed I couldn't connect remotely and thought the system had crashed so rebooted. After checking the disk via smartctl, fsck etc. I discovered that its the...

Follow the instructions from the wiki to create an lcx container and once done, edit the container‘s conf file directly to add the additional text from above. Your conf file will be in /etc/pve/lxc/<containerid>.conf.

Fixed with pct mount and pct unmount.

Hi, Very strangely I followed the above guide and after stopping the lxc container, it won't restart. The error is: root@littleman:/etc/pve/lxc# lxc-start -n 100 -F --logfile /tmp/log lxc-start: 100: conf.c: run_buffer: 316 Script exited with status 1 lxc-start: 100: start.c: lxc_init: 816...

I changed to: arch: amd64 cores: 2 features: nesting=1 hostname: frigate memory: 4096 net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=xxx,ip=dhcp,type=veth ostype: debian rootfs: local-lvm:vm-102-disk-0,size=32G swap: 512 lxc.mount.entry: /dev/bus/usb/003/004 dev/bus/usb/003/004 none...

Hi, I upgraded one of my systems to the latest 7.0 and one of the LXC containers will not start. There are no errors displayed, it's just that the container doesn't start, or seems to start momentarily and then stop. My full config is: arch: amd64 cores: 2 features: nesting=1 hostname...

Definitely need updated mesa and libva alongside the kernel. Not sure about the AMD firmware either. I've got Jellyfin working in docker in LXC fine. I tried installing the updated libraries into the frigate container but while vainfo shows transcoding is supported, frigate is not working...

Not 100% sure but definitely Kernel 5.4+ as this includes amdgpu. Then you need updated VAAPI related libraries like Mesa and libva. I've got upgraded Mesa in my frigate container but as compared to Jellyfin, I don't have updated libva and can't seem to find the same version that Jellyfin is...