Hi Jeff, what I tried to outline before for virsh applies to virt-manager as well as they are all just libvirt frontends.
So the default of qemu:///system will be a system owned guest with all the implications (good and bad) that come with it. If you want to run "as user" it should be qemu:///session as shown above. The same works for virt-manager. You can go to "File -> Add connection" and enter "qemu:///session" as custom URL. With a guest started like that I have: - running qemu-system-x86_64 as my UID F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND 2 1000 11683 1 20 0 1856652 333760 poll_s Sl ? 3:51 qemu-sys... - my disk image still self-owned -rw------- 1 paelzer paelzer 16108814336 Aug 10 07:34 /home/paelzer/.local/share/libvirt/images/qemu-session-18.04.qcow2 As I mentioned before user session comes OTOH with other implications. The one I heard most about are issues with networking that needs different setup and some help to get working depending on the network setup. My default case - install from 18.04 ISO in virt-manager with qemu:///session that I just tried worked for me (including network to external sites). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784001 Title: Libvirt changes ownership (user/group) of my ISO images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1784001/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
