Please enable Javascript for better experience...
 
Storage vMotion Fails with error: The migration has exceeded the maximum switchover time of 100 second(s).
By Pranay Jha | Jun 16, 2016 | In Tips | Update: Jun 21, 2016 | Total Views [ 1197 ]
Taged In
(3 Like)
Rate

Issue:-

While performing Storage vMotion, it fails with below error at 65-70%.

A general system error occurred: 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.

Solution:-

Check Vmware.log for virtual machine logs, and /var/log/hostd.log of the source host to see the read the error.

Performing Storage vMotion process required time to open, close, and process disks during the final copy phase. Sometimes it face timeout issue beacuase of many reasons i;e overhead, latency on disk.

Default timeout is 100 seconds to perform these tasks which may not be enough if there is some latency or overhead on disk. We can change this timeout value by modifying switchover time.

There are different way to modify it. Either change it through *.vmx configuration file, or add fsr.maxSwitchoverSeconds in virtual machine configuration. Please note that making configuration changes required downtime of Virtual machine.

Follow below steps to fix this isssue:-

  • Open Virtual Center through vSphere Client.
  • Search for Virtual Machine in Inventory.
  • Make sure that it's in Power down state.
  • Select Virtual Machine , Right Click and Select Edit Settings.
  • Go to Option tab.
  • Select Advance Tab and go to General Section.
  • Click on Right bottom Configuration Parameters. (Image#1)
  • Click on Add Row. (Image#2)
  • In Name field, enter below value.
    • fsr.maxSwitchoverSeconds
  • Enter Time out value (ex; 150) in Value field. (Image#3)
  • Click OK and Power on the Virtual Machine.
  • Perform Storage vMotion, it should fix the issue.


 Image#1


 Image#2


 Image#3

These steps should fix the issue. Enjoy reading. :)


Thanks for visiting here. Share this article if you found it useful.
Join Facebook Group https://www.facebook.com/groups/VMwareInsight/
Like Facebook Page https://www.facebook.com/VMwareInsight/
Connect to twitter https://twitter.com/VMwareInsight
Share this on Social Media

About the Author

Pranay Jha
Pranay Jha
Founder, Contributer VMwareInsight.com
Follow me

facebook linkedin twitter G+ VMTN

My name is Pranay Jha, working in IBM as Technical Solution Architect for Virtualization platform. I have been working in IT for near around 10 years. Passionate to get involved as an Independent blogger for my blog http://vmwareinsight.com. I am VMware vExpert 2016/2017, VCAP5-DCD/DCA, VCP5-DCV, VCA-Cloud, VCE-CIA, MCSE, MCITP, MCSA(Messaging). For any query or suggestion, please connect me at pranay1988jha@gmail.com. Thanks for visiting here.

 
Please SignUp/Login to comment...

Or comment as anonymous...
* Name
* Email ID
Comment
 
Sponsors
 
 
 
 
 
Facebook Likes