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/
this post was submitted on 06 Mar 2024
41 points (97.7% liked)
Selfhosted
40173 readers
729 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
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.
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]
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.
If it wasn't connected via PCIe how would it talk to the GPU. Anyway Proxmox does in fact not officially support ARM so that is a pretty miniscule use case. I'm not even sure why you would want Proxmox on a low powered device.
For me PCIe pass though is the easiest. Virtualization adds little overhead in terms of raw performance so it isn't a big deal. If you prefer LXC that's fine but my initial statement was based on my own experiences.
AMBA/AXI-bus in the case of the Pi. GPUs existed long before PCIe did lol.
One some x86 systems the CPU and GPU aren't connected with PCIe either. AMD has infinity fabric that they use for things like the Instinct MI300 and some of their other APUs
Edit: Oh yeah also ARM isn't just low power anymore. It's used in data centers and super computers these days. Even if it was there is lots of stuff you can do with a low power node, including running file servers, DNS or Pi hole, web servers, torrent/usenet downloaders, image and music servers, etc. I have also seen them used to maintain cluster quorum after loss of one more powerful node. A two node cluster won't have quorum if one fails, so adding a pi as a third node makes sense.