Viewing activities
On the Monitoring > Activities screen, you can view and manage activities related to VM migrations, including manually initiated migrations and migrations triggered by resource policies.
Limitations
- You can retry a migration only if its status is "Failed" and it is still eligible.
Prerequisites
- VM migrations have been initiated either either manually, as described in Migrating virtual machines, or automatically by resource policies, as described in Using resource policies.
To view an activity
Admin panel
- Go to the Monitoring > Activities screen to view the list of VM migration activities.
- Locate and click the required VM migration activity.
-
On the activity right pane, review the activity information:
- The Tasks tab shows the history of associated activity tasks.
- The Details tab displays the activity type, status, initiator, object name, start and completion time.
Command-line interface
Use the following command:
vinfra service compute server migration show <migration_uuid>
<migration_uuid>- Migration UUID
For example, to view the details of the last VM migration activity, run:
# vinfra service compute server migration list +----------------+--------------+-------------+---------+----------------+-------------+-----------+---------------------+---------------------+ | migration_uuid | server_id | server_name | status | type | source_node | dest_node | start_time | finish_time | +----------------+--------------+-------------+---------+----------------+-------------+-----------+---------------------+---------------------+ | b8e57a7e<...> | 1af6d1dc<...> | vm4 | success | live-migration | node001 | node002 | 2026-02-25T20:33:41 | 2026-02-25T20:33:59 | | 0efa0953<...> | f30fae5d<...> | vm1 | failed | live-migration | node005 | node003 | 2026-02-25T20:30:20 | 2026-02-25T20:30:37 | +---------------+---------------+-------------+---------+----------------+-------------+-----------+---------------------+---------------------+ # vinfra service compute server migration show b8e57a7e-8e08-4b09-b160-87346f9554aa +----------------+--------------------------------------------------------------------+ | Field | Value | +----------------+--------------------------------------------------------------------+ | dest_compute | node002.vstoragedomain | | dest_host | | | dest_node | node002.vstoragedomain | | domain_id | default | | fault | | | finish_time | 2026-02-25T20:33:59.694354 | | history | - details: Performing post live migration operations. | | | event: compute_post_live_migration_at_destination | | | finish_time: '2026-02-25T20:33:58.228835' | | | host: node002.vstoragedomain | | | hostId: 288e46deb22981c69421b20eab0315873f602bbd7b96ed5dd498cdff | | | result: Success | | | start_time: '2026-02-25T20:33:56.871407' | | | traceback: null | | | - details: Live migrating instance. | | | event: driver__live_migration_operation | | | finish_time: '2026-02-25T20:33:55.726310' | | | host: null | | | hostId: '' | | | result: Success | | | start_time: '2026-02-25T20:33:51.283914' | | | traceback: null | | | - details: Preparing for live migration on destination node. | | | event: compute_pre_live_migration | | | finish_time: '2026-02-25T20:33:51.122364' | | | host: node002.vstoragedomain | | | hostId: 288e46deb22981c69421b20eab0315873f602bbd7b96ed5dd498cdff | | | result: Success | | | start_time: '2026-02-25T20:33:44.400671' | | | traceback: null | | | - details: Preparing for live migration on source node. | | | event: compute_live_migration | | | finish_time: '2026-02-25T20:33:44.290530' | | | host: node001.vstoragedomain | | | hostId: 5af5c1ec1278dd2d2ed52c4ad197e5ba2e5b5cc36dadedff5ee416dd | | | result: Success | | | start_time: '2026-02-25T20:33:44.234010' | | | traceback: null | | | - details: Checking if migration from source node is possible. | | | event: compute_check_can_live_migrate_source | | | finish_time: '2026-02-25T20:33:43.836884' | | | host: node001.vstoragedomain | | | hostId: 5af5c1ec1278dd2d2ed52c4ad197e5ba2e5b5cc36dadedff5ee416dd | | | result: Success | | | start_time: '2026-02-25T20:33:43.671252' | | | traceback: null | | | - details: Checking if migration to destination node is possible. | | | event: compute_check_can_live_migrate_destination | | | finish_time: '2026-02-25T20:33:43.901423' | | | host: node002.vstoragedomain | | | hostId: 288e46deb22981c69421b20eab0315873f602bbd7b96ed5dd498cdff | | | result: Success | | | start_time: '2026-02-25T20:33:42.942913' | | | traceback: null | | | - details: Received request to live migrate instance. | | | event: conductor_live_migrate_instance | | | finish_time: '2026-02-25T20:33:44.221049' | | | host: node002.vstoragedomain | | | hostId: 288e46deb22981c69421b20eab0315873f602bbd7b96ed5dd498cdff | | | result: Success | | | start_time: '2026-02-25T20:33:41.090806' | | | traceback: null | | migration_uuid | b8e57a7e-8e08-4b09-b160-87346f9554aa | | progress | 100 | | project_id | 83b0ed344abc4af88cc3c24fb98d948f | | request_id | req-1b9087a6-ea9a-4fac-9944-eddd6883155a | | server_id | 1af6d1dc-1672-4f3b-b6a6-394765b91908 | | server_name | vm4 | | source_compute | node001.vstoragedomain | | source_node | node002.vstoragedomain | | start_time | 2026-02-25T20:33:41.138167 | | status | success | | type | live-migration | | user_id | ec658b4a9d644e59a8ed4b2b5dce72d3 | | username | admin | +----------------+--------------------------------------------------------------------+
To cancel an ongoing activity
Admin panel
- On the Monitoring > Activities screen, click the required ongoing VM migration activity.
- On the activity right pane, click Cancel.
Command-line interface
Use the following command:
vinfra service compute server migration abort <server>
<server>- Virtual machine ID or name
For example, to abort a queued or ongoing migration for the VM vm1, run:
# vinfra service compute server migration abort vm1
To retry a failed activity
Admin panel
- On the Monitoring > Activities screen, click the required failed VM migration activity.
- On the activity right pane, click Retry.
Command-line interface
Use the following command:
vinfra service compute server migration retry <server> <migration_uuid>
<server>- Virtual machine ID or name
<migration_uuid>- Migration UUID
For example, to retry a migration with the ID 0efa0953-2b90-4bec-8dc1-f0bc294f4cbc for the VM vm1, run:
# vinfra service compute server migration retry vm1 0efa0953-2b90-4bec-8dc1-f0bc294f4cbc