How does Bluefin-dx implement virt-manager, quemu and kvm?

Bluefin
1

In my previous post, I was relieved to hear there are no significant missing tools on Bazzite vs. normal bluefin, but now I‘m realising there‘s actually an aspect of bluefin-dx that would be very helpful for me.
I „need“ (need as in this is the newest cool thing I heard about that may make my life a bit easier :grin: ) a ideally highly performant Windows VM to use soundgridder. I heard Quemu/KVM is the best way to go about that.
I would really like to know how this is implemented in bluefin-dx, because I would like to use Bazzite instead. Is it simply layered or…?

All things Universal Blue and Atomic are very interesting, but I still don‘t entirely know how it all works :sweat_smile:

2

PS: I haven‘t looked into the virt-manager flatpak yet. Is that viable too?

1 Like
3

I was just about to comment that there is now a “full fledged” virt-manager+qemu extension as a flatpak.

I haven’t personally tested it yet but it should work fine. And no need to layer anything.

You can easily test it on Bazzite too

1 Like
4

Bazzite uses the virt-manager flatpak, but really you are free here. You could layer virt-manager yourselves, use GNOME Boxes or virt-manager through flatpak, call ujust setup-virtualization on bazzite. As long as libvirt and qemu are installed on the system, which is installed out-of-the-box with all uBlue DX images it seems.

You say you are on bluefin-dx, and to my knowledge virt-manager is already installed on that image. So just try opening something like “Virtual machine manager” from the gnome search.

5

Alright then! Fingers crossed it’ll work well, had some weird issues with the flatpak version of Gnome Boxes but that thing is generally pretty wack

6

call ujust setup-virtualization on bazzite

interestingly enough, that doesn’t seem to be available on Bluefin, probably because it’s a part of devmode. I’m on normal bluefin by the way!

I’ll try those two then. Thanks everybody!

7

That is only on Bazzite.

On bluefin-dx the virtualization stuff is already baked in, just launch virt-manager and off you go.

on non-dx images the flatpak is propably the best way to run VMs. no need to layer stuff in etc

8

It’s a 2 step process, then you should be good to go:

9

Thanks, but don’t worry, I know that! I’ve just always treated dx with respect for now… If I’m not fully able to handle Bluefin as is, how will I deal with her when she has sharper claws? Also I’d probably get a light bit of imposter syndrome lol

I’ll probably end up using dx in the long run, but for now I want to really try out all images, and I haven’t done that with Bazzite yet.
Say, is there any difference in performance/functionality between the Bazzite and Bluefin-dx implementations? Flatpak could technically be safer if you properly sandbox it, I suppose.

1 Like
10

They both do basically the same. Also, theres almost no difference between normal and DX images except for some added packages/flatpaks. Normal images are just meant for people who aren’t developers and want to save on ISO size and/or disk space…

In your case, since you want virtualisation and are interested in programming on uBlue, I’d reccommend just going with bluefin-dx, which just has everything out of the box that you need. If you REALLY want a bunch of gaming out of the box you could use Bazzite plus manually layering developer stuff. But then you don’t get the nice workflow and integration you’d get with Bluefin.

11

They both do basically the same.

All right then. Yeah, I’ll probably use bluefin (or Aurora if I find I like KDE more)-dx at the end of the day, but I still want to try Bazzite. Thanks again for all the helpful answers everybody!