Linux VPS

Migrate Proxmox VMs between nodes (live and offline)

Move Proxmox VMs and containers between cluster nodes with live or offline migration, including local disks, and avoid the common CPU and storage pitfalls.

IntermediateProxmox VE2 min read

In a Proxmox cluster you can migrate a VM between nodes with a couple of clicks, often while it keeps running. Use it to empty a node before updates or hardware work, or to spread load.

Before you start

  • A working cluster (cluster setup).
  • Shared storage for fastest live migration, or enough local space on the target for local disks.
  • A CPU type that exists on both nodes. CPU type host can fail between different CPU models; a generic type such as x86-64-v2-AES is safer in mixed clusters.
  • No local ISO attached and no passthrough devices on the VM.

Live migrate a Proxmox VM

  1. Right-click the running VM and choose Migrate.
  2. Select the Target node. Mode shows Online for running VMs.
  3. If disks are on local storage, choose the target storage; Proxmox copies them live (this takes longer).
  4. Click Migrate and follow the task log. Downtime is usually well under a second.

From the shell:

qm migrate 105 pve2 --online

Add --with-local-disks when disks are on local storage.

Offline migration

Stopped VMs migrate offline: their configuration (and local disks) moves to the target node. Containers are migrated in restart mode, which stops and starts them on the target:

pct migrate 110 pve2 --restart

Empty a node for maintenance

  • Use Node → Bulk Actions → Bulk Migrate to move many guests at once.
  • With HA, enable maintenance mode so HA moves resources for you (high availability).

Tip: Set a dedicated migration network under Datacenter → Options → Migration Settings so large copies do not slow your public traffic.

Troubleshooting

  • "can't migrate local disk" or local resource error: detach local ISOs or use the local disk migration option.
  • Migration fails with CPU errors: change the VM CPU type to one supported by both nodes and restart the VM.
  • Very slow: use a faster migration network or shared storage.

Frequently asked questions

Is live migration safe for databases?

Yes, memory is copied and the switch-over is near-instant, but run it in quieter hours for very busy VMs.

Can I migrate between separate (non-clustered) hosts?

Use backup and restore, or the remote migration feature in recent versions where available.

Does the VM keep its IP?

Yes, if both nodes connect to the same network and bridge.

Next steps

Was this guide helpful?

Still stuck?

Ask MdmHost AI for a quick answer, or open a ticket and our team will take a look. We are here 24/7.