topic Re: vMotion and maximum latency of 150 msec in VMware vSphere™ Discussions

vMotion and maximum latency of 150 msec

zeebahi — Wed, 09 Dec 2020 01:04:04 GMT

Hi everybody,

Based on the link below, we can have maximum 115 msec round trip time for vMotion.

Out of curiosity, what happens if we violate this limit?

Thanks and have a good day!!

##########################################################

https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-3B41119A-1276-404B-8BFB-A32409052449.html#:~:text=If%20you%20have%20the%20proper,vMotion%20migrations%20is%20150%20milliseconds.

If you have the proper license applied to your environment, you can perform reliable migrations between hosts that are separated by high network round-trip latency times. The maximum supported network round-trip time for vMotion migrations is 150 milliseconds. This round-trip time lets you migrate virtual machines to another geographical location at a longer distance.

Re: vMotion and maximum latency of 150 msec

daphnissov — Wed, 09 Dec 2020 01:16:10 GMT

You get failures and very odd problems.

Re: vMotion and maximum latency of 150 msec

scott28tt — Wed, 09 Dec 2020 06:16:20 GMT

@zeebahi

Moderator: Moved to vSphere Discussions, not a HA or FT question.

Re: vMotion and maximum latency of 150 msec

depping — Wed, 09 Dec 2020 07:45:36 GMT

If you are fortunate the vMotion will complete but the VM will just run extremely slow. If you are unfortunate the vmotion will be cancelled half way down. Either way, we don't support this.