Also consider setting a reasonable 'TimeoutStartSec=' in your systemd service file when you create the service... Best Regards, Strahil Nikolov В сряда, 30 септември 2020 г., 20:18:01 Гринуич+3, Strahil Nikolov via Users <users@ovirt.org> написа: I would create an ansible playbook that will be running from the engine: 1. Check the engine's health page via uri module and wait_for (maybe with a regex) Healthpage is : https://engine_FQDN/ovirt-engine/services/health 2. Use ansible ovirt_vm module to start your vms in the order you want 3. Test the playbook 4. Create a oneshot systemd servce that starts after 'ovirt-engine.service' and runs your playbook Best Regards, Strahil Nikolov В сряда, 30 септември 2020 г., 18:27:13 Гринуич+3, Jeremey Wise <jeremey.wise@gmail.com> написа: When I have to shut down cluster... ups runs out etc.. I need a sequence set of just a small number of VMs to "autostart" Normally I just use DNS FQND to connect to oVirt engine but as two of my VMs are a DNS HA cluster.. as well as NTP / SMTP /DHCP etc... I need those two infrastructure VMs to be auto boot. I looked at HA settings for those VMs but it seems to be watching for pause /resume.. but it does not imply or state auto start on clean first boot. Options? -- penguinpages _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VAYHFFSANCBRN4... _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/X2TC2S56HVRDE3...