Description of problem: Testing migration. Migration failed, destination libvirtd crashed soon after Version-Release number of selected component: libvirt-daemon-1.1.3.3-2.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 3 cmdline: /usr/sbin/libvirtd --listen crash_function: virClassIsDerivedFrom executable: /usr/sbin/libvirtd kernel: 3.12.8-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 virClassIsDerivedFrom at util/virobject.c:166 #1 virObjectIsClass at util/virobject.c:362 #2 virObjectUnlock at util/virobject.c:335 #3 qemuDomainMemoryStats at qemu/qemu_driver.c:9540 #4 virDomainMemoryStats at libvirt.c:8732 #5 remoteDispatchDomainMemoryStats at remote.c:1180 #6 remoteDispatchDomainMemoryStatsHelper at remote_dispatch.h:5196 #7 virNetServerProgramDispatchCall at rpc/virnetserverprogram.c:435 #8 virNetServerProgramDispatch at rpc/virnetserverprogram.c:305 #9 virNetServerProcessMsg at rpc/virnetserver.c:165
Created attachment 858132 [details] File: backtrace
Created attachment 858133 [details] File: cgroup
Created attachment 858134 [details] File: core_backtrace
Created attachment 858135 [details] File: dso_list
Created attachment 858136 [details] File: environ
Created attachment 858137 [details] File: limits
Created attachment 858138 [details] File: maps
Created attachment 858139 [details] File: open_fds
Created attachment 858140 [details] File: proc_pid_status
Created attachment 858141 [details] File: var_log_messages
I haven't seen this since, so closing