vCenter VM list view does not include overhead for thin provision VM's provision size when created on vSAN datastores

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• When creating a VM on vSAN with a reservation policy of 0 percent, which acts as a thin provisioned, it displays the currently allocated space for the VM but not the total amount of space the VM could consume if fully utilized.

• When creating a VM on vSAN with a reservation of 100 percent, which acts as a thick provisioned, the VM display the space allocation as if the VM was fully utilized. 

Environment

VMware vSphere ESXi 6.7
VMware vSphere ESXi 7.0.x

Resolution

This issue is fixed in 7.0U2c or higher.

• For ESXi/vCenter 70U2c or later, the VM provision size takes the policy overhead into consideration for VMs created on vSAN datastores.
• However, for VMs created on vSAN datastores prior to version 7.0U2c, the overhead is not calculated into the provisioned size.

Note : vSAN replication overhead relates to the mirror copy according to the set FTT (Failure To Tolerate). 
For example, a vmdk on vSAN with FTT1, if the disk claimed size is 10GB, vSAN will duplicate the vdisk to 20GB. 10 GB for the primary usage, the other 10GB to keep compliant with policy this is vSAN replication overhead.
Initially for versions before 7.0U2c, in the VM view, it does not take the replication overhead into consideration, thus, 10GB is listed in provision size. while after 7.0U2c, 20GB will be listed in provision size.