this post was submitted on 18 Jan 2025
32 points (92.1% liked)

Linux

49107 readers
1492 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
all 13 comments
sorted by: hot top controversial new old
[–] BananaTrifleViolin 1 points 1 day ago

Depends on what distro you're on? You say the deb version is 4.0 and flatpak is 5.0, suggesting you may be on a long release distro?

I'd favour the Deb version as it's official for your distro. The flatpak version is unverified; it's extremely unlikely Virt-Manager is compromised or will cause any issues but virtual machines do have security risks.

Also problem solving issues with the flatpak version may be more difficult as you have a whole layer potential issues in the sandbox on top of all the other issues people can have around KVM/QEMU. But you could install it, if it works great, if not, revert to the Deb version.

[–] [email protected] 20 points 3 days ago (3 children)

I would use the native version. For something like this, it makes sense that it should have less restricted/sandboxed access to the underlying system.

[–] [email protected] 2 points 2 days ago (1 children)

i am not sure which one is the native version... you mean the version packaged by the distro (deb) or the developer (flatpak)?

[–] [email protected] 2 points 2 days ago

In this case I meant the one packaged by your distro.

[–] [email protected] 14 points 3 days ago

Hmm, wouldn't the virt manager just be a frontend and communicate with the virtd socket though?

[–] [email protected] 7 points 3 days ago (2 children)

virt-manager only requires access to the libvirtd socket, as long as the flatpak.has that as default configuration (which I imagine would be the case), there's zero difference beteween flatpak and native.

[–] deafboy 1 points 2 days ago

In my experience, this is not the case. It just says it can't connect. Doesn't specify how or where to.

[–] [email protected] 1 points 2 days ago

actually there is difference in version between the two. deb by my distro is in 4.0.0 (mar, 2022) while flatpak is 5.0.0 (nov, 2024)

[–] that_leaflet 10 points 3 days ago

The virt-manager flatpak doesn’t work out of the box, you need to do some setup on the host. At that point you may as well use the deb of virt-manager.

[–] user_naa 8 points 3 days ago

If you install virt-manager on Debian via apt it will have full system acres and also automatically install and configure libvirt, so this method is preferred.

[–] [email protected] 7 points 3 days ago

Is there now a flatpak for virt-manager?

[–] [email protected] 1 points 3 days ago

I recommend using a QEMU guest session with libvirt. This works in both versions.

The standard session requires root, and for some reason this means that VMs couls harm your system more or something

Guest sessions are usable within Flatpaks, GNOME boxes has a Flatpak too. Is the virt-manager flatpak from Flathub? Fedora had one before.

Pretty cool, on debian you may want to use that to get newer versions. Even though virt-manager is pretty slow in updates