Your message dated Fri, 14 Aug 2015 09:06:06 +0200
with message-id <20150814070606.ga7...@bogon.m.sigxcpu.org>
and subject line Re: Bug#605964: [Pkg-libvirt-maintainers] Bug#605964: 
libvirt-bin: sometimes(randomly) crashes when connecting using python-libvirt
has caused the Debian Bug report #605964,
regarding libvirt-bin: sometimes(randomly) crashes when connecting using 
python-libvirt
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
605964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvirt-bin
Version: 0.8.3-5
Severity: normal

I cannot reliably reproduce this, but here is the python I was using to crash 
libvirt-bin (sometimes):

import libvirt
import sys


def main():
        #conn = libvirt.openReadOnly(None)
        conn = libvirt.openReadOnly("qemu:///system")
        print conn.isSecure()
        print conn.listDefinedDomains()


if __name__ == "__main__":
        main()

I was switching between a conn None and the conn connected to qemu:///system. 
The conn (established with None in the call) seems to be talking to virtualbox.

When it crashes I see something like this:
[46609.226658] libvirtd[2139]: segfault at 7fa018db5bdf ip 0000000000419293 sp 
00007fa013d8a270 error 7 in libvirtd[400000+dc000]
or this
[49173.212641] libvirtd[15647]: segfault at 7f9ac72acbdf ip 00007f9acb7bcb73 sp 
00007f9ac2a82270 error 7 in libvirtd[7f9acb79c000+e5000]
in dmesg output. 

In /var/log/messages, the following is present(before the crash - I cannot be 
sure on the exact ordering of events):

Dec  5 15:43:46 randombox libvirtd: 15:43:46.381: warning : lxcStartup:1900 : 
Unable to create cgroup for driver: No such device or address
Dec  5 15:43:47 randombox libvirtd: 15:43:47.944: warning : 
qemudDispatchSignalEvent:396 : Shutting down on signal 15
Dec  5 15:43:49 randombox libvirtd: 15:43:49.212: warning : qemudStartup:1832 : 
Unable to create cgroup for driver: No such device or address
Dec  5 15:43:49 randombox libvirtd: 15:43:49.645: warning : 
qemudParsePCIDeviceStrs:1422 : Unexpected exit status '1', qemu probably failed
Dec  5 15:43:49 randombox libvirtd: 15:43:49.921: warning : 
qemudParsePCIDeviceStrs:1422 : Unexpected exit status '1', qemu probably failed


-- System Information:
Debian Release: 5.0.7
  APT prefers stable
  APT policy: (900, 'stable'), (650, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.36.1 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



--- End Message ---
--- Begin Message ---
Hi,
On Sun, Dec 05, 2010 at 04:01:36PM +0100, Guido Günther wrote:
> tag 605964 +unreproducible
> thanks,

I'm closing this one since I still can't reproduce it and there werent
any other reports pointing into that direction since >4 years.
Cheers,
 -- Guido

--- End Message ---

Reply via email to