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



(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

I don't think this needs to be owned by user, just accessible by $USER.
But Boxes seems to be coping just fine with that.

No, unless I change the group for libvirt-sock-ro to something accessible to
the user, boxes says it cannot connect to the socket. Note that libvirt was
compiled with "--with-qemu-group=appropriate_group"

$ mkdir -p /home/tc/.local/libvirt/images
$ virsh pool-define-as gnome-boxes dir - - - -
/home/tc/.local/libvirt/images

Maybe you need to start the pool as well, virsh pool-start gnome-boxes

$ virsh pool-start gnome-boxes
Pool gnome-boxes started

$ G_MESSAGES_DEBUG=all gnome-boxes
...
(gnome-boxes:28203): Boxes-DEBUG: vm-creator.vala:376: Creating volume
'boxes-unknown'..
(gnome-boxes:28203): Boxes-DEBUG: vm-creator.vala:378: Created volume
'boxes-unknown'.
(gnome-boxes:28203): Boxes-WARNING **: wizard.vala:463: Incapable host
system

Perhaps the qemu I compiled is missing some functionality required by boxes?

What does boxes need in qemu:

Spice?
Pulseaudio?
Anything else?

Regards
John


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]