Storage policy IOPS limits are not updated upon virtual machine creation from template

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

This article describes an issue where IOPS limit settings are not correctly applied when creating a virtual machine with IOPS limits under the following conditions.

The IOPS limit is not updated in the following case:

・This occurs when you switch to a storage policy with IOPS limits while running the wizard to create a virtual machine from a template.

The throughputCap (IOPS Limit) setting in the virtual machine's .vmx file is configured using the throughputCap value from the VM template.

sched.scsi0:0.throughputCap = "###"

The storage policy name displayed under VM storage policy in the Hard disk # section of the virtual machine's Edit Settings in the vSphere Client will be changed.
However, the virtual machine operates using the IOPS limit value originally specified in the template.

Environment

VMware ESXi 8.0

VMware vCenter Server 8.0

Cause

Even if the storage policy is changed during the wizard for creating a virtual machine from a template, the virtual machine inherits the template's ThroughputCap.

Resolution

This issue will be resolved vCenter Server in a future release.

The workaround is as follows:
1. Log in to the vSphere Client.
2. Select the virtual machine for which the IOPS limit was not updated.
3. Click Actions > Edit Settings > Hard Disk # > VM storage Policy
4. Change the virtual machine storage policy for the hard disk to match the policy specified in the template.
5. Click OK.
6. Click Actions > Edit Settings again.
7. Revert the virtual machine storage policy for the hard disk to its original setting.

Additional Information

Japanese Version : テンプレートから作成した仮想マシンでストレージポリシーのIOPS制限の値が更新されない