After RHEV-M had fenced a hypervisor a guest previously running on it is marked as non-responsive and is not able to start.

Solution Verified - Updated -

Issue

  • 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.

Environment

  • Red Hat Enterprise Virtulization 3.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content