[libvirt] qemu-kvm blocked for more than 120 seconds when "libvirt-guests" is enabled

[Andrea Bolognani]

On Sat, 2016-12-31 at 17:25 +0100, Oscar Segarra wrote:
[...]
> [root at vdicnode01 ~]# service libvirt-guests status
> Redirecting to /bin/systemctl status  libvirt-guests.service
> ● libvirt-guests.service - Suspend Active Libvirt Guests
>    Loaded: loaded (/usr/lib/systemd/system/libvirt-guests.service; disabled; vendor preset: disabled)

This is weird, libvirt-guests.service is disabled yet is being
stopped at shutdown, according to your screenshots.

>    Active: active (exited) since Sat 2016-12-31 17:13:34 CET; 5s ago
>      Docs: man:libvirtd(8)
>            http://libvirt.org
>   Process: 6619 ExecStart=/usr/libexec/libvirt-guests.sh start (code=exited, status=0/SUCCESS)
>  Main PID: 6619 (code=exited, status=0/SUCCESS)
> 
> Dec 31 17:13:34 vdicnode01.vdicube.com systemd[1]: Starting Suspend Active Libvirt Guests...
> Dec 31 17:13:34 vdicnode01.vdicube.com libvirt-guests.sh[6619]: libvirt-guests is configured not to start any guests on boot
> Dec 31 17:13:34 vdicnode01.vdicube.com systemd[1]: Started Suspend Active Libvirt Guests.
> [root at vdicnode01 ~]#
> 
> If I stop locally libvirt-guests (as root) Looks work perfectly:
> 
> [root at vdicnode01 ~]# virsh list
>  Id    Name                           State
> ----------------------------------------------------
> 
> [root at vdicnode01 ~]#

What does 'systemctl status libvirt-guests' tell you
at this point?

My only guess is that your guests might be taking too
long to shut down cleanly, which is not a problem when
you're stopping the service while the host is running
but causes a timeout during shutdown.

-- 
Andrea Bolognani / Red Hat / Virtualization