Might be a better question for someone who knows more JF ffmpeg configs, but I think the HEVC up top should be checked and the bottom range extended hevc should be unchecked. I think you should have AV1 support too.
Worst case, start with h264 and move down the list
Just checked one of mine, VAAPI is where I’m set, with acceleration working. 7th or 8th gen or so on that box, so VAAPI should do the trick for you.
What do you have above that?
There should be a hardware acceleration dropdown, and then a device below that. Since you have /dev/dri/renderD128, that should be in the “device” field, and the Hardware Acceleration dropdown should be QSV or VAAPI (if one doesn’t work, do the other)
Ok lets start with that rendering - seeing those is good! You should only need to add some group access, so run this:
groups jellyfin
The output should just say “jellyfin” right now. Thats the user thats running the Jellyfin service. So lets go ahead and…
usermod -a -G video,render jellyfin
groups jellyfin
You should now see the jellyfin user as a member of jellyfin, video, and render. This gives access for the jellyfin user to make use of the gpu/hardware acceleration.
Now restart that jellyfin and try again!
LXC is going to be better, IMO. And we can definitely get hardware acceleration going.
So first, let’s do this from the console of the lxc:
ls -la /dev/dri/
Is there something like card0 and renderD128 listed?
Great!
Transcoding we should be able to sort out pretty easily. How did you make the lxc? Was it manual, did you use one of the proxmox community scripts, etc?
For transferring all your JF goodies over, there are a few ways you can do it.
If both are on the NAS, I believe you said you have a synology. You can go to the browser and go to http://nasip:5000/ and just copy around what you want if its stored on the NAS as a mount and not inside the container. If its inside the container only its going to be a bit trickier, like mounting the host as a volume on the container, copying to that mount, then moving around. But even Jellyfin says its complex - https://jellyfin.org/docs/general/administration/migrate/ - so be aware that could be rough.
The other option is to bring your docker container over to the new VM, but then you’ve got a new complication in needing to pass through your GPU entirely rather than giving the lxc access to the hosts resource, which is much simpler IMO.
We shouldn’t be complacent or lose hope.
I’m… not exactly a fan of the existence of a state in general, but I’ll happily support more dem-socialists and the ousting of establishment democrats (aka “traditional” republicans with a blue sign).
That usually means something has changed with the storage, I’d bet there is a lingering reference in the .conf to the old mount.
The easiest? Just delete the container, start clean. Thats what nice about containers by the way! The harder would be mounting the filesystem of the container, and taking a look at some logs. Which route do you want to go?
For the VM, its really easy. Go to the VM, and open up the console. If you’re logging in as root, commands as is, if you’re logging in as a user, we’ll need to add a sudo in there (and maybe install some packages / add the user to the sudoers group)
apt update && apt upgradeapt install nfs-commonmkdir /mnt/NameYourMountsudo mount -t nfs 192.168.1.100:/share/dir /mnt/NameYourMountls -la /mnt/NameYourMount. If you have an issue here, pause and come back and we’ll see whats going on.nano /etc/fstab192.168.1.100:/share/dir /mnt/NameYourMount nfs defaults,x-systemd.automount,x-systemd.requires=network-online.target 0 0ctrl+x then yls -la /mnt/NameYourMount to confirm you’re all setKind of.
Its a barometer, and it usually features some degree of losses for the party in power. The degree of which is a big indicator for the midterms. While the presidents party tends to lose out overall in off-years, the degree to which can vary drastically.
Off year elections do not have sweeping losses or historically significant voter turnout though. They also dont generate anywhere near the kind of media attention this year saw, or the historic amounts of money being put into a mayoral election as we saw in NYC.
We shouldn’t downplay the significance of yesterdays election. And it was significant.
These weren’t midterms, they were an off-year election. The midterms will be next year.
They are usually low turnout, but saw a historic turnout in NY and NJ, not sure about the others offhand.
Off-years you do not typically see this kind of sweeping response, its absolutely atypical.
I’m not suggesting its time to stop, but clarifying that this is not the norm.
Ok we can remove it as an SMB mount, but fair warning a few bits of CLI to do this thoroughly.
systemctl list-units "*.mount" That said - I like to be sure, so lets do a few more things.
umount -R /mnt/pve/thatshare - Totally fine if this throws an errorcat /proc/mounts - a whooole bunch of stuff will pop up. Do you see your network share listed there? If so, lets go ahead and delete that line. nano /proc/mounts, find the line if its still there, and remove it. ctrl+x then y to save.Ok, you should be all clear. Lets go ahead and reboot one more time just to clear out anything if you had to make any further changes. If not, lets re-add.
Go ahead and add in the NAS using NFS in the storage section like you did previously. You can mount to that same directory you were using before. Once its there, go back into the Shell, and lets do this again: ls -la /mnt/pve/thenameofyourmount/
Is your data showing up? If so, great! If not, lets find out whats going on.
Now lets add back to your container mount. You’ll need to add that mount point back in again with: pct set 100 -mp0 /mnt/pve/NAS/media,mp=/media (however you had it mounted before in that second step).
Now start the container, and go to the console for the container. ls -la /whereveryoumountedit - if it looks good, your JF container is all set and now working with NFS! Go back to the options section, and enable “Start at Boot” if you’d like it to.
Onto the VM, what distribution is installed there? Debian, fedora, etc?
For the record, I prefer NFS
And now I think we may have the answer…
OK so that command is for LXCs, and not for VMs. If youre doing a full VM, we’d mount NFS directly inside the VM.
Did you make an LXC or a VM for 102?
If its an lxc, we can work out the command and figure out what’s going on.
If its a VM, we’ll get it mounted with NFS utils, but how is going to depend on what distribution you’ve got running on there (different package names and package managers)
Ok, lets take a step back then and check things this way.
In shell (So datacenter, the host, then shell), if you enter ls -la /mnt/pve/thenameofyourmount/, do you get an accurate and current listing of the contents of your nas?
If you’ve got nothing under it, yeah.
OK, what I’d probably do is shutdown proxmox, reboot your nas, wait for the nas to be fully up and running (check if you can access it from your regular computer over the lab), then boot up the proxmox server.
Then run that command again, you should see a result.
Its possible you’ve got some conflicting stuff going on if you did manual edits for the storage, which may need to be cleaned up.
What do you get putting in:
showmount <ip address of NAS>
No worries!
So if you’ve got docker containers going already, you don’t need them to be LXCs.
So why not keep them docker?
Now there are a couple of approaches here. A VM will have a bit higher overhead, but offers much better isolation than lxc. Conversely, lxc is lightweight but with less host isolation.
If we’re talking the *arr stack? Meh, make it an lxc if you want. Hell, make it an lxc with dockge installed, so you can easily tweak your compose files from the web, convert a docker run to compose, etc.
If you have those configs (and their accompanying data) stored on the NAS itself - you dont have to move them. Let’s look at that command again…
pct set 100 -mp0 /mnt/pve/NAS/media,mp=/media
So let’s say your container data is stored at /opt/dockerstuff/ on your NAS, with subdirectories of dockerapp1 and dockerapp2. Let’s say your new lxc is number 101. You have two options:
pct set 101 -mp0 /mnt/Pve/NAS/opt/dockerstuff,mp=/opt/dockerstuff
pct set 101 -mp0 /mnt/Pve/NAS/opt/dockerstuff/dockerapp1,mp=/opt/dockerstuff/dockerapp1
pct set 101 -mp1 /mnt/Pve/NAS/opt/dockerstuff/dockerapp2,mp=/opt/dockerstuff/dockerapp2
Either will get you going
This line right here shares it with the LXC, I’ll break it down for you:
pct set 100 -mp0 /mnt/pve/NAS/media,mp=/media
pct is the proxmox container command, youre telling it to set the mount point (mp0, mp1, mp2, etc). That point on the host is /mnt/pve/yourmountname. In the container is on the right, mp=/your/path/. So inside the container if you did an ls command in the directory /your/path/, it would list the files in /mnt/pve/yourmountname.
The yourmountname part is the name of the storage you added. You can go to the shell at the host level in the GUI, and go to /mnt/pve/ then enter ls and you will see the name of your mount.
So much like I was mentioning with the GPU, what youre doing here is sharing resources with the container, rather than needing to mount the share again in your container. Which you could do, but I wouldn’t recommend.
Any other questions I’ll be happy to help as best as I can.
Edit: forgot to mention, if you go to the container and go to the resources part, you’ll see “Mount Point 0” and the mount point you made listed there.
If youre going LXC, its not going to matter much of you just map GIDs and provide the LXC access to the host.
Side bonus, multiple LXCs and they can all share that GPU. This is what I do, I have a couple of JF instances among other containers that use the GPUs.
Edited to add: Well, nvidia itself can be a pain. But that’d be because nvidia.
How should Jellyfin be set up, lxc or vm
Either way. I prefer lxc, personally, but to each their own. lxc I think is drastically easier, in part because you don’t need to pass through the whole GPU…
Is there a way to enable iGPU to pass to an lxc or VM without editing a .conf in nano?
You don’t need to pass the igpu, you just need to give the LXC access to render and video groups, but yes, editing the conf is easiest. I originally wrote out a bunch here, then remembered there is a great video.
https://www.youtube.com/watch?v=0ZDr5h52OOE
My Synology NAS is mounted to the host, but making mount points to the lxc doesn’t actually connect data
Do they show up as resources? I add my mount points at the CLI personally, this is the best way imo:
pct set 100 -mp0 /mnt/pve/NAS/media,mp=/media
This is done from the host, not inside the LXC.
Does your host see the mounted NAS? After you added the mount point, did you fully stop the container and start it up again?
Edit: You can just install curl/wget/etc BTW, its just Debian in there.
apt install curl
Edit 2: I must have glossed over the mount part.
Dont add your network storage manually, do it through proxmox as storage, by going to Datacenter > Storage > Add, and enter the details there. This will make things a lot easier.
Also may be good for c/jellyfin, but what I’d see if you could do is leverage a backup tool. Export and download, then import, all from the web. I know there is a built in backup function, and I recall a few plugins as well that handled backups.
Seems to me that might be the most straightforward method - but again, probably better with a more jellyfin focused comm for that. I have moved that LXC around between a bunch of machines at this point, so snapshots and backups via proxmox backup server are all I need.