VMware vMotion Troubleshooting: Network, CPU and Compatibility Checklist

Confirm the vMotion VMkernel path

Verify that both source and destination ESXi hosts have a VMkernel adapter configured for vMotion and that the intended network is reachable between them.

Test the migration network

Use vmkping with the correct VMkernel interface and test the configured MTU. An MTU mismatch can produce intermittent or performance-related migration failures.

Check CPU compatibility

Review EVC and CPU feature compatibility when moving a VM between different processor generations. A CPU compatibility failure can block migration even when networking is healthy.

Check VM hardware and device constraints

Review passthrough devices, CPU settings, mounted ISO files and other configuration items that may constrain migration.

Separate cold and hot data

Current vMotion networking guidance distinguishes cold data from hot VM state. Review which VMkernel traffic path is carrying the migration data in your design.

Check concurrent migrations

Multiple migrations can saturate a 1 Gbps vMotion network and affect other services. Limit concurrency or move migration traffic to a higher-capacity network when required.

Validate after correction

Run one controlled migration first, then increase concurrency. Capture the task duration and network utilization so you can establish a baseline.

vmkping -I vmkX <destination-vMotion-IP>
vmkping -I vmkX -s 8972 -d <destination-vMotion-IP>
esxcli network ip interface list