this post was submitted on 17 Apr 2024
168 points (96.7% liked)

Linux

48381 readers
1002 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r
168
VirtualBox 7.0.16 Released with Initial Support for Linux 6.8 and 6.9 Kernels (9to5linux.com)
submitted 7 months ago by petsoi@discuss.tchncs.de to c/linux@lemmy.ml
64 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] SpaceCadet@feddit.nl 11 points 7 months ago (2 children)

That's not GPU passthrough. That just enables VirGL, which is a translation layer that passes some OpenGL calls through to the host's Mesa installation. It has rather poor performance though, it's extremely limited and is rather buggy too. You certainly can't use it for cutting edge gaming.

GPU passthrough is when you pass through an entire GPU device as-is to the virtual machine. That is: if you have an Nvidia RTX 3060, the guest operating system will see an Nvidia RTX 3060 and it can use the native drivers for it. This gives you near-native performance for gaming.

Now, I didn't even know this was possible with VirtualBox (if so: cool!), but it's certainly doable with KVM if you have the right motherboard and GPU combination. I have done it, but it is quite the hassle indeed though that isn't really KVM's fault.

[–] penquin@lemm.ee 4 points 7 months ago (1 children)

That's why it failed for me, I don't have an Nvidia GPU. I wanted to pass my GPU to my windows install but it never worked and I blamed kvm 🤦🏽‍♂️ I knew about the first part that the "3rd acceleration" isn't a full GPU passthrough, but didn't know the latter was Nvidia only.

[–] SpaceCadet@feddit.nl 4 points 7 months ago* (last edited 7 months ago) (1 children)

It does work with AMD GPUs too, I did it with an RX6800XT myself, but there are some (most...) AMD GPUs that have a reset bug which means they hang if you reboot the guest and you need to powercycle the physical host machine to make the GPU usable for the guest again.

[–] penquin@lemm.ee 2 points 7 months ago (1 children)

Well that sucks. I have a 580xt GPU. It's about 7 years old, but still powers. Do you have a link on how to get it working? Pretty please?

[–] SpaceCadet@feddit.nl 4 points 7 months ago (1 children)

To get basic GPU passthrough working, I mainly followed the Arch Linux guide: https://wiki.archlinux.org/title/PCI_passthrough_via_OVMF

Be warned though that this is just the start of the journey. There are all kinds of issues that you need to deal with and decisions that you need to make if you want to practically use it for gaming, and those require lots of googling, piecing bits of information together from all over the place, and trial and error. From memory these are things I had to deal with:

  • How to handle storage? Just a qcow2 file or pass through a partition or drive?
  • How to handle mouse and keyboard input? Emulated or through a passed through USB port? Both have their pros and cons.
  • Audio is a pain in the ass... emulated it either crackly or laggy. There is a way to pass it through to pipewire through a unix socket, but it's convoluted to setup. Or perhaps you can pass an entire audio device through to your guest?
  • Bluetooth audio, for my wireless headset, was an even bigger issue because audio did not get routed correctly to the headset if I just connected to the host. In the end, I got a separate bluetooth dongle for my VM, and passed it through.
  • How do you handle the display between guest and host? Two separate monitors? A monitor with dual inputs, and toggle between them? Or something like looking-glass, which sounds appealing but again introduces issues like vrr not working properly, and your GPU will probably need a dummy "dongle" to work without an actual monitor connected.
  • Then there's the CPU and how to divide the cores between guest and host: for best performance, the guest's cores need to be reserved, and should take into account the CPU topology. For example, I have a 5900x and reserved the 6 cores on one CCX for my VM , leaving the other 6 for my host.

For more information, there's the /r/VFIO subreddit. Yeah I know, f*** reddit, but it has a lot of useful information. The looking glass site has some FAQs too, even on things not directly related to looking-glass itself. There is some VFIO discussion on the level one forums as well, but they're not so active.

Anyway if all this sounds like a cool project to spend a few weeks on, I heartily recommend you try it. I sure enjoyed setting this all up and getting it working, but I spent way more time configuring and troubleshooting things than I did gaming with that setup, and in the end I decided that just gaming on Proton and occasionally dual booting for problematic games is a much more practical solution.

[–] penquin@lemm.ee 1 points 7 months ago

Thank you so much for this, I really appreciate it. Saving this comment.

[–] possiblylinux127@lemmy.zip 2 points 7 months ago

I do what your describing (its called vfio) and it works pretty well on Proxmox.