nerdexam
Broadcom-VMware

VCP550 · Question #92

A VMware administrator determines that a low priority virtual machine is negatively affecting the disk I/O performance of a higher priority virtual machine. The virtual machines are hosted on the same

The correct answer is A. Increase the disk share value for the high priority VM.. When two VMs on the same datastore and host compete for disk I/O, disk shares determine how available I/O bandwidth is proportionally allocated. Increasing shares for the high priority VM gives it a larger fraction of I/O during contention.

Configure and Administer vSphere Storage

Question

A VMware administrator determines that a low priority virtual machine is negatively affecting the disk I/O performance of a higher priority virtual machine. The virtual machines are hosted on the same datastore presented to the same ESXi host. Which configuration option should the VMware administrator use to resolve this issue?

Options

  • AIncrease the disk share value for the high priority VM.
  • BMigrate the low priority VM to another ESXi host.
  • CCreate a Storage Profile for each priority level.
  • DEnable vSphere APIs for Array Integration (VAAI).

How the community answered

(27 responses)
  • A
    74% (20)
  • B
    4% (1)
  • C
    15% (4)
  • D
    7% (2)

Why each option

When two VMs on the same datastore and host compete for disk I/O, disk shares determine how available I/O bandwidth is proportionally allocated. Increasing shares for the high priority VM gives it a larger fraction of I/O during contention.

AIncrease the disk share value for the high priority VM.Correct

Disk shares in vSphere set the relative priority for I/O access when contention exists on the same datastore and host. By increasing the share value assigned to the high priority VM, the ESXi scheduler allocates a proportionally larger portion of available I/O operations per second to it compared to the low priority VM, directly resolving the performance impact during periods of contention.

BMigrate the low priority VM to another ESXi host.

Migrating the low priority VM to another host would resolve the contention only if the datastore is also different or exclusively accessible - if both hosts share the same datastore, I/O contention at the storage layer can still occur.

CCreate a Storage Profile for each priority level.

Storage Profiles (VM Storage Policies) are used to match VMs to datastores based on capabilities such as replication or encryption, not to arbitrate I/O priority between VMs sharing a datastore.

DEnable vSphere APIs for Array Integration (VAAI).

VAAI offloads specific storage operations like cloning and zeroing to the array to reduce host CPU overhead, but it does not provide per-VM I/O prioritization or resolve contention between competing workloads.

Concept tested: vSphere disk shares for storage I/O contention resolution

Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.resmgmt.doc/GUID-7B2D0A6B-3F5C-4A8E-9F1D-2C4B5E6A7D8F.html

Topics

#disk shares#storage I/O#resource contention#QoS

Community Discussion

No community discussion yet for this question.

Full VCP550 Practice