Manage VMware Paravirtual SCSI Controller with the vss-cli
- JM Lopez
Analytics
According to VMware, there are two main reasons to deploy a virtual machine with the Paravirtual SCSI controller:
PVSCSI adapters are high-performance storage adapters that can result in greater throughput and lower CPU utilization. PVSCSI adapters are best for environments, especially SAN environments, where hardware or applications drive a very high amount of I/O throughput. The VMware PVSCSI adapter driver is also compatible with the Windows Storport storage driver. PVSCSI adapters are not suitable for DAS environments. VMware Paravirtual SCSI adapters are high-performance storage adapters that can result in greater throughput and lower CPU utilization. [1]
The PVSCSI adapter offers a significant reduction in CPU utilization as well as potentially increased throughput compared to the default virtual storage adapters, and is thus the best choice for environments with very I/O-intensive guest applications. [2]
Changing VMware Storage Controller to Paravirtual for CentOS 7
This tutorial contain step by step guidance to change the Virtual Storage Controller from LSI Logic Parallel (SCSI controller 0) to VMware Paravirtual for a CentOS 7 based Virtual Machine that is running on the ITS Private Cloud.
Create a Virtual Machine Snapshot:
vss-cli --wait compute vm set <name-or-vm-id> snapshot mk -d "lsi logic to paravirtual" -l 72More information Manage virtual machine snapshots with the vss-cli.
Power Off the virtual machine:
vss-cli --wait compute vm set <vm-name-or-vm-id> state shutdownAdd a temporary VMware Paravirtual Controller to the Virtual Machine.
vss-cli --wait compute vm set <vm-name-or-vm-id> controller scsi mk --scsi paravirtualVerify that a new SCSI controller has been created.
Power On the virtual machine.
Login and promote your account to have root level permission.
Rebuild the initial
ramdiskimage:
Power Off or shutdown the virtual machine:
Update scsi controller 0 to type Paravirtual:
Check whether the update executed successfully:
Remove temporary SCSI controller
Power On the virtual machine:
Verify everything is working well.
(Optional) Remove Virtual Machine snapshot:
More information Manage virtual machine snapshots with the vss-cli.
Changing VMware Storage Controller to Paravirtual for Windows
This tutorial contain step by step guidance to change the Virtual Storage Controller from LSI Logic SAS (SCSI controller 0) to VMware Paravirtual for a Microsoft Windows Server 2016 or later (64-bit) based Virtual Machine running on the ITS Private Cloud [3].
Ensure machine is patched and latest VMware Tools installed and running.
If VMware Tools is ever removed from the system, it will not boot.
Create a Virtual Machine Snapshot:
Shutdown/Power Off the virtual machine:
Add a temporary VMware Paravirtual Controller to the Virtual Machine.
Verify that a new SCSI controller has been created.
Power On the virtual machine.
Log Onto windows machine to verify whether the VMware Paravirtual driver get installed using Device Manager > Controllers > PVSCSI device.
Shutdown/Power Off the virtual machine:
Update scsi controller 0 to type Paravirtual:
Check whether the update executed successfully:
Power On the virtual machine.
Log Onto windows machine to verify boot and driver changed, in device manager you will now see 2 - controllers PVSCSI device.
Shutdown/Power Off the virtual machine:
Remove temporary SCSI controller
Power On the virtual machine.
Log Onto windows machine verify boot and removal of secondary scsi controller using the device manager.
(Optional) Remove Virtual Machine snapshot:
Contributed by Joe Bate.
Related content
University of Toronto - Since 1827