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.
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)
In my experience, this is not the case. It just says it can’t connect. Doesn’t specify how or where to.
Hmm, wouldn’t the virt manager just be a frontend and communicate with the virtd socket though?
i am not sure which one is the native version… you mean the version packaged by the distro (deb) or the developer (flatpak)?
In this case I meant the one packaged by your distro.
