21
submitted 2 weeks ago* (last edited 2 weeks ago) by cm0002@piefed.world to c/linux@programming.dev
you are viewing a single comment's thread
view the rest of the comments
[-] GenderNeutralBro@lemmy.sdf.org 1 points 2 weeks ago

Gotcha. Yeah, that's been a pain point for me on previous distros. On Bazzite they make it easy with ujust setup-virtualization. I'm not sure if that's a one-size-fits-all solution but it suits my needs, at least.

[-] sgibson5150@lemmy.dbzer0.com 1 points 2 weeks ago* (last edited 2 days ago)

ujust setup-virtualization

I didn't realize that was a thing! Neat. Do you know what all that includes? On Aurora DX I only had to layer virt-top (virtio-win can be installed as a local package). My use case: I run a Windows VM that uses the discrete graphics card.

Edit: I did an rpm-ostree reset this week and found virtio-win was baked into the deployment. Long story but this started as a Bazzite machine, then I mistakenly rebased to the Silverblue source image that they used to make all the ublue OSes (which is a thing you can do, but obviously not supported or desired) before I eventually rebased again to Aurora DX. Learning is fun. At no point did the system fail to work, though. Kinda badass.

[-] GenderNeutralBro@lemmy.sdf.org 1 points 2 weeks ago

I think all it does is install the virt-manager Flatpak and then set a bunch of kernel arguments with rpm-ostree kargs ... depending on various hardware detections.

this post was submitted on 01 Oct 2025
21 points (100.0% liked)

Linux

9810 readers
788 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS