- After RHEV-M had fenced a hypervisor a guest previously running on it is marked as non-responsive and is not able to start.
- Once the hypervisor had rebooted it was originally marked in a non-operational state.
- Once the hypervisor was correctly up the guest remained in a non-responsive state, unable to be started on any hypervisor.
- Red Hat Enterprise Virtulization 3.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.