Red Hat Bugzilla – Bug 637184
libvirtd can't start
Last modified: 2011-01-11 13:15:44 EST
Description of problem:
I'm trying to use libvirt and it's not working so I tried
service libvirtd restart
and it said ok ok, but virt-manger said it's not running
Version-Release number of selected component (if applicable):
Try to restart libvirtd and check your log
Steps to Reproduce:
1. service libvirtd restart
Should be up and working
Sep 24 17:29:36 localhost libvirtd: 17:29:36.379: warning : qemudDispatchSignalEvent:396 : Shutting down on signal 15
Sep 24 17:29:38 localhost libvirtd: Could not find keytab file: /etc/libvirt/krb5.tab: No such file or directory
Sep 24 17:29:38 localhost libvirtd: 17:29:38.490: error : virRunWithHook:857 : internal error '/sbin/iptables --table mangle --delete POSTROUTING --out-interface virbr0 --protocol udp --destination-port 68 --jump CHECKSUM --checksum-fill' exited with non-zero status 2 and signal 0: iptables v1.4.9: unknown option `--checksum-fill'#012Try `iptables -h' or 'iptables --help' for more information.#012
Sep 24 17:29:38 localhost libvirtd: 17:29:38.716: error : virRunWithHook:857 : internal error '/sbin/iptables --table filter --delete INPUT --in-interface virbr0 --protocol udp --destination-port 69 --jump ACCEPT' exited with non-zero status 1 and signal 0: iptables: Bad rule (does a matching rule exist in that chain?).#012
Sep 24 17:29:38 localhost libvirtd: 17:29:38.833: error : virRunWithHook:857 : internal error '/sbin/iptables --table mangle --insert POSTROUTING --out-interface virbr0 --protocol udp --destination-port 68 --jump CHECKSUM --checksum-fill' exited with non-zero status 2 and signal 0: iptables v1.4.9: unknown option `--checksum-fill'#012Try `iptables -h' or 'iptables --help' for more information.#012
Sep 24 17:29:38 localhost libvirtd: 17:29:38.833: warning : networkAddIptablesRules:850 : Could not add rule to fixup DHCP response checksums on network 'default'.
Sep 24 17:29:38 localhost libvirtd: 17:29:38.833: warning : networkAddIptablesRules:851 : May need to update iptables package & kernel to support CHECKSUM rule.
Sep 24 17:29:42 localhost libvirtd: 17:29:42.602: warning : qemudStartup:1832 : Unable to create cgroup for driver: No such device or address
Sep 24 17:29:43 localhost kernel: lo: Disabled Privacy Extensions
Items 3 - 7 are red herrings - Those messages are informational only, and don't lead to shutting down of libvirtd. See Bug 642355.
Item 8 is also a red herring, although I don't have a reference for it.
(Actually I spoke to quickly - items 3 & 4 are not related to Bug 642355).
is the fact that virt-manager can't find libvirt your only indication that libvirtd is not running? Have you looked for libvirtd in the output of ps:
ps -AlF | grep libvirtd
None of the messages you included from your log indicate that libvirtd is going to shut down; even those that are valid errors would not lead to libvirtd terminating.
Since there is no indication of a legitimate shutdown, libvirtd would have to be crashing, and that should show up as an abrt alert (run "abrt-gui" as root to see if there are any crashes recorded).
Also, items 3 & 4 are possibly ancillary errors encountered during the
cleanup of a failure to start the network, and thus are obscuring the actual
which was added to upstream libvirt in this commit:
Author: Daniel P. Berrange <firstname.lastname@example.org>
Date: Tue Oct 26 11:17:25 2010 +0100
Avoid squashing errors during network startup cleanup path
When failing to start a virtual network, we have to cleanup,
tearing down any iptables rules. If the iptables rules were
not present yet though, this raises an error, which squashes
the original error we were handling.
* src/network/bridge_driver.c: When failing to start a virtual
network, don't squash the original error in cleanup
If possible, try the upcoming 0.8.5 release (or just grab the latest git sources and build/install yourself) and see if the error log changes.