Re: [libvirt] Deadlock when using custom handlers

2011-08-16 Thread Daniel P. Berrange
On Tue, Aug 16, 2011 at 02:24:53PM +0200, Guido Günther wrote: > Hi Daniel, > On Sat, Aug 13, 2011 at 08:57:45PM -0700, Daniel P. Berrange wrote: > > On Fri, Aug 12, 2011 at 11:54:28PM +0200, Guido Günther wrote: > [..snip..] > > In the default libvirt event loop, the 'ff' callback is always invok

Re: [libvirt] Deadlock when using custom handlers

2011-08-16 Thread Guido Günther
Hi Daniel, On Sat, Aug 13, 2011 at 08:57:45PM -0700, Daniel P. Berrange wrote: > On Fri, Aug 12, 2011 at 11:54:28PM +0200, Guido Günther wrote: [..snip..] > In the default libvirt event loop, the 'ff' callback is always invoked > from a "clean" stack in the event loop, so you never have this probl

Re: [libvirt] Deadlock when using custom handlers

2011-08-13 Thread Daniel P. Berrange
On Fri, Aug 12, 2011 at 11:54:28PM +0200, Guido Günther wrote: > Hi, > virt-viewer is using it's own virEventRegisterImpl. With current libvirt > this can deadlock when connection to nonexistant URIs like > > qemu+ssh:///unknownhost.example.com/system > Gdb displays the deadlock nicely: > > #

[libvirt] Deadlock when using custom handlers

2011-08-12 Thread Guido Günther
Hi, virt-viewer is using it's own virEventRegisterImpl. With current libvirt this can deadlock when connection to nonexistant URIs like qemu+ssh:///unknownhost.example.com/system like: 23:47:00.338: 1526: debug : doRemoteOpen:503 : proceeding with name = qemu:///system 23:47:00.338: 1526: d