Bug 637184
Summary: | libvirtd can't start | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ahmed Abdou <mail> |
Component: | libvirt | Assignee: | Daniel Veillard <veillard> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 14 | CC: | berrange, clalance, crobinso, itamar, jforbes, laine, veillard, virt-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-01-11 18:15:44 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ahmed Abdou
2010-09-24 14:41:59 UTC
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). Ahmed, 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 error. See: https://www.redhat.com/archives/libvir-list/2010-October/msg00997.html which was added to upstream libvirt in this commit: commit d68bb70a2d606b7206e78c360cbd4cf62b070493 Author: Daniel P. Berrange <berrange> 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. |