Virt-Manager as Flatpack | errors

Did you start it with root privileges or did you start it normally, entered the sudo password, deleted the system session, created a user session, and then created a VM?

In the console:

sudo -i
root@host: flatpak run virt-manager  # I don't remember fully qualified virt-manager's flatpak name

virt-manager started with no connection - neither system nor user.
Next, in the virt-manger I created QEMU/KVM User Session connection. In its properties, the image location on the disk was this - /var/lib/libvirt/images and not a directory in user’s home.
So, I concluded that running virt-manager with elevated privileges+QEMU/KVM User Session connection in fact isvirt-manager started normally+QEMU/KVM System Session connection effectively.

I can only create QEMU/KVM User Session with image location in dir of my user’s home if my user is added to the libvirt group.

For me the expected behavior of running virt-manager as flatpak was this:

  1. I launch virt-manager flatpak app normally.
  2. I create QEMU/KVM User Session connection straight away without adding my user to libvirt group or running virt-manager with elevated privileges.
  3. I add a VM and everything is saved to my user’s home
    AND
  4. QEMU/KVM User Session has access to all libvirt services to run normally without needing root or user in the libvirt group.

This scenario doesn’t happen. Maybe my expectations are wrong ?

Both a Fedora flatpak of GNOME Boxes as well as getting the QEMU user session to work normally in virt-manager requires getting qemu and the libvirt daemons to build and install as flatpak builds. The necessary changes are extensive, but I do have a local proof of concept build of both apps that are working. It will take some work to clean up, submit, and get my patches merged, but it does seem doable now.

4 Likes