Bug 618498 - libvirtd fails to start
Summary: libvirtd fails to start
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Daniel Veillard
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-27 05:13 UTC by Conrad Meyer
Modified: 2011-02-04 16:47 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-02-04 16:47:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Conrad Meyer 2010-07-27 05:13:24 UTC
Description of problem:
the libvirtd service won't start (stock F-13 system).


Version-Release number of selected component (if applicable):
libvirt-0.7.7-5.fc13.x86_64


How reproducible:
always


Steps to Reproduce:
1. libvirtd as root
2.
3.
  
Actual results:
22:11:40.067: warning : qemudStartup:1150 : Unable to create cgroup for driver: No such device or address
22:11:40.301: warning : lxcStartup:1748 : Unable to create cgroup for driver: No such device or address
22:11:40.320: error : virStateInitialize:890 : Initialization of UML state driver failed
22:11:40.320: error : main:3160 : Driver state initialization failed
22:11:40.321: warning : qemudDispatchSignalEvent:385 : Shutting down on signal 3


Expected results:
(libvirtd starts)

Additional info:
selinux in enforcing mode, no AVC denials. i'll be gone for a week without access to this machine, but after that i should be able to answer any questions you may have. sorry about the timing.

also, got this line in /var/log/messages: Jul 26 21:48:25 localhost libvirtd: Could not find keytab file: /etc/libvirt/krb5.tab: No such file or directory

Comment 1 Luc de Louw 2010-09-28 08:09:27 UTC
Add the following to /etc/fstab and libvirtd works again:

cgroup /cgroup cgroup  cpuset,cpu,cpuacct,memory,devices,freezer,net_cls

Comment 2 Stefan Berger 2011-02-04 15:41:25 UTC
I had a similar problem. The reason on my machine was a corrupted qemu binary (some linklib was missing) that libvirt was trying to probe while starting. I believe I found it with 

export LIBVIRT_DEBUG=1

skipping over the iptables errors that libvirt tolerates to fail.

Comment 3 Conrad Meyer 2011-02-04 16:47:28 UTC
libvirtd has gone back to working for me since I filed this (without any action on my part other than installing updates). go figure.


Note You need to log in before you can comment on or make changes to this bug.