[ClusterLabs] timeout for stop VirtualDomain running Windows 7

Lentes, Bernd bernd.lentes at helmholtz-muenchen.de
Mon Jul 24 13:30:28 EDT 2017


i have a VirtualDomian resource running a Windows 7 client. This is the respective configuration:

primitive prim_vm_servers_alive VirtualDomain \
        params config="/var/lib/libvirt/images/xml/Server_Monitoring.xml" \
        params hypervisor="qemu:///system" \
        params migration_transport=ssh \
        params autoset_utilization_cpu=false \
        params autoset_utilization_hv_memory=false \
        op start interval=0 timeout=120 \
        op stop interval=0 timeout=130 \
        op monitor interval=30 timeout=30 \
        op migrate_from interval=0 timeout=180 \
        op migrate_to interval=0 timeout=190 \
        meta allow-migrate=true target-role=Started is-managed=true

The timeout for the stop operation is 130 seconds. But our windows 7 clients, as most do, install updates from time to time .
And then a shutdown can take 10 or 20 minutes or even longer.
If the timeout isn't as long as the installation of the updates takes then the vm is forced off. With all possible negative consequences.
But on the other hand i don't like to set a timeout of eg. 20 minutes, which may still not be enough in some circumstances, but is much too long
if the guest doesn't install updates.

Any ideas ?



Bernd Lentes 

institute of developmental genetics 
Gebäude 35.34 - Raum 208 
HelmholtzZentrum München 
bernd.lentes at helmholtz-muenchen.de 
phone: +49 (0)89 3187 1241 
fax: +49 (0)89 3187 2294 

no backup - no mercy

Helmholtz Zentrum Muenchen
Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH)
Ingolstaedter Landstr. 1
85764 Neuherberg
Aufsichtsratsvorsitzende: MinDir'in Baerbel Brumme-Bothe
Geschaeftsfuehrer: Prof. Dr. Guenther Wess, Heinrich Bassler, Dr. Alfons Enhsen
Registergericht: Amtsgericht Muenchen HRB 6466
USt-IdNr: DE 129521671

More information about the Users mailing list