> strace isn't very helpful for debugging hangs - better to connect to
> libvirtd with GDB and get a stack trace of all threads, using
>
> (gdb) thread apply all bt
This is what i have with GDB
(gdb) thread apply all bt
Thread 1 (Thread 0x7f8b18e7c700 (LWP 4196)):
#0
On Thu, Apr 05, 2018 at 06:11:44PM +0300, Mathieu Tarral wrote:
> > You can enable debugging for virsh too:
> >
> > LIBVIRT_DEBUG=1 ./tools/virsh list --all
> >
> > Alternatively, you can run the libvirtd under strace to see if it
> > accepts() the connection request. Seems like virsh is trying to
> You can enable debugging for virsh too:
>
> LIBVIRT_DEBUG=1 ./tools/virsh list --all
>
> Alternatively, you can run the libvirtd under strace to see if it
> accepts() the connection request. Seems like virsh is trying to connect
> to a different socket than libvirtd is listening to.
I can see
On 04/05/2018 03:59 PM, Mathieu Tarral wrote:
> Hi,
>
> I managed to compile libvirt from the git repo,
> now i have some trouble to run it.
>
> This is what i did:
>
> I configured the source to use /var because i wanted the socket
> to be at the same place as the system one
>
Hi,
I managed to compile libvirt from the git repo,
now i have some trouble to run it.
This is what i did:
I configured the source to use /var because i wanted the socket
to be at the same place as the system one
(/var/run/libvirt/libvirt-sock)
./configure --prefix=$HOME/usr
