VMs do not shutdown when powering off a F20 host

[Rick Stevens]

On 11/19/2013 10:32 AM, Juan Orti Alcaine issued this missive:
> Hello,
>
> I have upgraded to F20 and now my virtual machines don't shutdown when I
> shutdown the host.
>
> In /etc/sysconfig/libvirt-guests I have:
> ON_SHUTDOWN=shutdown
> SHUTDOWN_TIMEOUT=100
>
> This is what I see in the log (in Spanish):
>
> # journalctl -a _SYSTEMD_UNIT=libvirt-guests.service
> _SYSTEMD_UNIT=libvirtd.service
>
> nov 17 23:38:15 xenon.miceliux.com libvirtd[750]: libvirt version: 1.1.3.1,
> package: 1.fc20 (Fedora Project, 2013-11-06-18:12:08,
> buildvm-04.phx2.fedoraproject.org)
> nov 17 23:38:15 xenon.miceliux.com libvirtd[750]: Received unexpected event 1
> nov 17 23:38:16 xenon.miceliux.com libvirtd[750]: Error interno: Fin del
> archivo desde monitor
> nov 17 23:38:16 xenon.miceliux.com libvirtd[750]: Error interno: Falta objeto
> de respuesta de monitor
> nov 17 23:38:16 xenon.miceliux.com libvirt-guests.sh[21049]: Ejecutando
> huéspedes en URI default:lithium
> nov 17 23:38:16 xenon.miceliux.com libvirt-guests.sh[21049]: Cerrando
> huéspedes en URI default...
> nov 17 23:38:16 xenon.miceliux.com libvirt-guests.sh[21049]: Starting shutdown
> on guest: lithium
> nov 17 23:38:17 xenon.miceliux.com libvirtd[750]: Object (nil) ((unknown)) is
> not a virObjectLockable instance
> nov 17 23:38:17 xenon.miceliux.com libvirtd[750]: Argumento inválido: el
> monitor no debe poseer un valor NULL
> nov 17 23:38:17 xenon.miceliux.com libvirt-guests.sh[21049]: Error:Falló al
> apagar el dominio 3ee0acb2-3da9-7045-868c-3dec16e03ad1
> nov 17 23:38:17 xenon.miceliux.com libvirt-guests.sh[21049]: Error:Argumento
> inválido: el monitor no debe poseer un valor NULL
>
>
> Which translated is something like:
>
> nov 17 23:38:15 xenon.miceliux.com libvirtd[750]: libvirt version: 1.1.3.1,
> package: 1.fc20 (Fedora Project, 2013-11-06-18:12:08,
> buildvm-04.phx2.fedoraproject.org)
> nov 17 23:38:15 xenon.miceliux.com libvirtd[750]: Received unexpected event 1
> nov 17 23:38:16 xenon.miceliux.com libvirtd[750]: Internal error: End of file
> from monitor
> nov 17 23:38:16 xenon.miceliux.com libvirtd[750]: Internal error: Response
> object from monitor is missing
> nov 17 23:38:16 xenon.miceliux.com libvirt-guests.sh[21049]: Running guests in
> URI default:lithium
> nov 17 23:38:16 xenon.miceliux.com libvirt-guests.sh[21049]: Closing guests in
> default URI...
> nov 17 23:38:16 xenon.miceliux.com libvirt-guests.sh[21049]: Starting shutdown
> on guest: lithium
> nov 17 23:38:17 xenon.miceliux.com libvirtd[750]: Object (nil) ((unknown)) is
> not a virObjectLockable instance
> nov 17 23:38:17 xenon.miceliux.com libvirtd[750]: Invalid argument: monitor
> must not have a NULL value
> nov 17 23:38:17 xenon.miceliux.com libvirt-guests.sh[21049]: Error:Failed to
> shutdown domain 3ee0acb2-3da9-7045-868c-3dec16e03ad1
> nov 17 23:38:17 xenon.miceliux.com libvirt-guests.sh[21049]: Error:Invalid
> argument: monitr must not have a NULL value
>
>
> Any idea? do I open a bug report?

F20 is not officially released yet so this isn't the forum for this
question. It should be directed to the fedora-test-list. If you
subscribe there, you'll see there have been a number of issues with
libvirt and shutting down VMs.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    ricks at alldigital.com -
- AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
-                                                                    -
-          Consciousness: that annoying time between naps.           -
----------------------------------------------------------------------