-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation Request for non-Windows Configurations #47
Comments
There must be something else, because following this guide i stucked with HaOS/Frigate. How can I install drivers, when the Proxmox developer said drivers are already installed? |
Hi @carmanj , if you go LXC route¹ you probably don't need to follow this tutorial, you will actually want proxmox host handling your GPU, using the proxmox builtin AMD GPU drivers. And that means you don´t want to passthrough your GPU, because if you do then proxmox won't be able to access it so it can share with LXC. I recommend checking both those links if you wanna go on the route for Jellyfin on LXC:
¹: Of course, I'm assuming you mean LXC running over proxmox host directly. Now, if you are going the VM/docker route, yes, you will need GPU passthrough to the guest VMs. About drivers, it's basically the same worry you will have on proxmox host, almost none, since drivers already included in the OS installation will probably just work. Now about the AMD Reset Bug.. I'm afraid there's no solution similar to the RadeonResetBugFix service that's available for Linux based guest OS... So that might be a problem. |
Could we get some extended documentation about configuring GPU Passthrough to non-Windows VMs, Docker, or LXC in the README? Or are there no real additional steps that need to be taken? For whatever it is worth, I've got a Beelink GTR-7 (R7 7840HS/Radeon 780M). Ideally looking at doing GPU passthrough for Scripted and JellyFin/Plex.
Thanks!
The text was updated successfully, but these errors were encountered: