Bug 906009 - libvirt-guests fails to restart guests at boot time
Summary: libvirt-guests fails to restart guests at boot time
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: 20
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2013-01-30 15:46 UTC by Alan Jenkins
Modified: 2013-12-31 01:55 UTC (History)
13 users (show)

Fixed In Version: libvirt-
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-12-31 01:55:41 UTC

Attachments (Terms of Use)

Description Alan Jenkins 2013-01-30 15:46:00 UTC
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
3. reboot
Actual results:

After the reboot, the guest system is shown as "saved" in virt-manager.

Expected results:

After the reboot, the guest system should be running.

Additional info:

- 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[1]: Starting Suspend Active Libvirt Guests...
Jan 30 15:17:11 fossil.scree.dyndns.org libvirt-guests[1279]: Can't connect to default. Skipping.
Jan 30 15:17:11 fossil.scree.dyndns.org systemd[1]: Started Suspend Active Libvirt Guests.

Comment 1 Alan Jenkins 2013-01-30 16:40:44 UTC
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).

Comment 2 Cole Robinson 2013-04-01 18:01:44 UTC
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.

Comment 3 Zbigniew Jędrzejewski-Szmek 2013-11-18 14:47:15 UTC
It seems that libvirt-guests.service has no dependency on libvirtd.service. It should probably have After=libvirtd.service.

Comment 4 Eric Blake 2013-11-18 15:46:44 UTC
Might be related to bug 1031696

Comment 5 Cole Robinson 2013-11-19 20:23:18 UTC
I've sent a patch upstream with the suggestion in Comment #3

Comment 6 Cole Robinson 2013-11-20 14:04:32 UTC
Upstream now:

commit d92036754a70098377798d93cb6d20378959e3a7
Author: Cole Robinson <crobinso@redhat.com>
Date:   Tue Nov 19 15:19:25 2013 -0500

    libvirt-guests: Run only after libvirtd

And pushed to F19 and F20 maint

Comment 7 Fedora Update System 2013-12-14 21:34:19 UTC
libvirt- has been submitted as an update for Fedora 20.

Comment 8 Fedora Update System 2013-12-16 07:07:39 UTC
Package libvirt-
* 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-'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 9 Fedora Update System 2013-12-31 01:55:41 UTC
libvirt- has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

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