Overview
Live migration transfers a running instance from one hypervisor node to another without instance downtime. This enables host maintenance, workload rebalancing, and fault recovery. The instance remains accessible to users throughout the migration — memory pages and disk state are transferred iteratively while the instance continues running.Live Migration Prerequisites
- Shared storage (Xloud Distributed Storage) must be configured, or block migration must be enabled
- Both source and destination compute nodes must be
upandenabled - Both nodes must run compatible hypervisor software versions
- CPU models on source and destination must be compatible — configure a common CPU baseline in your compute configuration to prevent failures across nodes with different physical processor generations
- For instances with a virtual TPM, Xloud Key Management must be enabled for automatic secret transfer during migration
Migration Types
| Type | Shared Storage Required | Downtime | Best For |
|---|---|---|---|
| Live Migration | Yes | None | Standard workload movement with Xloud Distributed Storage-backed volumes |
| Block Migration | No | None | Instances on local ephemeral disk; disk content is copied to destination during migration |
| Cold Migration | No | Yes (instance paused) | Offline resize or host draining when live migration is not possible |
Migrate an Instance
- Dashboard
- CLI
Locate the instance
Log in to the Xloud Dashboard (
https://connect.<your-domain>) and navigate to
Admin → Compute → Instances. Use the project filter to locate the target
instance.Initiate live migration
In the Actions column, click Migrate Instance.Select the migration options in the dialog:
Click Migrate Instance to begin.
| Option | Description |
|---|---|
| Auto-select destination | The scheduler selects the best available host |
| Specify destination host | Manually target a specific compute node |
| Block migration | Enable for instances on local (non-shared) storage |
Post-Migration Verification
After a live migration completes, verify the instance is operating correctly on the destination host.- CLI
Confirm instance is ACTIVE on destination
Verify migration completed (not failed)
completedCheck instance console for application health
Instance status is
ACTIVE, host shows the destination node, and migration
status shows completed. Application logs show normal operation.Troubleshooting Migration Failures
| Error | Likely Cause | Resolution |
|---|---|---|
guest CPU doesn't match specification | CPU microarchitecture mismatch between hosts | Configure a common CPU baseline model via XDeploy under Compute → Advanced Settings → CPU Compatibility |
No valid host found | Destination lacks capacity or does not meet flavor requirements | Check destination host capacity with openstack hypervisor show <host> |
Connection timeout | Network disruption on the migration network | Verify connectivity between compute nodes; check firewall rules on the management interface |
Block migration disk copy failed | Insufficient free disk on destination | Check available disk with openstack hypervisor show <host> |
Next Steps
Compute Hosts
Disable hosts before maintenance and drain them using live migration.
Troubleshooting
Resolve live migration failures and other common Compute issues.
Admin Guide
Return to the Compute Administration Guide index.