On Thu, Mar 31, 2016 at 05:07:38PM +0400, John Frankish wrote:
Is libvirtd running as root? You could also try running 'virsh -c qemu:///session list --all' as a regular user before starting Boxes as there are known issue with some libvirt versions with automatic startup of the userlibvirtd.libvirtd isn't running at all - shouldn't gnome-boxes start it (and create a gnome-boxes pool) via dbus?user (session) libvirtd is going to be started automatically when needed, which is what seems to not work on your setup.How is it going to be started (by what)?
libvirt.so (which boxes uses) has some code to start libvirtd if needed.
When started as user: /home/tc/.cache/libvirt/libvirt-sock /home/tc/.cache/libvirt/libvirtd.pid /home/tc/.cache/libvirt/libvirtd.log $ virsh -c qemu:///session list Id Name State ----------------------------------------------------
Ok, virsh seems to be working fine then (assuming you don't have preexisting VMs which should be listed there).
..and $ G_MESSAGES_DEBUG=all gnome-boxes (gnome-boxes:28538): Gtk-DEBUG: Connecting to session manager (gnome-boxes:28538): Boxes-DEBUG: libvirt-system-importer.vala:45: Connected to system libvirt, now fetching domains.. (gnome-boxes:28538): Boxes-DEBUG: libvirt-system-importer.vala:49: Fetched 0 domains from system libvirt. (gnome-boxes:28538): Boxes-DEBUG: wizard-source.vala:285: No boxes to import (gnome-boxes:28538): Libvirt.GObject-DEBUG: Close GVirConnection=0x132a100
It successfully connected to your system libvirtd instance.
(gnome-boxes:28538): Libvirt.GLib-DEBUG: Error: internal error: client socket is closed (gnome-boxes:28538): Boxes-WARNING **: wizard.vala:463: Unable to get storage pool info: internal error: client socket is closed
And here something goes wrong, not sure why though... I assume "virsh -c qemu:///session pool-list" is working fine? Or maybe it's just a red herring and trying to create a VM would work? Christophe
Attachment:
signature.asc
Description: PGP signature