Skip to main content

​
Overview

The VM Moves page provides a consolidated view of every VM evacuation performed by the Instance HA engine across all recent recovery notifications. Unlike the per-notification Recovery Progress tab, VM Moves aggregates evacuations from up to 50 recent notifications into a single sortable, searchable list — making it the primary tool for recovery auditing and troubleshooting.
Prerequisites
  • An active Xloud account with project access
  • Instance HA service enabled with at least one completed or in-progress recovery event

​
View VM Moves

1

Navigate to VM Moves

Navigate to Instance HA > VM Moves in the sidebar.The page loads all VM evacuations from recent notifications automatically.
2

Review the evacuation list

The table shows every individual VM evacuation, sorted by start time (most recent first).
ColumnDescription
VM NameInstance name. Falls back to instance UUID if no name is set
Instance IDVM UUID (copyable, truncated display showing first 8 characters)
NotificationParent notification UUID (copyable, truncated display)
Source HostThe failed compute host the VM was evacuated from
Destination HostThe healthy host the VM was moved to. Shows - if not yet assigned
TypeEvacuation type — typically evacuation
StatusColored tag with icon indicating the evacuation result
Start TimeWhen the evacuation started (default sort column, descending)
End TimeWhen the evacuation completed, or - if still in progress
MessageError details if the evacuation failed (displayed in red), otherwise -
3

Understand evacuation statuses

Each VM evacuation has one of four statuses:
StatusColorIconMeaning
PendingGreyClockEvacuation is queued but has not started
RunningBlueLoading spinnerEvacuation is actively in progress
SucceededGreenCheck circleVM was successfully recovered on the destination host
FailedRedClose circleEvacuation failed — check the Message column for details
VMs with Failed status require manual intervention. Check the error message, verify the destination host has sufficient capacity, and attempt a manual evacuation if needed. See Troubleshooting for resolution steps.
4

Refresh the data

Click the Refresh button in the page header to reload the latest VM move data. This fetches evacuations from the most recent 50 notifications.
During an active recovery, refresh periodically to see new VM evacuations appear as the engine processes each instance. For real-time auto-refreshing, use the Recovery Progress tab on the individual notification detail page instead.

​
VM Moves vs Recovery Progress

The Dashboard provides two ways to view VM evacuations. Choose based on your use case:
FeatureVM Moves PageRecovery Progress Tab
LocationInstance HA > VM MovesNotification detail > Recovery Progress
ScopeAll evacuations across up to 50 notificationsSingle notification only
Auto-refreshManual refresh buttonAuto-refreshes every 5 seconds when running
Summary statsNot shownTotal, succeeded, failed counts with progress indicator
Best forAuditing, historical review, cross-notification searchReal-time monitoring of an active recovery
Use Recovery Progress when you want to watch a single recovery event complete in real time. Use VM Moves when you need to review evacuation history across multiple events, or search for a specific VM’s recovery outcome.

​
Common Scenarios

Find all failed evacuations

Open Instance HA > VM Moves and look for rows with a red Failed status tag. The Message column shows the error reason. Common causes:
  • Insufficient capacity: No destination host has enough vCPU/memory
  • Shared storage not available: Instance uses local ephemeral disk
  • Compute service down: Target host’s nova-compute is not running
For each failed VM, attempt a manual evacuation:
Manually evacuate a failed instance
openstack server evacuate <instance-id> --host <target-host>
Open Instance HA > VM Moves and locate the VM by name or instance ID. Check that:
  • Status is Succeeded (green)
  • Destination Host shows a valid compute host
  • End Time is populated
Then verify the instance is running:
Confirm instance is active
openstack server show <instance-id> -c status -c "OS-EXT-SRV-ATTR:host"
Status is ACTIVE and the host matches the Destination Host from VM Moves.
Open Instance HA > VM Moves and sort by Start Time. The default sort is descending (most recent first). Scroll through to find evacuations in your time window.For CLI-based historical analysis:
Export VM moves to JSON for analysis
curl -s -H "X-Auth-Token: $TOKEN" \
  "$MASAKARI_ENDPOINT/v1/notifications?sort_key=updated_at&sort_dir=desc&limit=50" \
  | python3 -c "
import sys, json, requests, os
token = os.environ['TOKEN']
endpoint = os.environ['MASAKARI_ENDPOINT']
notifs = json.load(sys.stdin)['notifications']
all_moves = []
for n in notifs:
    r = requests.get(f'{endpoint}/v1/notifications/{n[\"notification_uuid\"]}/vmoves',
                    headers={'X-Auth-Token': token})
    all_moves.extend(r.json().get('vmoves', []))
json.dump(all_moves, sys.stdout, indent=2)
" > vm-moves-history.json

​
Next Steps

Recovery Workflows

Understand recovery methods and the Recovery Progress real-time view

Monitoring Status

View notifications, hosts, and notification details

Troubleshooting

Resolve failed evacuations and stuck recovery workflows

Protection Segments

Manage segments and host registrations