[Pkg-libvirt-maintainers] Bug#565983: Bug#565983: libvirt-bin: libvirtd crashes when accessed through virt-manager

[Guido Günther]

Hi,
On Fri, Jan 22, 2010 at 03:03:47PM +0100, Luca Tettamanti wrote:
> On Fri, Jan 22, 2010 at 1:21 PM, Guido Günther <agx at sigxcpu.org> wrote:
> >
> > ----- Ursprüngliche Mitteilung -----
> >> On Thu, Jan 21, 2010 at 11:49:47PM +0100, Laurent Léonard wrote:
> >> > Le jeudi 21 janvier 2010 à 23:16, Luca Tettamanti a écrit :
> >> > > I encountered the same problem on my machine. The bug appeared after a
> >> > > recent upgrade, I've downgraded to 0.7.5-4 and I can connect with
> >> > > virt-manager again.
> >> >
> >> > I noticed libvirt only crashed at the first connection with Virt-manager. If I
> >> > start libvirt again and try to reconnect it works. I can confirm all Debian
> >> > revisions of libvirt 0.7.5 are affected by that bug.
> >> >
> >> > See the upstream bug report https://bugzilla.redhat.com/show_bug.cgi?id=556815
> >> > for more informations.
> >>
> >> The stack trace matches what I'm seeing on my machine, however 0.7.5-4 works
> >> fine here. I only connect via ssh though.
> > The trace lacks the glibc part (libc6-dbg).
> 
> #2  0x000000000041d1ff in remoteDispatchNodeDeviceLookupByName
> (server=<value optimized out>, client=<value optimized out>,
>     conn=0x14ea030, hdr=<value optimized out>, rerr=0x7f8115bb7e30,
> args=<value optimized out>, ret=0x7f8115bb7e80)
>     at remote.c:5401
This seems to be in the device enumeration code. However
virNodeDeviceLookupByName has debugging output. Could you run libvirtd
as:

LIBVIRT_DEBUG=1 /usr/sbin/libvirtd

This should give us a clue what's going on. Also the output of
"virt-manager --debug" will help.
Cheers,
 -- Guido