Comment 6 for bug 1531833

Revision history for this message
Misi (ne-ebresz-fel) wrote :

sudo systemctl status libvirt-bin.service -l:

libvirt-bin.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirt-bin.service; enabled; vendor preset: enabled)
   Active: failed (Result: start-limit) since Mon 2016-01-11 21:13:10 CET; 5min ago
     Docs: man:libvirtd(8)
           http://libvirt.org
  Process: 877 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, status=1/FAILURE)
 Main PID: 877 (code=exited, status=1/FAILURE)

Jan 11 21:13:09 localhost systemd[1]: libvirt-bin.service: Unit entered failed state.
Jan 11 21:13:09 localhost systemd[1]: libvirt-bin.service: Failed with result 'exit-code'.
Jan 11 21:13:10 localhost systemd[1]: libvirt-bin.service: Service hold-off time over, scheduling restart.
Jan 11 21:13:10 localhost systemd[1]: Stopped Virtualization daemon.
Jan 11 21:13:10 localhost systemd[1]: libvirt-bin.service: Start request repeated too quickly.
Jan 11 21:13:10 localhost systemd[1]: Failed to start Virtualization daemon.
Jan 11 21:13:10 localhost systemd[1]: libvirt-bin.service: Unit entered failed state.
Jan 11 21:13:10 localhost systemd[1]: libvirt-bin.service: Failed with result 'start-limit'.

sudo journalctl -xe:
In attachment