Basic vm workflow creates vm with SCSI controller type "LSI Logic Parallel"

[sajithru]

Hi All,

I have a blueprint to create virtual machines from the scratch using BasicVMWorkflow with specifying guest OS type at the beginning. However, all of the VMs created are using SCSI controller type LSI Logic Parallel.

This makes some of the guest OS types (ex: windows) unable to identify the hard disk during the OS installation. Since I am specifying guest OS type it should pick the appropriate SCSI controller type but somehow its not happening.

Apart from separately specifying the SCSI controller at provisioning stage how can I resolve this?

Thanks in advance.

-Sajith Rupasinghe.

[daphnissov]

You will need the VMware.SCSI.Type custom property with the value being one of either buslogic, lsilogic, lsilogicsas, pvscsi, or none. See the Custom Properties reference guide for more info.

[sajithru]

Yes it works but then it would be limited only to a particular OS type right. Windows need lsilogicsas but Linux need lsilogic. My blueprint is designed to deploy both types of VMs.

Can I change the value before provision from a VRO workflow and then pass it back to VRA?

[daphnissov]

Well, if I were you I'd just have them both use the pvscsi controller because that's the recommended type to begin with for optimal performance. It will require bootstrapping those drivers into the image that you're going to lay down because neither Windows nor Linux has those by default (if I'm not mistaken).

[rdaka]

How about day2 operations. vRA is adding Logic SAS by default. I want the controller to be Paravirtual