Thanks for your fast answer, Alex. Will flag the VMs as HA. Indeed I was not interpreting correctly the "Resiliency policy" setting. For the record, I found it very well explained here: https://lists.ovirt.org/pipermail/users/2015-March/031896.html Best regards, On 24/08/18 10:06, Alex K wrote:

Hi,

On Fri, Aug 24, 2018, 10:25 Eduardo Mayoral <emayoral@arsys.es <mailto:emayoral@arsys.es>> wrote:

Hi,

    Recently I have had 2 oVirt hosts (oVirt 4.2, CentOS 7.5) crash unexpectedly (not at the same time). Both seem hardware related.

    In both cases oVirt did detect the host as non responsive, did a fence on the hosts and set the VMs which were running on the host at the time as "Down". So far, so good.

    The hosts were on 2 different clusters. Both had Migration policy / resilience policy set to "migrate Virtual Machines". The VMs are not configured as "Highly available", but my understanding is that with that resiliency policy, this makes no difference. My (probably wrong) expectation, is that oVirt should have attempted to start the VMs in another host. It did not. A colleague started the VMs manually and they started with no further issues.

    So. How should I configure oVirt to try to start the VMs on another host when the physical host they are running in crashes? 

You need to flag it as highly available.

    Thanks in advance!

-- Eduardo Mayoral.

_______________________________________________ Users mailing list -- users@ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/MNC6OPRD52PZK4...