RE: gnome-boxes-3.16.2 - "Libvirt KVM guest available: no"
- From: John Frankish <john frankish outlook com>
- To: <gnome-boxes-list gnome org>
- Cc: 'Christophe Fergeau' <cfergeau redhat com>
- Subject: RE: gnome-boxes-3.16.2 - "Libvirt KVM guest available: no"
- Date: Thu, 31 Mar 2016 22:29:30 +0400
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)?
libvirt.so (which boxes uses) has some code to start libvirtd if needed.
OK, but in my case that doesn't happen, although I guess boxes would not be
able to start the daemon as root.
(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?
Starting libvirtd as root does not create a libvirt-sock-ro owned by $USER
$ sudo libvirtd -d
$ ls -l /var/run/libvirt
...
srwx------ 1 root root 0 Mar 31 21:55 libvirt-sock
srwxrwxrwx 1 root root 0 Mar 31 21:55 libvirt-sock-ro
...
If I change the libvirt-sock-ro owner to $USER and..
$ mkdir -p /home/tc/.local/libvirt/images
$ virsh pool-define-as gnome-boxes dir - - - -
/home/tc/.local/libvirt/images
Then...
$ G_MESSAGES_DEBUG=all gnome-boxes
(gnome-boxes:28050): Gtk-DEBUG: Connecting to session manager
(gnome-boxes:28050): Boxes-DEBUG: libvirt-system-importer.vala:45: Connected
to system libvirt, now fetching domains..
(gnome-boxes:28050): 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:28050): Boxes-DEBUG: libvirt-system-importer.vala:49: Fetched 0
domains from system libvirt.
(gnome-boxes:28050): Boxes-DEBUG: wizard-source.vala:285: No boxes to import
(gnome-boxes:28050): Libvirt.GObject-DEBUG: Close GVirConnection=0x2868500
(gnome-boxes:28050): Boxes-DEBUG: util-app.vala:268:
check_module_kvm_loaded: yes
(gnome-boxes:28050): Boxes-DEBUG: util-app.vala:248:
check_cpu_vt_capability: yes
** (gnome-boxes:28050): 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:28050): 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:28050): Boxes-DEBUG: vm-creator.vala:376: Creating volume
'boxes-unknown'..
(gnome-boxes:28050): Boxes-DEBUG: vm-creator.vala:378: Created volume
'boxes-unknown'..
(gnome-boxes:28050): Boxes-WARNING **: wizard.vala:463: Incapable host
system
(gnome-boxes:28050): 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:28050): 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:28050): Boxes-DEBUG: app.vala:432: Suspending running boxes
(gnome-boxes:28050): Boxes-DEBUG: app.vala:460: Running boxes suspended
I'm not sure why it claims " Incapable host system" as qemu will open the
iso directly without problems?
Regards
John
[
Date Prev][Date Next] [
Thread Prev][Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]