Hide Forgot
Description of problem: This happens regularly after shutting down an instance Version-Release number of selected component: libvirt-daemon-1.1.0-1.fc18 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/sbin/libvirtd crash_function: virObjectLock executable: /usr/sbin/libvirtd kernel: 3.10.14-100.fc18.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (9 frames) #0 virObjectLock at /lib64/libvirt.so.0 #1 virNetServerClientSendMessage at /lib64/libvirt.so.0 #2 remoteDispatchDomainEventSend #3 remoteRelayDomainEventLifecycle #4 virDomainEventStateDispatchFunc at /lib64/libvirt.so.0 #5 virDomainEventTimer at /lib64/libvirt.so.0 #6 virEventPollRunOnce at /lib64/libvirt.so.0 #7 virEventRunDefaultImpl at /lib64/libvirt.so.0 #8 virNetServerRun at /lib64/libvirt.so.0
Created attachment 834128 [details] File: backtrace
Created attachment 834129 [details] File: cgroup
Created attachment 834130 [details] File: core_backtrace
Created attachment 834131 [details] File: dso_list
Created attachment 834132 [details] File: environ
Created attachment 834133 [details] File: exploitable
Created attachment 834134 [details] File: limits
Created attachment 834135 [details] File: maps
Created attachment 834136 [details] File: open_fds
Created attachment 834137 [details] File: proc_pid_status
Created attachment 834138 [details] File: var_log_messages
Looks like you are using the last libvirt version from virt-preview before we discontinued it for F18 (we only target the lastest stable release). Please either downgrade to the libvirt version in the F18 repos, or update to F19/F20, and see if this issue reproduces.