Limiting the number of concurrent vMotions

[vsalimgareev]

Hello everyone.

We have installed vSphere Server 6.5 on Windows Server 2016.

We need change maximum number of concurrent vMotions: we need only one simultaneous vMotion.

For vSphere server 5.0 we uses this guide: Limiting the number of concurrent vMotions - frankdenneman.nl​, but now it not work

How can we limit the number of concurrent vMotions?
Thanks in advance for answers

[hussainbte · Accepted solution]

Can you try in vCenter advanced configurations

<ResourceManager>

<maxCostPerHost>4</maxCostPerHost>

</ResourceManager>

[vsalimgareev]

Does not work. Migrations continue to go simultaneously. What other options are available to solve our problem? Maybe I incorrectly indicated the value in vCenter advanced configurations?

[Finikiez]

AFAIK these advanced parameters are not officially supported, so there's no guarantee that they will work.

Probably the best option here is to open a technical SR with VMware support.

[hussainbte]

The setting says it is per host value.. are you sure the simultaneous vMotions are on separate hosts or on the same ESXi.

I will continue to look to find some more info on this

[hussainbte]

Just a reminder.. this requires vCenter service restart after enabling.. im sure you have done that

[vsalimgareev]

I guess I made the wrong request.
We have a HA cluster configured. We need to automatically migrate between hosts only one VM at a time.
After the changes, we restart the vCenter service.

[vsalimgareev]

Everything is working. Set the value of "maxCostPerHost" to 3. Migrations can start simultaneously, but then move one by one
thanks for the help