Displaying 3 results from an estimated 3 matches for "virdbusgetsessionbus".
2019 Apr 29
3
Re: libvirtd via unix socket using system uri
...path '/system', try
qemu:///session
But now I see virsh opening the socket, writing, etc.
The server log shows this:
2019-04-29 15:32:07.306+0000: 20863: info : libvirt version: 5.2.0
2019-04-29 15:32:07.306+0000: 20863: info : hostname: koji
2019-04-29 15:32:07.306+0000: 20863: error : virDBusGetSessionBus:169 :
internal error: Unable to get DBus session bus connection: Unable to
autolaunch a dbus-daemon without a $DISPLAY for X11
2019-04-29 15:32:24.534+0000: 20852: error : qemuConnectOpen:1127 :
internal error: unexpected QEMU URI path '/system', try qemu:///session
2019-04-29 15:32:24.534+...
2019 Apr 30
0
Re: libvirtd via unix socket using system uri
...sion
>
> But now I see virsh opening the socket, writing, etc.
>
> The server log shows this:
>
> 2019-04-29 15:32:07.306+0000: 20863: info : libvirt version: 5.2.0
> 2019-04-29 15:32:07.306+0000: 20863: info : hostname: koji
> 2019-04-29 15:32:07.306+0000: 20863: error : virDBusGetSessionBus:169 :
> internal error: Unable to get DBus session bus connection: Unable to
> autolaunch a dbus-daemon without a $DISPLAY for X11
> 2019-04-29 15:32:24.534+0000: 20852: error : qemuConnectOpen:1127 :
> internal error: unexpected QEMU URI path '/system', try qemu:///session
>...
2019 Apr 29
2
libvirtd via unix socket using system uri
I want to run libvirtd as a special user, and allowing users that belong
to a special group to connect via qemu+unix:///system (eg: unix socket).
I did everything necessary to do so: created a libvirt user and group,
added the libvirt user to the kvm group, added my normal user to the
libvirt group, and made sure the socket is owned by libvirt:libvirt with
permissions set to 770.
libvirtd starts