vMotion limitations in VMware vSphere 8

There are limits on the number of simultaneous virtual machine migration and provisioning operations that can occur on each host, network, and datastore in vCenter. This article gives you more insight into their numbers.

let's have a look at a basic understanding of vMotion. In vSphere, each operation, such as migration with vMotion or cloning a virtual machine, is assigned a resource cost. Each host, datastore, or network resource, has a maximum cost that it can support at any one time. Any new migration or provisioning operation that causes a resource to exceed its maximum cost does not proceed immediately but is queued until other operations complete and release resources.

Network Limits

Network limits depend on the version of ESXi and the network type. All migrations with vMotion have a network resource cost of 1.

Network Limits for Migration with vMotion

Datastore Limits

Migration with Storage vMotion has a resource cost of 16 against the source datastore and 16 against the destination datastore.

Host Limits

Host limits apply to migrations with vMotion, Storage vMotion, and other provisioning operations such as cloning, deployment, and cold migration. All hosts have a maximum cost per host of 8.

For example, on an ESXi 7.0 host, you can perform 2 Storage vMotion operations, or 1 Storage vMotion and 4 vMotion operations.

For more understanding, please go through with VMware Articles associated with vSphere 8 Version. For any queries, please feel free to email me.