Bug 902887

Summary: [abrt] libvirt-daemon- virDomainDefFree: Process /usr/sbin/libvirtd was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Richard W.M. Jones <rjones>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: berrange, clalancette, crobinso, itamar, jforbes, jyang, laine, libvirt-maint, veillard, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b2d7c75f2958514dfed5733aeada1e930f39a238
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-28 17:42:23 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
File: backtrace
File: build_ids
File: cgroup
File: core_backtrace
File: dso_list
File: environ
File: limits
File: maps
File: open_fds
File: proc_pid_status
File: var_log_messages none

Description Richard W.M. Jones 2013-01-22 10:57:44 EST
Description of problem:
I didn't do anything.  libvirtd appeared to crash after I logged in.

Version-Release number of selected component:

Additional info:
backtrace_rating: 4
cmdline:        /usr/sbin/libvirtd --timeout=30
crash_function: virDomainDefFree
executable:     /usr/sbin/libvirtd
kernel:         3.6.9-4.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 virDomainDefFree at conf/domain_conf.c:1626
 #1 virDomainObjDispose at conf/domain_conf.c:1737
 #2 virObjectUnref at util/virobject.c:139
 #3 qemuDomainObjEndJob at qemu/qemu_domain.c:943
 #4 qemuDomainDestroyFlags at qemu/qemu_driver.c:1996
 #5 virDomainDestroyFlags at libvirt.c:2264
 #6 remoteDispatchDomainDestroyFlags at remote_dispatch.h:1329
 #7 remoteDispatchDomainDestroyFlagsHelper at remote_dispatch.h:1307
 #8 virNetServerProgramDispatchCall at rpc/virnetserverprogram.c:431
 #9 virNetServerProgramDispatch at rpc/virnetserverprogram.c:304
Comment 1 Richard W.M. Jones 2013-01-22 10:57:49 EST
Created attachment 685266 [details]
File: backtrace
Comment 2 Richard W.M. Jones 2013-01-22 10:57:51 EST
Created attachment 685267 [details]
File: build_ids
Comment 3 Richard W.M. Jones 2013-01-22 10:57:57 EST
Created attachment 685268 [details]
File: cgroup
Comment 4 Richard W.M. Jones 2013-01-22 10:57:59 EST
Created attachment 685269 [details]
File: core_backtrace
Comment 5 Richard W.M. Jones 2013-01-22 10:58:02 EST
Created attachment 685270 [details]
File: dso_list
Comment 6 Richard W.M. Jones 2013-01-22 10:58:09 EST
Created attachment 685271 [details]
File: environ
Comment 7 Richard W.M. Jones 2013-01-22 10:58:24 EST
Created attachment 685272 [details]
File: limits
Comment 8 Richard W.M. Jones 2013-01-22 10:58:35 EST
Created attachment 685273 [details]
File: maps
Comment 9 Richard W.M. Jones 2013-01-22 10:58:37 EST
Created attachment 685274 [details]
File: open_fds
Comment 10 Richard W.M. Jones 2013-01-22 10:58:40 EST
Created attachment 685275 [details]
File: proc_pid_status
Comment 11 Richard W.M. Jones 2013-01-22 10:58:45 EST
Created attachment 685276 [details]
File: var_log_messages
Comment 12 Richard W.M. Jones 2013-01-22 11:00:05 EST
Since ABRT just popped up immediately after I logged in,
and I wasn't using libvirt at all, I suspect this bug is
just something that ABRT pulled out of its guts at random
and decided to submit.
Comment 13 Cole Robinson 2013-01-28 17:42:23 EST
I'm just gonna assume this is related to the destroy() race since the backtrace is close.

*** This bug has been marked as a duplicate of bug 877110 ***