Free tech learning for everyone, from basics to pro

VirtualizationSystems ArchitectureIntermediate

High availability and live migration for virtual machines

In short: Clusters of hypervisor hosts with shared storage let VMs restart automatically when a host fails and move between hosts while running. Live migration enables maintenance with no downtime, load balancing spreads work, and admission control reserves enough spare capacity to survive a failure.

Why clusters matter

When dozens of VMs run on one physical host, that host becomes a big single point of failure. Hypervisor platforms solve this by grouping hosts into a cluster that shares storage and networks. The cluster software monitors every host and can move or restart VMs. Examples include vSphere HA and DRS, Windows Server Failover Clustering with Hyper-V, and Proxmox VE HA.

Cluster featuresVM clustershared storageHA restarthost failureLive migrationno downtimeLoad balancingDRS-styleFault toleranceshadow VMMaintenance modedrain hostAdmission controlkeep spare
Figure 1. A cluster of hosts with shared storage enables several availability features.

HA restart

With VM high availability (HA), hosts exchange heartbeats. If one host stops responding, the others confirm the failure (often by checking the shared storage as well, to avoid acting on a mere network problem) and restart its VMs elsewhere. This is not zero downtime: the VMs reboot, so expect a few minutes of outage. It does, however, remove the need for someone to notice and act at 3 a.m.

Admission control makes HA work in practice. It reserves enough spare CPU and memory, for example one host's worth (N+1), so there is room to restart failed VMs. Without it, a busy cluster may have nowhere to put them. Set restart priorities so infrastructure such as domain controllers and DNS comes up before application servers.

Live migration

Live migration in stepsPre-copycopy memoryIterateresend changedpagesPausemillisecondsSwitchfinal state,ARPResumeon new host
Figure 2. Memory is copied while the VM runs, so the final pause is too short for users to notice.

Live migration (vMotion in VMware, Live Migration in Hyper-V) moves a running VM to another host without shutting it down. Memory is copied in rounds while the VM keeps working; then the VM is paused very briefly, the last changes are sent, and it resumes on the new host. The new host announces the VM's MAC address so switches update their tables. Users typically notice nothing.

Requirements usually include:

  • Shared storage, or a storage migration at the same time (shared-nothing migration).
  • The same port groups and VLANs on both hosts.
  • Compatible CPUs; features such as VMware EVC or Hyper-V processor compatibility mode hide differences between CPU generations.
  • A fast, isolated migration network, ideally 10 Gb/s or more, encrypted if it crosses untrusted links.

Other availability features

FeatureWhat it doesDowntime on host failure
HA restartReboots VMs on surviving hostsMinutes (VM restarts)
Fault toleranceKeeps a live shadow copy of a VM on another hostNear zero, but costly and limited
Load balancing (DRS-style)Moves VMs to spread load automaticallyNone; prevents hotspots
Maintenance modeLive migrates all VMs off a host before patchingNone for planned work
Application clusteringDatabase or app replicas with their own failoverSeconds, app-aware

Affinity and anti-affinity rules control placement. Anti-affinity keeps two domain controllers or two web servers on different hosts, so one failure cannot take out both.

Tip: HA protects against host hardware failure, not against a corrupted VM, a bad patch or the loss of the whole site. Combine it with backups, application-level redundancy and disaster recovery to another location.

Test HA regularly: put a host into maintenance mode, or in a test cluster pull its power, and check that VMs restart in the right order and that admission control left enough room.

Practice

Does VM HA give zero downtime when a host fails?
No. The VMs are restarted on another host, so there is a short outage while they boot. Fault tolerance or application clustering is needed for near-zero downtime.
What is the purpose of admission control?
It reserves spare capacity in the cluster so there is room to restart VMs if a host fails.
Why would you set an anti-affinity rule for two domain controllers?
To keep them on different hosts, so a single host failure cannot take both offline.

Key takeaways

  • Clusters with shared storage let VMs restart or move between hosts.
  • HA restarts VMs after host failure; expect a short outage.
  • Live migration moves running VMs with no noticeable downtime.
  • Admission control and restart priorities make HA reliable.
  • Use anti-affinity for redundant pairs and combine HA with backups and DR.
Tracks your learning on this device only. See your progress on the learning paths.

About the author

Mohamed Fayas

Founder of FM TecHub. CCNA certified, with a BTEC HND in Network Engineering, and BEng (Hons) in Computer Networking and Cloud Security. He writes practical, plain-English guides on networking, security and cloud.

More about the author

Original content written by Mohamed Fayas for FM TecHub. © 2026 FM TecHub. You're welcome to share a link to this page; please don't copy the text elsewhere without permission.

Stay up to date by email

New notes, tools and security news from FM TecHub, explained simply. Free.

We only use your email to send these updates. See our privacy policy.