Description of problem:
libvirt-guests fails to restart guests at boot time. The journal shows it failing to connect to libvirtd.
Version-Release number of selected component (if applicable):
(installed from testing, fixes libvirt crash on system shutdown a.k.a. bug 903184)
How reproducible: always
Steps to Reproduce:
1. systemctl enable libvirt-guests
2. start a guest system
After the reboot, the guest system is shown as "saved" in virt-manager.
After the reboot, the guest system should be running.
- On a running system, you can stop, and then start libvirt-guests, and it has the expected result. I.e. the guest is saved, and then resumed.
- Log messages:
libvirt-guests.service - Suspend Active Libvirt Guests
Loaded: loaded (/usr/lib/systemd/system/libvirt-guests.service; enabled)
Active: active (exited) since Wed 2013-01-30 15:17:11 GMT; 18min ago
Process: 1279 ExecStart=/etc/init.d/libvirt-guests start (code=exited, status=0/SUCCESS)
Jan 30 15:17:11 fossil.scree.dyndns.org systemd: Starting Suspend Active Libvirt Guests...
Jan 30 15:17:11 fossil.scree.dyndns.org libvirt-guests: Can't connect to default. Skipping.
Jan 30 15:17:11 fossil.scree.dyndns.org systemd: Started Suspend Active Libvirt Guests.
I noticed guests didn't start at boot-time on F17 either. I didn't look for the error message at the time, but I can reproduce the exact same error message in an F17 VM. (It looks like you can't nest KVM, so the inner VM was run under QEMU).
I rebooted a few times and managed to reproduce this once. Might be a race with libvirtd starting up, if libvirt-guests tries to connect to early, the check fails and no guests are started.
It seems that libvirt-guests.service has no dependency on libvirtd.service. It should probably have After=libvirtd.service.
Might be related to bug 1031696
I've sent a patch upstream with the suggestion in Comment #3
Author: Cole Robinson <email@example.com>
Date: Tue Nov 19 15:19:25 2013 -0500
libvirt-guests: Run only after libvirtd
And pushed to F19 and F20 maint
libvirt-220.127.116.11-1.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libvirt-18.104.22.168-1.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
libvirt-22.214.171.124-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.