Support Policies for RHEL High Availability Clusters - RHEL libvirt/KVM Virtual Machines as Cluster Members

Updated -



Applicable Environments

  • Red Hat Enterprise Linux (RHEL) with the High Availability Add-On
  • Using one or more RHEL libvirt/KVM hypervisor to provide VMs that may serve as High Availability cluster members

Useful References and Guides


This guide offers Red Hat's policies, requirements, and limitations applicable to the use of RHEL libvirt/KVM virtual machines as members of a RHEL High Availability cluster. Users of RHEL High Availability software components should adhere to these policies by installing only on the approved platforms in order to be eligible to receive assistance from Red Hat Support with the appropriate support subscriptions.


Consider general conditions for support of RHEL High Availability in virtualization environments

Supported RHEL libvirt/KVM products/releases with RHEL High Availability: Red Hat provides support for RHEL High Availability deployments consisting of members that are libvirt/KVM virtual machines running on RHEL hosts that are still actively supported by Red Hat.

Mixed baremetal and libvirt/KVM VM clusters: Red Hat provides support for clusters consisting of both baremetal systems and libvirt/KVM virtual machines, subject to these other applicable policies.

Live Migration is not supported: For more information see: Is live migration supported for VMs that are members of a RHEL cluster?

KVM VMs (cluster nodes) running on IBM Power host (hypervisor) is not supported: Virtual machines hosted by KVM on IBM Power host is not supported.

Fencing methods

Power Fencing agent used with KVM/libvirt devices is fence_xvm :