Migrate a VMNEW
Move a VM to another node of its cluster; its HA rule and backup job follow.
Start a migration
- 1Open the VM and find the host in its details.
- 2Click the host and choose Migrate to node (needs vm.migrate).
- 3Pick a target node and confirm. The VM's name shimmers until it has arrived.
A running VM is migrated live, including local disks. The request returns immediately; the migration continues in the background.
What moves with it
- High availability: if the VM is in a node-affinity rule, its membership moves to the target node's rule before the migration, so HA allows the move and does not pull the VM back.
- Backups: after the move, the VM is taken out of the old node's backup job and added to the target node's job.
- The new host is recorded and the migration is written to Activity, including what happened with the HA rule and backup job.
The HA and backup adjustments are best-effort and never fail the migration itself. Check the activity entry if something looks off.
When a migration is refused
- The VM is still provisioning or is locked by a configuration run.
- The target is the current node, is not online, is not a node of the VM's cluster, or is not enabled for the project.
- The VM is not linked to a Proxmox guest, or the cluster cannot be reached.
Features on this page
- VM migrationNEW
More in Virtual machinesAll topics
Create a VMThe seven-step New VM wizard, how names map to VMIDs, placement, and what happens after Create.Power actionsStart, shutdown, reboot, hard stop, suspend and resume, each with its own permission, for one VM or many.The VM page and consoleThe Virtual Machines list, a VM's tabs, and the browser console (noVNC, SSH and RDP).