31
submitted 1 month ago by hellostick@lemm.ee to c/linux@lemmy.ml
all 17 comments
sorted by: hot top controversial new old
[-] liliumstar@lemmy.dbzer0.com 20 points 1 month ago

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.

[-] alteredEnvoy@sopuli.xyz 13 points 1 month ago

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

[-] deadcade@lemmy.deadca.de 7 points 1 month ago

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@lemmy.world 1 points 1 month ago

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

[-] hellostick@lemm.ee 1 points 1 month 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)

[-] hellostick@lemm.ee 2 points 1 month ago

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

[-] liliumstar@lemmy.dbzer0.com 2 points 1 month ago

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

[-] that_leaflet@lemmy.world 10 points 1 month 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.

[-] Neptr 8 points 1 month ago

Is there now a flatpak for virt-manager?

[-] thingsiplay@beehaw.org 2 points 1 month ago

I assume its this one: https://flathub.org/apps/org.virt_manager.virt-manager but its unverified and not directly from the actual developers.

[-] Neptr 2 points 1 month ago

Also seems to have way too many permissions. Maybe to work around some problem "flatpak"ing virt-manager?

[-] hellostick@lemm.ee 2 points 1 month ago

that is a good point... I obviously missed that. my generally would only use flatpak from the same developer of the app, or I will just use the deb packaged by my distro.

[-] user_naa@lemmy.world 8 points 1 month 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.

[-] boredsquirrel@slrpnk.net 1 points 1 month 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

[-] thingsiplay@beehaw.org 1 points 1 month ago

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

VMs don't have access to the host, so even if the virtual machine emulator Qemu and libvirt require root access, the encapsulated guest virtual machine have no access to the host. They can't harm your system.

[-] boredsquirrel@slrpnk.net 2 points 1 month ago

Yup VMs dont get access to the system. Unless there is a vulnerability.

For doing malware testing etc, qemu user sessions might be preferred.

You can just use RPM/DEB virt-manager and switch to the QEMU user session anyways. If you dont need some advanced stuff like GPU passthrough (I guess) (USB works) you can use that full time. I do.

this post was submitted on 18 Jan 2025
31 points (100.0% liked)

Linux

50417 readers
566 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