Bug 1060523

Summary: Libvirtd does not start correctly.
Product: [Fedora] Fedora Reporter: Frederic Hornain <fhornain>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 20CC: berrange, clalancette, itamar, jforbes, jyang, laine, libvirt-maint, veillard, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-02 11:13:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Frederic Hornain 2014-02-02 10:48:33 UTC 
Description of problem:
systemctl status libvirtd
libvirtd.service - Virtualization daemon
   Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled)
   Active: failed (Result: start-limit) since Sun 2014-02-02 11:37:40 CET; 2min 53s ago
  Process: 1110 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, status=1/FAILURE)
 Main PID: 1110 (code=exited, status=1/FAILURE)
   CGroup: /system.slice/libvirtd.service

Feb 02 11:37:40 localhost.localdomain systemd[1]: Starting Virtualization daemon...
Feb 02 11:37:40 localhost.localdomain systemd[1]: Started Virtualization daemon.
Feb 02 11:37:40 localhost.localdomain systemd[1]: libvirtd.service: main process exited, code=exited, status=1/FAILURE
Feb 02 11:37:40 localhost.localdomain systemd[1]: Unit libvirtd.service entered failed state.
Feb 02 11:37:40 localhost.localdomain systemd[1]: libvirtd.service holdoff time over, scheduling restart.
Feb 02 11:37:40 localhost.localdomain systemd[1]: Stopping Virtualization daemon...
Feb 02 11:37:40 localhost.localdomain systemd[1]: Starting Virtualization daemon...
Feb 02 11:37:40 localhost.localdomain systemd[1]: libvirtd.service start request repeated too quickly, refusing to start.
Feb 02 11:37:40 localhost.localdomain systemd[1]: Failed to start Virtualization daemon.
Feb 02 11:37:40 localhost.localdomain systemd[1]: Unit libvirtd.service entered failed state.

Version-Release number of selected component (if applicable):
[root@localhost log]# rpm -qa | grep libvirt
libvirt-daemon-driver-storage-1.1.3.3-2.fc20.x86_64
libvirt-daemon-driver-lxc-1.1.3.3-2.fc20.x86_64
libvirt-client-1.1.3.2-1.fc20.x86_64
libvirt-glib-0.1.7-2.fc20.x86_64
libvirt-daemon-driver-qemu-1.1.3.3-2.fc20.x86_64
libvirt-daemon-kvm-1.1.3.3-2.fc20.x86_64
libvirt-daemon-driver-network-1.1.3.3-2.fc20.x86_64
libvirt-daemon-driver-nodedev-1.1.3.3-2.fc20.x86_64
libvirt-daemon-driver-xen-1.1.3.3-2.fc20.x86_64
libvirt-1.1.3.3-2.fc20.x86_64
libvirt-daemon-1.1.3.2-1.fc20.x86_64
libvirt-daemon-driver-nwfilter-1.1.3.3-2.fc20.x86_64
libvirt-daemon-config-network-1.1.3.3-2.fc20.x86_64
libvirt-python-1.1.3.3-2.fc20.x86_64
libvirt-daemon-driver-interface-1.1.3.3-2.fc20.x86_64
libvirt-daemon-driver-libxl-1.1.3.3-2.fc20.x86_64
libvirt-gobject-0.1.7-2.fc20.x86_64
libvirt-daemon-driver-vbox-1.1.3.3-2.fc20.x86_64
libvirt-client-1.1.3.3-2.fc20.x86_64
libvirt-daemon-driver-secret-1.1.3.3-2.fc20.x86_64
libvirt-gconfig-0.1.7-2.fc20.x86_64
libvirt-daemon-config-nwfilter-1.1.3.3-2.fc20.x86_64
libvirt-daemon-driver-uml-1.1.3.3-2.fc20.x86_64

How reproducible:
Well, I do not know how I can reproduce it.
It works before I did a system update. 

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
The libvirt daemon should start.

Additional info:
Comment 1 Frederic Hornain 2014-02-02 10:53:44 UTC 
[root@localhost etc]# libvirtd -d
libvirtd: /lib64/libvirt.so.0: version `LIBVIRT_PRIVATE_1.1.3.2' not found (required by libvirtd)
Comment 2 Frederic Hornain 2014-02-02 11:13:11 UTC 
OK, this problem is linked to an update issue.