Bug 700963 - Cannot start libvirtd [NEEDINFO]
Cannot start libvirtd
Product: Fedora
Classification: Fedora
Component: libvirt (Show other bugs)
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Daniel Veillard
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2011-04-29 18:35 EDT by Javier Ramirez
Modified: 2011-05-02 14:43 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-05-02 14:43:28 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
laine: needinfo?

Attachments (Terms of Use)

  None (edit)
Description Javier Ramirez 2011-04-29 18:35:56 EDT
Description of problem:

libvirtd is not starting and is not showing any useful error message

Version-Release number of selected component (if applicable):

How reproducible:


Steps to Reproduce:
1. Try to start libvirtd running "service libvirtd start"
Actual results:
Error message:
[root@oldie systemd]# service libvirtd start
Starting libvirtd (via systemctl):  Job failed. See system logs and 'systemctl status' for details.
And the following error at /var/log/messages:
Apr 30 00:30:19 oldie systemd[1]: libvirtd.service: control process exited, code=exited status=1
Apr 30 00:30:19 oldie systemd[1]: Unit libvirtd.service entered failed state.

Expected results:
libvirtd to start

Additional info:
kvm modules are loaded:
[root@oldie systemd]# lsmod | grep kvm
kvm_intel              43336  0 
kvm                   306680  1 kvm_intel
Comment 1 Javier Ramirez 2011-05-01 03:51:23 EDT

I found that the problem was a buggy installation of fedora. If I try to run libvirtd manually I get the following error:

libvirtd: error while loading shared libraries: 
                /usr/lib64/libvirt-qemu.so.0: file too short

And that turns out that /usr/lib64/libvirt-qemu.so.0.8.8 was an empty file.

After reinstalling using yum, now I get other empty files so I would say the problem is not libvirt related.

Feel free to close the bugzilla.

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