Description of problem: libvirtd on source was killed when I was migrating a vm. The migration itself was successful. How reproducible: 50% Steps to Reproduce: 1. virsh migrate pgrunt-rhel6.5 qemu+ssh://<host>/system Additional info: 2015-02-16 17:57:39.863+0000: 10509: info : libvirt version: 1.2.12, package: 2.fc22 (Fedora Project, 2015-02-03-14:17:38, buildvm-08.phx2.fedoraproject.org) 2015-02-16 17:57:39.863+0000: 10509: warning : virDomainMigrateVersion3Full:3253 : Guest pgrunt-rhel6.5 probably left in 'paused' state on source Version-Release number of selected component: libvirt-daemon-1.2.12-2.fc22 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/sbin/libvirtd crash_function: virClassIsDerivedFrom executable: /usr/sbin/libvirtd kernel: 3.20.0-0.rc0.git5.1.fc23.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 virClassIsDerivedFrom at util/virobject.c:169 #1 virObjectIsClass at util/virobject.c:365 #2 virObjectUnlock at util/virobject.c:338 #3 virDomainObjListFindByUUIDInternal at conf/domain_conf.c:1073 #4 virDomainObjListFindByUUIDRef at conf/domain_conf.c:1093 #5 qemuDomObjFromDomain at qemu/qemu_driver.c:222 #6 qemuDomainGetJobInfo at qemu/qemu_driver.c:12259 #7 virDomainGetJobInfo at libvirt-domain.c:8659 #8 remoteDispatchDomainGetJobInfo at remote_dispatch.h:4309 #9 remoteDispatchDomainGetJobInfoHelper at remote_dispatch.h:4285 Potential duplicate: bug 1060461
Created attachment 992314 [details] File: backtrace
Created attachment 992315 [details] File: cgroup
Created attachment 992316 [details] File: core_backtrace
Created attachment 992317 [details] File: dso_list
Created attachment 992318 [details] File: environ
Created attachment 992319 [details] File: exploitable
Created attachment 992320 [details] File: limits
Created attachment 992321 [details] File: maps
Created attachment 992322 [details] File: open_fds
Created attachment 992323 [details] File: proc_pid_status
Created attachment 992324 [details] File: var_log_messages
Is this reproducible when you run the daemon on the source under valgrind? Seeing which function freed the object would be useful. Was the domain transient or persistent?
The domain was transient. I don't know what changed but I am unable to reproduce it. Sorry for the noise.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
There's only two hits of this particular crash in faf, and they both appear to be the reporter. Since it's no longer reproducible, closing