Pre-copy migration
Can the network copy memory faster than the guest changes it?
Pre-copy sends memory while the VM continues running. Each round recopies pages dirtied since the previous pass. Eventually the system pauses the guest, transfers the remaining state and resumes it on the destination.
dirty-page rate ÷ usable migration bandwidthIf the ratio approaches or exceeds 1, repeated copying may not converge.- Round 1Copy most memoryguest keeps writing
- Round 2Copy dirty pagesnew pages become dirty
- Final pauseCPU/device state + remainderdowntime window
- ResumeDestination becomes activevalidate network and storage
A measurable example
Use numbers before promising “zero downtime.”
| VM memory | Dirty rate | Usable bandwidth | Interpretation |
|---|---|---|---|
| 32 GiB | 300 MiB/s | 800 MiB/s | Likely room to converge |
| 32 GiB | 900 MiB/s | 800 MiB/s | Pre-copy may not converge |
These are illustrative inputs, not a VMBook benchmark. Real measurement must include compression, protocol overhead, storage transfer, device state and the permitted downtime.
Failure timeline
HA begins where a normal migration cannot.
Host stops responding
Network loss and host failure may look identical from the controller.
Quorum decides
Surviving members determine whether they have authority to act.
Fence the source
Power or storage fencing prevents two hosts from writing the same machine state.
Recover the workload
Restart from accessible storage, then validate dependencies and service state.
Why fencing is not optional
If a disconnected host is still running while another host starts the same VM against shared writable storage, both can believe they are authoritative. That split-brain condition can corrupt data. A ping timeout is not proof that the old writer is dead.
Compatibility checklist
- CPU baseline: destination must expose every guest-visible feature required by the running state;
host-passthroughcan improve performance while reducing migration compatibility. - Storage: shared, replicated or separately migrated with ordering and consistency understood.
- Network: destination must preserve required VLAN, address, MTU and security policy.
- Devices: passthrough hardware and host-specific devices can block migration.
- Recovery: application consistency and restart behavior still need testing after the VM resumes.