Hi Tore,
Option 1: Clone from a template or base VM
If you have a base VM or template that already uses LSI Logic SAS, then creating new VMs from that template will preserve the same controller type.
New-VM -Name "MyNewVM" -Template "Base-LSI-Template" -Datastore "Datastore01"
→ This is the simplest and cleanest way to keep the LSI controller without post-modification.
Option 2: Use New-VM with -DiskStorageFormat None, then add your own
You can create the VM without a disk, then manually attach an LSI Logic SAS controller and disk.
Example:
# Create VM without a disk
$vm = New-VM -Name "MyNewVM" -ResourcePool "Resources" -Datastore "Datastore01" -DiskStorageFormat None
# Add LSI Logic SAS controller
New-ScsiController -VM $vm -Type "LSILogicSAS"
# Add a new virtual disk on that controller
New-HardDisk -VM $vm -CapacityGB 60 -Controller (Get-ScsiController -VM $vm | where {$_.Type -eq "LSILogicSAS"})
→ This avoids the "create-then-delete" mess. You're simply creating the VM with no disk, then explicitly defining the correct controller and disk.
-------------------------------------------
Original Message:
Sent: Oct 10, 2025 07:59 PM
From: Tore
Subject: Create vmguest with LSI controller
Hi.
Since upgrading to vSphere8, the New-VM Powercli command has started to create vms with VMware paravirtual controller by default.
Before upgrade to vSphere8, LSI Logic SAS was the default disk controller.
It seems like the only way get out of this mess, is to have the New-VM script first create the with VMware Paravirtual controller, then delete disk and controller, and then set the new LSI Logic controller and the create the disk.
Am I right or wrong?
------------------------------
Best Regards,
Tore
------------------------------