Configure VM with paravirtual adapter for better queue depth

From Notes_Wiki
Revision as of 08:42, 7 April 2022 by Saurabh (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Home > VMWare platform > VMWare vSphere or ESXi > Configure VM with paravirtual adapter for better queue depth

In case of:

  • Database VMs OR
  • Any other VMs expecting high I/O OR
  • VMs experiencing high OS queue length and high latency (Visible on vrops)

it makes sense to try to change its storage controller from default "LSI Logic SAS" or "LSI Logic Parallel" to "VMWare Paravirtual" using below steps:

  1. Validate that VMWare tools are installed on the VM so that VM can recognize virtual devices such as "VMWare paravirtual" storage controller or vmxnet3 NIC (Network adapter)
  2. Shutdown the VM after taking required downtime.
  3. Go to edit settings and add storage controller. A VM can have upto four storage controller. Add more controllers based on no. of disks or based on I/O required per disk.
    Note that a disk can be managed only by one controller at a time. Hence there is no point having more controllers then disk
  4. Change the disk controller from existing controller to one or more paravirtual controllers added
  5. Save the configuration
  6. Boot the VM and validate it is working as expected.




Home > VMWare platform > VMWare vSphere or ESXi > Configure VM with paravirtual adapter for better queue depth