RHEV: Hypervisors in non-responding state, impossible to start vdsmd service.

Solution Verified - Updated -

Issue

A hypervisor is suddenly set to the non-responsive state without any obvious reason.
Impossible to start vdsmd service.

Environment

  • Red Hat Enterprise Virtualization (RHEV) 3.1
  • vdsm-4.10.2-1.12 and older

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