High Availability

Virtualizor now supports High Availability for KVM Virtualization.

NOTE: This feature is in Public Beta.


  • CentOS 7.x
  • yum
  • Shared Storage to create the VPS disks.
  • Shared mount point for KVM XML configuration files at /etc/libvirt
  • At least four nodes to create HA cluster with Virtualizor KVM (to get reliable quorum) includes Virtualizor master.
  • Shared IPPool among the HA Server group, so that the same IP can work on the other server where VM will get migrated on failure.
  • Since Version 2.9.9+


  • Login to the Virtualizor Master with the servers root details
  • Click on Servers ->Add Server Groups and check the High Availability checkbox to enable High Availability for the Server Group.

NOTE: You MUST add the server group with High Availability enabled before adding Slave servers under High Availability cluster. Otherwise Virtualizor will not be able to add HA cluster and install HA utilities on new server which will be added under HA enabled server group.

Check if Server Group has HA enabled.
Click on Servers -> Server Groups/Regions

Add Server in HA enabled Server Group

Once the HA server group is added and enabled you are ready to add new servers in HA group/cluster.
To add new server under HA Server Group, you will need to select HA enabled server group while adding the new server.

Once you have entered all the information for adding the new server with HA enabled server group, click on Add Server.
You can check the installation process on task wizard.

Create VPS with HA Enabled

If the server has HA enabled, VM will be automatically create with HA enabled.
NOTE: Above option (High Availability) will be shown if the selected server is under HA enabled server group.

Monitor HA Cluster(s)

Once you have created/added Server with HA enabled, you can monitor the resource created on those HA cluster.

To check resource and node go to Admin Panel -> Virtual Servers -> High Availability

You can create select the HA enabled Group from the dropdown and it will fetch the status of that cluster.

Was this helpful to you?