<tt>libvir-list-bounces@redhat.com wrote on 11/23/2010 01:49:46 PM: > Hello, > I noticed that libvirtd sometimes crashes immediately after start.. > here's the backtrace: > > Core was generated by `libvirtd --daemon --listen'. > Program terminated with signal 11, Segmentation fault. > #0 0x00007fee038c0ca0 in pthread_mutex_lock () from /lib64/libpthread.so.0 > (gdb) bt > #0 0x00007fee038c0ca0 in pthread_mutex_lock () from /lib64/libpthread.so.0 > #1 0x000000000042eb21 in qemuDomainObjEnterMonitor (obj=0xe417d0) > at qemu/qemu_driver.c:478 > #2 0x0000000000448e7e in qemudDomainGetInfo (dom=<value optimized > out>, info=0x43392e10) at qemu/qemu_driver.c:5165 > #3 0x00007fee054f29f2 in virDomainGetInfo (domain=0xe3f610, > info=0x43392e10) at libvirt.c:3177 > #4 0x000000000042554e in remoteDispatchDomainGetInfo (server=<value > optimized out>, client=<value optimized out>, conn=0xdd8a20, > hdr=<value optimized out>, rerr=0x43392eb0, > args=<value optimized out>, ret=0x43392f90) at remote.c:1503 > #5 0x0000000000427444 in remoteDispatchClientCall (server=0xdb84d0, > client=0x7fedfc040bc0, msg=0x7fedfc0410a0) at dispatch.c:529 > #6 remoteDispatchClientRequest (server=0xdb84d0, > client=0x7fedfc040bc0, msg=0x7fedfc0410a0) at dispatch.c:407 > #7 0x00000000004194c7 in qemudWorker (data=<value optimized out>) > at libvirtd.c:1587 > #8 0x00007fee038be73d in start_thread () from /lib64/libpthread.so.0 > #9 0x00007fee03430f6d in clone () from /lib64/libc.so.6 > > Could somebody please look at it? > If I could provide any additional information, please let me know. > Thanks in advance > BR > nik > </tt> <tt>I also saw crashes recently, though those were resolved with a recent patch from ~3 hours ago.</tt> <a href="http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=149c49213799bc0fb1b99ccd3310a932b512bc07"><tt>http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=149c49213799bc0fb1b99ccd3310a932b512bc07</tt></a> <tt>Hope this one also resolves your crashes.</tt> <tt>Regards,</tt> <tt> Stefan</tt>