I have successfully converted 5 windows 2003 STD physical server into VM. but their SCSI controller are all BUSlogic. i know LSIlogic have better performance, so i want to change it to LSIlogic in Editing VM menu, is this safe or cause data corrupt? or is there any other method to do this?
You'll be fine to make the change.
If you have any issues, you can always switch back again.
As you'll know the buslgic device is legacy and Windows 2003 will have the drivers for lsilogic, so it will detect the switch.
you are correct, thanks. the VM works fine when i change the SCSI controller to LSIlogic.
the real change behind the scene is that the disk descriptor file changed:
from:
ddb.adapterType = "buslogic"
to
ddb.adapterType = "lsilogic"
Make the switch in the VM configuration settings. Next time you power on the VM, VMware will detect that the virtual controller does not match that of its connected disk(s) (descriptor), and would you like it to convert the disk(s) to an LSI Logic type. Yes.
Hi jasonboche, i'm a new user! How can i modify the .vmx to change the scsi controller type to LSIlogic? How can i see the type of .vmdk that has been created?
Thank you so much!
By default Windows 2003 VMs should use the LSI Logic controller type. Normally this is what is set when performing a conversion. I have seen cases where a BusLogic controller appears instead, and in those cases the VM may not boot up properly-- it will result in a STOP error blue screen-- unless the controller is changed to LSI Logic.
Yes, our old friend 0x0000007b inaccessible boot device...
I never see a converted win2k3 VM use lsilogic by default, so it's a tedious work for me to change it one by one, if VMware will auto this work instead of manual modification, it will be better.