---------- Forwarded message ----------
From: Stefano Ricci <sfn....@gmail.com>
Date: 2016-10-11 12:35 GMT+02:00
Subject: Re: [libvirt-users] Problems connecting to the libvirtd server
To: Michal Privoznik <mpriv...@redhat.com>

There is not AppArmor and SElinux is disabled.
The permits of the sock are as follows:
libvirt-sock-admin 0700 (rwx) root: root
libvirt-sock 0700 (rwx) root: root
libvirt-sock-ro 0777 (rwxrwxrwx) root: root
The libvirtd process runs with the root user.

Below you will find the link to the requested log:
http://pastebin.com/0jtpWU0h (libvirt_client.log command LIBVIRT_DEBUG
= 1 virsh -c qemu: /// system list --all)


2016-10-11 11:04 GMT+02:00 Michal Privoznik <mpriv...@redhat.com>:
> On 10.10.2016 18:36, Stefano Ricci wrote:
> > Hello everyone
> > I do not know if it is correct address this mailing lists but I can
> > not use libvirt.
> > I run compile libvirt version 2.2.0 into environment lfs stable with
> > qemu 2.7.0 and have not had any problems.
> > The program when it starts not report any errors in the log, with
> > activated debug level file.
> > Only when you try to connect with the following command virsh -c
> > qemu:///system remains hung without reporting any error either in the
> > logs that screen.
> > The command virsh -c test:///default list instead concludes on a regular 
> > basis.
> > I attach the file libvirt.log and libvirt.conf
> Interesting. Maybe something else is causing the problem? Is there an
> AppArmor running? What are the socket perms? Can you attach client debug
> logs? (well, maybe paste them somewhere to pastebin-like service)
> http://wiki.libvirt.org/page/DebugLogs
> Michal

libvirt-users mailing list

Reply via email to