Storage I/O control settings from a storage policy are not shown correctly in vSphere Client and ESXi host client when creating a new virtual disk or migrating an existing one to a different datastore

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• When you create a new virtual machine with a hard disk that is configured to use a storage policy with host-based IOPS settings enabled, both vSphere Client and ESXi host client do not display the correct values for any IOPS limit, reservation or shares configured in the policy. 
• Similarly, when adding a new virtual hard disk with a storage policy with host-based IOPS settings, these settings are not shown correct in both vSphere Client and ESXi host client
• When you Storage vMotion a VM under Storage IO Control (SIOC), the configured parameters for disks are not shown when the VM has moved to the destination. The behaviour is the same if a VM Storage Policy was applied.
• After creating a storage policy for Storage IO control and assigning it to a VM the values (IOPS limit, IOPS shares) are not updated for the disks of this VM in both clients, but instead just the default values are displayed

Environment

VMware vCenter Server 7.0.x
VMware vCenter Server 8.0

Resolution

Currently there is no resolution. Please subscribe to this article to be updated about any changes to this.

Workaround:
Use the ESXi command shell to verify that the values have actually been correctly applied. To do this:

• connect to the ESXi per SSH
• run the following commands, while replacing <vm_name> with the correct display name of the virtual machine you want to confirm this for:

  # path=`find / -name "<vm_name>"`
  # vmkfstools --iofilterslist "$path/<vm_name>.vmdk"

Additional Information

Impact/Risks:
None, these values are correctly applied, this is a cosmetic issue in the vSphere Client UI and the ESXi host client UI