Libvirt locks on `getResponse()` about go-libvirt HOT 11 CLOSED

#98 fix this

from go-libvirt.

When this happens, is libvirt still responsive to virsh commands? Virsh uses the same rpc interface to talk to libvirt that go-libvirt uses, so if virsh also becomes unresponsive it would point to a problem in libvirt itself.

from go-libvirt.

Yes, it still responsive. I can call any virsh commands and they work correctly.

from go-libvirt.

when it fails again , can you try to dump all goroutines stack and share it with this issue?
Also can you try to compile you code (that sometimes fails like you say) with race detector?

from go-libvirt.

Yes, I compile my code with race detector and don't get any panics when it stuck, so it's not a race condition in my code (I hope 😄).
Attach archive with:

• trace
• cpu profile
• mutex profile
• goroutine profile

2020-01-14-02-17-35.zip

from go-libvirt.

i mean something different:
when you app if stuck and locks send to it SIGABRT so it prints to stderr all goroutine stack present on moment when you sent signal

from go-libvirt.

Ok, I will try to reproduce and dump goroutines.

from go-libvirt.

Goroutines dump in attached file.
goroutines.txt

from go-libvirt.

thanks, how much vm i can ran to may be reproduce this issue? 50 is enough?

from go-libvirt.

We reproduce this bug with 5 VMs. The main thing that all operations should perform in parallel.

from go-libvirt.

Looks like we found why we got a random hang on libvirt connection. We use the same connection for sending commands and for receiving events. And we got an idea that this is a key to the problem. So now we use two different connections. One is read-only for events and second for the commands and everything looks good.

from go-libvirt.