On hypervisor crash, VMs cannot be started on other hypervisors
Issue
- Virtual machines can not be started when a hypervisor crashed, until it is rebooted and back online. Setting 'Host was rebooted' manually does not help.
- Hypervisor can not be switched to maintenance after crash, until it is back online.
Environment
- Red Hat Enterprise Virtualisation (RHEV) 3.6
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.
