IIRC, virt-manager is not available as flatpak. GNOME Boxes flatpak is available, but it does not offer USB redirection.
1 Like
OK, I see now. I was referring to Flathub. Everyday learning something new 
Thank you !
Tried QEMU User Session with virt-manager flatpak as per the instruction but getting this error:
Unable to connect to libvirt qemu:///session.
binary '/app/sbin/virtqemud' does not exist in $PATH: No such file or directory
Libvirt URI is: qemu:///session
All required services and sockets are running OK.
Then tried creating normal QEMU session - all is OK, no errors.
P.S.: next tried creating QEMU User Session from root console - it worked. Apperantly, virt-manager flatpak lacks some permissions if launched not from root session…
Do you see the blue part under the VB list?
When you click on that you can connect a user session. Check this out please.
please click on details and copy past this here to see what errors we get.
@arturasb did you do that?
By the way … are you on a atomic-desktop?
I am a bit confused
So virt-manager flatpak did not work with the system session? This would be expected, this is the default of the app but it does not work rootless and not in the flatpak.
Manually deleting the system session and replacing with a user session would be nice upstream, or with a patchfile for the flatpak only.
@arturasb not answered yet. You made the proposal for a wiki, so it would be you who should make the tests fist.
I already did that, but here it goes:
Unable to connect to libvirt qemu:///session.
binary '/app/sbin/virtqemud' does not exist in $PATH: No such file or directory
Libvirt URI is: qemu:///session
1 Like
Did this part:
systemctl --now enable virtnetworkd.service
systemctl --now enable virtqemud.service
Yes and yes.
Fedora’s virt-manager flatpak worked if:
- I created QEMU/KVM system session
OR - I started
virt-managerin root session and created QEMU/KVM user session
Flatpak didn’t worked if started normally (not as root) with user session.
1 Like
I guess now it is clear
Aaah okay so it may well be that we need to start virt-manager with elevated privileges to remove the system session.
But isn’t it so, that running virt-manager with elevated privileges makes QEMU/KVM User session into System session effectively ?
No, virt-manager is the manager and viewer. Launching it with the polkit password allows some components to change protected other components, like the qemu session config.
User session qcow2 images are stored in a different place than system session ones for example.
Does it then mean that this is a bug or misconfiguration - running manager app with elevated privileges in order to get QEMU/KVM User Session?
OK, so I created QEMU/KVM User Session with virt-manager launched with root privileges. Location in connection settings points to /var/lib/libvirt/images. This indicated to me that virt-manager QEMU/KVM User Sessions created with elevated privileges effectively become System Sessions. And if I start virt-manager without root privileges previously created QEMU/KVM User Session is not visible in `virt-manager’.