Yesterday I was at a customer who complained his VMware ESXi 5.0 Update 1 environment was unable to vMotion between servers.
He saw two different error messages:
A general system error occurred: Failed to initialize migration at source. Error 0xbad0060. Necessary module isn’t loaded
– and –
A general system error occurred: The VMotion failed because the ESX hosts were not able to connect over the VMotion network. Please check your VMotion network settings and physical network configuration.
First I verified that the servers were actually able to ping each other on the vMotion VMkernel IP’s. This worked fine so the error had to be found elsewhere.
A Google search revealed others with the “0xbad0060. Necessary module isn’t loaded” message, but they were related to Storage vMotion – not vMotion.
Further research turned up VMware Knowledge Base article 2013128.
#1 From command line (for example via SSH) execute “esxcli system module load -m migrate”
#2 From vCenter open the configuration tab of the ESXi host and click to Software -> Advanced Settings. Make sure Migrate.Enabled is set to 1.
#3 The KB article does not mention it is required to reboot the ESXi host, but for me it did not work until I rebooted the ESXi host.
After following the steps mentioned on each of the customers three ESXi hosts vMotion started to work again.
If this helped you please post a comment 🙂
Incoming search terms:
- the vmotion migrations failed because the esx hosts were not able to connect over the vmotion network check the vmotion network settings and physical network configuration
- vmotion fails at 14
- A general system error occurred: The vMotion migrations failed because the ESX hosts were not able to connect over the vMotion network Check the vMotion network settings and physical network configuration