ID #1052

SCSI-controller : the parameters

SCSI-controllers only use a few parameters.
The present parameter is used as the main-switch - if you set it to "false" all other sub-parameters will be ignored.
To add a SCSI-controller you must enable the main-switch and set the virtualDev - parameter.
VMware sets the pciSlotNumber parameter automatically on first start - do not change the value unless you need something very special !


 

scsi*.present

All current VMware versions support upto 4 SCSI-controllers per VM.
A default VM is created with one controller.

scsi0.present = "true"
scsi1.present = "false"
scsi2.present = "false"
scsi3.present = "false"

The last 3 lines are "silent defaults" - that means they are not printed in the vmx-file.
To add a second, third or fourth controller create the line yourself and set the value to "true"


 

scsi*.virtualDev

Depending on the VMware versions and the virtual hardware version SCSI-controllers can use different types.

scsi0.virtualDev = "buslogic"
That is the "silent default" - if you do not find this parameter in your vmx-file it means that the old BUSLOGIC virtual device is used. This is a good choice for old guests.
For modern 64bit guests this device is no longer supported.
Guests can use this device if they have the vmscsi-driver installed.


scsi0.virtualDev = "lsilogic"
This is a more modern device then the old BUSLOGIC - on a typical Windows VM using this device it is detected as
LSI Logic Ultra 320 controller.
This is a good choice for Windows 2003 and most modern Linux guests as they have buildin drivers for this device.
This device is connected to a regular PCI-slot.

scsi0.virtualDev = "lsisas1068"
This new controller is only available with virtual hardware 7
it is a good choice for Windows 7 and 2008 R2
On Windows 7 this controller is detected as
LSI Adapter SAS 3000 series, 8 port with 1068
This device is connected to a  PCI- Express slot.

 

scsi0.virtualDev = "pvscsi"
This new controller is only available with virtual hardware 7
It is only supported for this guests.

  • Windows Server 2008
  • Windows Server 2003
  • Red Hat Enterprise Linux (RHEL) 5

This device is recommended for data-disks with heavy loads only.
Typically you would use it as scsi1 scsi2 or scsi3.
booting from such a device is not supported but possible.
If you need the F6 boot floppies read http://communities.vmware.com/thread/211243

This virtual device is only supported on ESX(i) but it also works on Workstation


 

scsi0.pciSlotNumber

This parameter is only used in virtual hardware 7 - do NOT set it in older versions.

scsi0.pciSlotNumber = "16"
This is typically used for the first SCSI-controller of a VM.
Do NOT change this !

scsi0.pciSlotNumber = "160"
This is typically used for a LSI-SAS controller. The high number says that it uses an PCI-express slot.

scsi0.pciSlotNumber = "-1"
This special value means that the PCI-slot has not been assigned yet - it will be changed automatically on next boot of the VM

 

 


 

scsi0.sasWWID = "50 05 05 68 ec 19 c8 b0"

This parameter is only used by the LSI-SAS controller - it is configured automatically - do net set it manually.
In doubt skip it - it will be recreated on next boot of the VM.

 

 

 


 

advanced ...



scsi0.returnBusyOnNoConnectStatus
scsi0.sharedBus
scsi0.unsafeReordering

Tags: scsi, scsi-controller, vmx

Related entries:

You can comment this FAQ

Comment of Ted:
How are SSDs enabled and disabled in the .vmx file in a Windows 8.1 x32 virtual machine?
Added at: 2014-11-12 23:31