Storage vMotion to vSAN Fails with "Timed out waiting to capture VM ID at destination" - VMware vCenter
search cancel

Storage vMotion to vSAN Fails with "Timed out waiting to capture VM ID at destination" - VMware vCenter

book

Article ID: 458676

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

When performing a Storage vMotion for a virtual machine to a vSAN datastore, the task may fail at 100% with the error:

A general system error occurred: Timed out waiting to capture VM ID at destination

This occurs specifically when the virtual machine currently has virtual disks distributed across mixed storage (e.g., some on VMFS and others on vSAN), and you attempt to migrate the remaining disks (such as the OS disk) to the same vSAN datastore where a portion of the VM's disks already reside.

Following this failure, the virtual machine may become orphaned and appear under "Discovered VMs" even though the guest OS remains running and reachable.

Environment

Mixed storage configurations (VMFS and vSAN)

Cause

The failure is triggered when the migration destination (vSAN) already contains a directory for that specific virtual machine because other disks of the same VM are already stored there. 

Resolution

This is a known issue impacting VMware vCenter. Subscribe to this KB article to be updated if a fix version becomes available.

Workaround:

To successfully migrate the remaining virtual disks to the target vSAN datastore, ensure the destination vSAN does not already contain a directory for the VM:

  1. Migrate the virtual disks off the target vSAN datastore to a temporary non-vSAN (VMFS) datastore so that no part of the VM remains on the target vSAN.
  2. Once the destination vSAN is clear of the VM's directory, perform a single Storage vMotion to move the entire virtual machine to the target vSAN datastore in one operation.