RHEV Cluster Resilience Policy "Migrate Virtual Machines" do not restart guest on another hypervisor until marked as "Highly Available".
Issue
- RHEV Cluster Resilience Policy "Migrate Virtual Machines" do not restart guest on another hypervisor until marked as "Highly Available".
- Affected VM don't start on another hypervisor not before checkbox "Highly Available" in VM is activated.
- What are the differences between Cluster Resilience Policy and VM being marked as "Highly Available"?
Environment
- Red Hat Enterprise Virtualization 3.3
- Red Hat Enterprise Virtualization 3.4
- Red Hat Enterprise Virtualization 3.5
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
