Re: [libvirt] Libvirt segfault in qemuMonitorSend() with multi-threaded API use

2010-03-05 Thread Adam Litke
Daniel, thanks for the help. I was able to fix the problem (see my post in a new thread). On Fri, 2010-03-05 at 09:32 +, Daniel P. Berrange wrote: > On Thu, Mar 04, 2010 at 02:22:35PM -0600, Adam Litke wrote: > > I have a multi-threaded Python program that shares a single libvirt > > connecti

Re: [libvirt] Libvirt segfault in qemuMonitorSend() with multi-threaded API use

2010-03-05 Thread Daniel P. Berrange
On Thu, Mar 04, 2010 at 02:22:35PM -0600, Adam Litke wrote: > I have a multi-threaded Python program that shares a single libvirt > connection object among several threads (one thread per active domain on > the system plus a management thread). On a heavily loaded host with 8 > running domains I a

[libvirt] Libvirt segfault in qemuMonitorSend() with multi-threaded API use

2010-03-04 Thread Adam Litke
I have a multi-threaded Python program that shares a single libvirt connection object among several threads (one thread per active domain on the system plus a management thread). On a heavily loaded host with 8 running domains I am getting a consistent libvirtd segfault in the qemu monitor handlin