I have a used Lenovo Thinkcenter 910 with a i5 7500T running Proxmox with Linux Mint in one VM and Adguard running in another. I’m just getting started so I am reading/searching for tons of answers still
I was hoping to host Jellyfin within Linux Mint. It works pretty well, but I did notice while watching a movie the CPU was pretty well pegged out. I wanted to enable hardware based acceleration but when I started reading setup guides to hope to understand what I was doing, I think I may have painted myself into a corner already.
I think I need to tell Proxmox to pass the hardware acceleration on to Linux, and then get Linux to, but also some of the things I have read make it sound like I need to have set up the VM from the beginning this way.
Am I trying to do this the hard way somehow? Does anyone have any suggestions on the best guide to follow for this?
You must log in or # to comment.
Check out the following link - I am pretty sure its what I used to get it all working.
https://3os.org/infrastructure/proxmox/gpu-passthrough/igpu-passthrough-to-vm/
There’s no need for adding all of those flags to your kernel command line - just the ones below will do the job:
intel_iommu=on iommu=pt video=efifb:off modprobe.blacklist=snd_hda_intel,snd_hda_codec_hdmi,i915
OP just needs to be aware that turning off the EFI framebuffer as above will result in no video output for the Proxmox host.
If you need further IOMMU group separation and your motherboard doesn’t support ACS, then you can add:
pcie_acs_override=downstream
If you run into problems with booting Proxmox, then you can simply remove the lines above at boot and then troubleshoot after.
second to this, and to add on that while it’s gotten easier (and yes, even with this guide, it’s much easier than it used to be) back up your system. Hopefully nothing goes wrong, but you are messing with the kernel, make sure you’re mentally prepared to have to build it all from the ground up.
Thanks for this! Looking forward to trying it out!
So this definitely seems like the guide that helped the most. I spent more hours than I would like to admit working on this over this weekend.
I am trying to figure out if I have a way to do what I want to here. When it was all said and done I could no longer log into the remote computer I was using to run my Jellyfin server. I have been messing around a little bit using a Linux PC with that, and enjoyed that aspect of things, but it seems like once you get hardware acceleration going, you cannot see the desktop anymore. There were several warnings about this so I wasn’t entirely surprised when it happened.
I think I am going to end up needing to get rid of the proxmox part, and just run Linux directly on the computer if I want to do this, and remote into it. It is currently not hooked up to a monitor and is actually on top of my kitchen cabinets out of the way. It was a fun challenge and I learned a lot I think.
Proxmox has an official guide on how to do this, which inlcudes these examples.
There’s also a video from Jim’s Garage where he sets up GPU passthrough in an unprivileged LXC container within proxmox.
See if any of that helps.
Here is an alternative Piped link(s):
GPU passthrough in an unprivileged LXC conatiner
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.
I did this recently and I wish I could answer you, but I’m on mobile and don’t remember exactly what got it working. I also referenced the guide linked below, along with the proxmox documentation.
If you start blacklisting drivers, you’ve gone too far for passing through Intel quicksync. I think I’m the end it was a pretty basic config, like checking motherboard settings and adding text to the grub config.
Also don’t guides say you have to use q35 as the machine type for the VM, but that didn’t work for me. Only 440fx works for me.
Don’t do that. Run Jellyfin in its own VM with a GPU passed though via pcie passthough.
That’s going to be almost impossible to do with an iGPU. Makes way more sense to pass through to LXC.
It takes about 2-3 clicks. What do you mean impossible? LXC is likely faster but it takes more setup.
2-3 clicks? That’s hilarious!
These are the steps it actually takes: https://3os.org/infrastructure/proxmox/gpu-passthrough/igpu-passthrough-to-vm/
That’s the best case scenario where it actually works without significant issues, which I am told is rarely the case with iGPUs.
In my case it was considerably more complicated as I have two GPUs from Nvidia (one used for host display outout), so I needed to block specific IDs rather than whole kernel modules.
Plus you lose display access to the Proxmox server which is important if anything goes wrong. You can also only passthrough to one VM at a time. Compared to using LXC you can passthrough to almost unlimited containers, and still have display output for the host system. It almost never makes sense to use PCIe passthrough on an iGPU.
The reason to do passthrough is for gaming on Windows VMs. Another reason is because Nvidia support on Proxmox is poor.
This is a guide to do passthrough with LXC: https://blog.kye.dev/proxmox-gpu-passthrough
It’s actually a bit less complicated for privileged LXC, as they are having to work around the restrictions of unprivileged LXC containers.
Its always worked well for me. I passthough my dedicated graphics and USB controller to a Pop os VM and then the integrated graphics to the Jellyfin VM. I initially had to enable virtualization extensions and for the dedicated graphics there was a bit more setup but for the most part it is reasonable.
My point is it’s not actually much (or potentially any) simpler to use PCIe passthrough than using an LXC. Yet it comes with more resource usage and more restrictions. Some hardware is more difficult to pass through, especially with iGPUs. I don’t even think all iGPUs even use PCIe.
iGPUs are incredibly easy to pass though and are PCIe devices.
Not all of them. Have a look at a Raspberry Pi or Apple Silicon devices. In fact most ARM SoCs I am fairly sure don’t use PCIe for their iGPUs. This makes sense when you think about the unified memory architecture some of these devices use. Just in case you aren’t aware Proxmox does indeed run on a raspberry pi, and I am sure they will gain support for more ARM devices in the future. Though I believe an x86 device with unified memory could also have problems here.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters DNS Domain Name Service/System LXC Linux Containers PCIe Peripheral Component Interconnect Express
[Thread #584 for this sub, first seen 9th Mar 2024, 13:25] [FAQ] [Full list] [Contact] [Source code]
deleted by creator
