Description of problem: Happened when I was using Boxes - don't know why. Version-Release number of selected component: libvirt-daemon-0.10.2.2-3.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/sbin/libvirtd --timeout=30 crash_function: __strlen_sse2_pminub executable: /usr/sbin/libvirtd kernel: 3.7.4-204.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 __strlen_sse2_pminub at ../sysdeps/x86_64/multiarch/strlen-sse2-pminub.S:38 #1 setfilecon_raw_internal at setfilecon.c:12 #2 virSecuritySELinuxSetFileconHelper at security/security_selinux.c:836 #3 virSecurityStackSetSavedStateLabel at security/security_stack.c:319 #4 qemuMigrationToFile at qemu/qemu_migration.c:3234 #5 qemuDomainSaveInternal at qemu/qemu_driver.c:2810 #6 qemuDomainManagedSave at qemu/qemu_driver.c:3019 #7 virDomainManagedSave at libvirt.c:17531 #8 remoteDispatchDomainManagedSave at remote_dispatch.h:3210 #9 remoteDispatchDomainManagedSaveHelper at remote_dispatch.h:3188
Created attachment 689100 [details] File: backtrace
Created attachment 689101 [details] File: cgroup
Created attachment 689102 [details] File: core_backtrace
Created attachment 689103 [details] File: dso_list
Created attachment 689104 [details] File: environ
Created attachment 689105 [details] File: limits
Created attachment 689106 [details] File: maps
Created attachment 689107 [details] File: open_fds
Created attachment 689108 [details] File: proc_pid_status
Created attachment 689109 [details] File: var_log_messages
Hmm, okay, this is the second report of this, so something must be going on. Looks like virSecurityStackSetSavedStateLabel is trying to label the save data with imagelabel=NULL. Maybe some cleanup race with daemon save-on-shutdown behavior?
Well no other reports have tricked in, so closing.