VMotion fails at 14% and the error:timed out (VM migration to 14% cannot continue)

I am here the environment is VMware vsphere ESXI 5.1.0 + vCenter 5,ha environment has always been normal, hot migration is available.

In a maintenance time, after restarting an esxi, found that the virtual machine can not be hot migration, has stopped at 14%, but the cold migration is OK, and the HA environment is not prompt is not normal, and the environment Hint Vmotion network hints have a problem, check again, found vmotion environment as before, And the Vmotion network has been rebuilt.

The following are the questions and logs of the error:

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/56/CD/wKioL1SOhjfB4NkkAAB69M1KuJo928.jpg "style=" float: none; "title=" 1.jpg "alt=" Wkiol1sohjfb4nkkaab69m1kujo928.jpg "/>

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/56/CF/wKiom1SOhZqSoZ4RAAB96C7q1ZE141.jpg "style=" float: none; "title=" 2.jpg "alt=" Wkiom1sohzqsoz4raab96c7q1ze141.jpg "/>

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/56/CD/wKioL1SOhjrQQ6PcAACsORUc0I8575.jpg "style=" float: none; "title=" 3.jpg "alt=" Wkiol1sohjrqq6pcaacsoruc0i8575.jpg "/>

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/56/CD/wKioL1SOhkHgfC5uAAHgfnBUCqE961.jpg "style=" float: none; "title=" 4.jpg "alt=" Wkiol1sohkhgfc5uaahgfnbucqe961.jpg "/>

The vmotionmigrations failed because the ESX hosts were not able to connect over thevmotion network. Check the VMotion network settings and physical networkconfiguration.

VMotion migration[169297471:1416318623171614] Failed to create a connection with remote Host<x.x.x.x>: The ESX hosts Failed to connect over the VMotion network

MIGRATION[169297471:1416318623171614] Failed to connect to remote host<x.x.x.x> from host <y.y.y.y>: Timeout

The VMotion failedbecause the destination host did not receive data from the source host on the Thevmotion network. Please check your vMotion network settings and physical networkconfiguration and ensure they is correct.

Error and prompt as above, multiple hot migration is stopped at 14%, then failed, cold migration normal, prompting Vmotion network can not connect, package time out, but re-verify ha, normal.

So Google, there are case mentions Vmotion network and other kernel network can not be in the same network segment, and the phenomenon is the same as my case.

Due to customer requirements to minimize the use of the network segment, so the previous Vmotion network and MANAGEMWNT network are all in the same network segment, but after the creation of the normal, sudden occurrence of such conditions.

So with the customer communication given a new network, re-establish the new network segment Vmotion Network, again verify that ha, is still normal, but again use the heat migration, passed, and other functions are normal.

At this point, can be basically judged as a network problem, so in the future do not save the network segment, all the kernel network isolated separately. It is recommended that management, VMotion, VMS, and IP San networks should be separated by VLANs to avoid this problem, and that if you catch the host down, the virtual machine cannot be migrated.

This article is from the "Heavenly Soul Eternal" blog, please be sure to keep this source http://tianhunyongheng.blog.51cto.com/1446947/1590105

VMotion fails at 14% and the error:timed out (VM migration to 14% cannot continue)