vMotion fails at 63% with the error: The migration exceeded the maximum switchover time of 100 seconds

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• Cannot vMotion a virtual machine
• vMotion fails at 63%
• In the virtual machine's vmware.log file, you see entries similar to:
  
  YYYY-11-06T15:45:31.005Z| vmx| Migrate_SetFailure: The migration has exceeded the maximum switchover time of 100 second(s). ESX has preemptively failed the migration to allow the virtual machine to continue running on the source. To avoid this failure, either increase the maximum allowable switchover time or wait until the virtual machine is performing a less intensive workload.
  
  
• In the /var/log/hostd.log file of the source host, you see entries similar to:
  
  YYYY-11-06T03:47:43.846Z [FFC44A90 verbose 'vm:/vmfs/volumes/########-####-########1208/[folder]/[VM name].vmx'] VMotionLastStatusCb: Failed with error 4: The migration has exceeded the maximum switchover time of 100 second(s). ESX has preemptively failed the migration to allow the virtual machine to continue running on the source. To avoid this failure, either increase the maximum allowable switchover time or wait until the virtual machine is performing a less intensive workload.

Environment

VMware vCenter Server 

VMware vSphere ESXi

Cause

This issue may be caused by time configuration issues on both the source and destination ESX/ESXi hosts.

Resolution

To resolve this issue, correct any time configuration issues on the source and destination hosts.

 

For more information, see Troubleshooting NTP on ESX and ESXi 6.x / 7.x / 8.x

Additional Information

Same error is noticed at vmotion failing at 69%

2024-09-10T04:52:10.868Z In(05) vmx - [msg.checkpoint.migration.maxSwitchoverTimeExceeded] The migration has exceeded the maximum switchover time of 100 second(s). ESX has preemptively failed the migration to allow the VM to continue running on the source.  To avoid this failure, either increase the maximum allowable switchover time or wait until the
 VM is performing a less intensive workload.

+ To resolve this issue we need to upgrade to vSphere 8.x release 8.0 U3 as this is resolved in this release