<div dir="ltr">I believe you would accomplish this by setting a VM to be highly available (like the engine). Then engine makes sure this VM is up on at least one node through lease agreements (IIRC). In either case, I think this is what you want</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 4, 2017 at 10:25 AM, Chris Adams <span dir="ltr"><<a href="mailto:cma@cmadams.net" target="_blank">cma@cmadams.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I have an oVirt cluster that was hard shutdown last night (fire is bad,<br>
and firemen killed the generators for their safety). When it came back<br>
up, it did not start any VMs other than the hosted engine.<br>
<br>
Is that expected? I know this is not a normal use case, but is there a<br>
way to set VMs to start on cluster boot?<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Chris Adams <<a href="mailto:cma@cmadams.net">cma@cmadams.net</a>><br>
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
</font></span></blockquote></div><br></div>