Version-Release number of selected component: libvirt-daemon-0.10.2.4-1.fc18 Additional info: reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/sbin/libvirtd crash_function: vasprintf executable: /usr/sbin/libvirtd kernel: 3.9.4-200.fc18.x86_64 runlevel: N 5 uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #2 vasprintf at /usr/include/bits/stdio2.h:210 #3 virVasprintf at util/util.c:1984 #4 virLogVMessage at util/logging.c:723 #5 virLogMessage at util/logging.c:670 #6 udev_log at src/libudev/libudev.c:64 #7 udev_device_new_from_syspath at src/libudev/libudev-device.c:726 #8 udevProcessDeviceListEntry at node_device/node_device_udev.c:1353 #9 udevEnumerateDevices at node_device/node_device_udev.c:1386 #10 udevDeviceMonitorStartup at node_device/node_device_udev.c:1704 #11 virStateInitialize at libvirt.c:804
Created attachment 755017 [details] File: backtrace
Created attachment 755018 [details] File: cgroup
Created attachment 755019 [details] File: core_backtrace
Created attachment 755020 [details] File: dso_list
Created attachment 755021 [details] File: environ
Created attachment 755022 [details] File: limits
Created attachment 755023 [details] File: maps
Created attachment 755024 [details] File: open_fds
Created attachment 755025 [details] File: proc_pid_status
Created attachment 755026 [details] File: var_log_messages
Apparently I had udev_log="debug" in /etc/udev/udev.conf. I set the log to info and libvirtd service starts up normally. I found the solution here: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/968930 It shouldn't crash just because udev is logging debug messages.
Upstream patch proposed: https://www.redhat.com/archives/libvir-list/2013-June/msg00349.html
Now fixed upstream: commit f753dd62f951cc62e164421d0c6491f39e4c68ad Author: Ján Tomko <jtomko> AuthorDate: 2013-06-07 11:55:27 +0200 Commit: Ján Tomko <jtomko> CommitDate: 2013-06-14 13:17:27 +0200 udev: fix crash in libudev logging Call virLogVMessage instead of virLogMessage, since libudev called us with a va_list object, not a list of arguments. Honor message priority and strip the trailing newline. https://bugzilla.redhat.com/show_bug.cgi?id=969152 git describe: v1.0.6-76-gf753dd6
libvirt-0.10.2.7-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/libvirt-0.10.2.7-1.fc18
Package libvirt-0.10.2.7-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libvirt-0.10.2.7-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-14066/libvirt-0.10.2.7-1.fc18 then log in and leave karma (feedback).
libvirt-0.10.2.7-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.