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.
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.
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.
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.
Hmm, wouldn’t the virt manager just be a frontend and communicate with the virtd socket though?
Is there now a flatpak for virt-manager?
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
deleted by creator
