RE: gnome-boxes-3.16.2 - "Libvirt KVM guest available: no"

[John Frankish <john frankish outlook com>]

> > > 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 user
libvirtd.
> > >
> > 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)?

> The pool creation goes through libvirt as well, it might not have worked
> on your setup because of these libvirtd issuse...
> system libvirtd is usually started automatically at boot time
> (or maybe on demand through systemd socket activation).
This is not a system box, so I will need to start libvirtd

> > $ libvirtd -d -p /var/run/libvirt/libvirt-sock-ro
> You usually have 2 libvirtd instances running on a system,
> one running as root listening on /var/run/libvirt/libvirt-sock and on
> /var/run/libvirt/libvirt-sock-ro, and one running as a regular user
> and listening on $XDG_RUNTIME_DIR/libvirt/libvirt-sock
> You should not need to use -p, it should do the right thing
> (and libvirtd --help will tell you which sockets it's going to use).
$ libvirtd --help
    Configuration file (unless overridden by -f):
      $XDG_CONFIG_HOME/libvirt/libvirtd.conf
    Sockets:
      $XDG_RUNTIME_DIR/libvirt/libvirt-sock
    PID file:
      $XDG_RUNTIME_DIR/libvirt/libvirtd.pid

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
----------------------------------------------------

When started as root:
/var/run/libvirtd.pid
/var/run/libvirt/libvirt-sock-ro
/var/run/libvirt/libvirt-sock
/usr/local/etc/libvirt/qemu/networks/default.xml
..but it does not appear to have created a pool?

$ virsh -c qemu:///session list
 Id    Name                           State
----------------------------------------------------

..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: app.vala:396: Failed to query
'/home/tc/.cache/gnome-boxes/sources/QEMU Session': Error when getting
information for file '/home/tc/.cache/gnome-boxes/sources/QEMU Session': No
such file or directory. Assuming it doesn't exist.
(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
(gnome-boxes:28538): Boxes-DEBUG: tracker-iso-query.vala:21: Tracker SPARQL
query: SELECT nie:url(?iso)   nie:title(?iso)
       osinfo:id(?iso) osinfo:mediaId(?iso) osinfo:language(?iso)
{ ?iso nfo:isBootable true }
(gnome-boxes:28538): Boxes-DEBUG: util-app.vala:268:
check_module_kvm_loaded: yes
(gnome-boxes:28538): Boxes-DEBUG: util-app.vala:248:
check_cpu_vt_capability: yes
** (gnome-boxes:28538): WARNING **: Using a file
(/usr/local/share/gnome-boxes/gnome-boxes-logos-db.xml) as a database
location is deprecated, use a directory instead
(gnome-boxes:28538): Boxes-DEBUG: tracker-iso-query.vala:21: Tracker SPARQL
query: SELECT nie:url(?iso)   nie:title(?iso)
       osinfo:id(?iso) osinfo:mediaId(?iso) osinfo:language(?iso)
{ ?iso nfo:isBootable true }
(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
(gnome-boxes:28538): Boxes-DEBUG: tracker-iso-query.vala:21: Tracker SPARQL
query: SELECT nie:url(?iso)   nie:title(?iso)
       osinfo:id(?iso) osinfo:mediaId(?iso) osinfo:language(?iso)
{ ?iso nfo:isBootable true }
(gnome-boxes:28538): Boxes-DEBUG: tracker-iso-query.vala:21: Tracker SPARQL
query: SELECT nie:url(?iso)   nie:title(?iso)
       osinfo:id(?iso) osinfo:mediaId(?iso) osinfo:language(?iso)
{ ?iso nfo:isBootable true }
(gnome-boxes:28538): Boxes-DEBUG: tracker-iso-query.vala:21: Tracker SPARQL
query: SELECT nie:url(?iso)   nie:title(?iso)
       osinfo:id(?iso) osinfo:mediaId(?iso) osinfo:language(?iso)
{ ?iso nfo:isBootable true }
(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
(gnome-boxes:28538): Boxes-DEBUG: tracker-iso-query.vala:21: Tracker SPARQL
query: SELECT nie:url(?iso)   nie:title(?iso)
       osinfo:id(?iso) osinfo:mediaId(?iso) osinfo:language(?iso)
{ ?iso nfo:isBootable true }
(gnome-boxes:28538): Boxes-DEBUG: tracker-iso-query.vala:21: Tracker SPARQL
query: SELECT nie:url(?iso)   nie:title(?iso)
       osinfo:id(?iso) osinfo:mediaId(?iso) osinfo:language(?iso)
{ ?iso nfo:isBootable true }
(gnome-boxes:28538): Boxes-DEBUG: app.vala:432: Suspending running boxes
(gnome-boxes:28538): Boxes-DEBUG: app.vala:460: Running boxes suspended