If the OS has been installed and running with Bus Logic and running fine with it,changing the SCSI controller would make it BSoD as the OS doesn't recognized the SCSI controller vHardware anymore.
During my first install, i use LSI Logic parallel for my Windows Server 2003 and it works fine, but for my Windows Server 2008 i use LSI logic SAS. and don't forget to install the VMWare tool once you've done with creating the VM.
You could try this:
1. Start the Server with BusLogic
2. Open Hardware from the Settings Menu
3. Choose to add new hardware (which is already installed)
4. Manual Choose Hardware -> SCSI&Raid Controller -> Vmware Inc. -> LSI Logic
5. After install shutdown Windows
6. Change SCSI Controller and start VM again
If this doesnt work, you can only make an repair install of windows 2003 to get the drivers in there.
I've tried to "pre-install" the drivers before I swapped the controller and it didn't work. I have found a way to edit the .vmx file so I now show a Bus Logic and an LSI Logic controller, but the LSI isn't showing up in the Device Manager. I wonder if I need to mount a disk to it. Any ideas how? Because these were physical machines and we converted them, they ended up with the BusLogic. I wouldn't have used them, but I wasn't given an option to use the LSI controller.
Yes it is quite annoying that when you do the P2V the default SCSI controller is the BusLogic one, however Windows 2003 has a built in driver for the LSI controller so therefore should just pick it up after changing the SCSI controller type in virtual machine properties. This was the case when we virtualized our datacenter (250+ P2V's). Since this is obviously not working in your case then the other thing you can do is to using Bart PE and add the Fix-VMSCSI (http://www.rtfm-ed.co.uk/?page_id=174) plugin in order to load the drivers into your Windows 2003 machine. This does two things at once: loads the LSI driver and modifies the registry of Windows to boot from it.
Yell if you need any further instructions otherwise I trust this helps.
Not sure if this is still a problem for you or not. But what I have done several times successfully is to add another scsi disk as SCSI ID 1:0 which will add a new scsi controller. It will pick busloigic be default, boot the vm let it see the deivce etc. shut it down and then change the secondary scsi controller to LSI, boot it up let it install the driver etc. once it's alll good, take it down again and switch the primary type to LSI, boo tit up and Viola!
you can now remove the temp harddrive and controller.
Also make sure you snapshot vm before hand as fallback...
I agree with Wade's solution. You can find a knowledge base article documenting the process here:
Scott Lowe also talked about using the same technique during the vSphere VM upgrade after upgrading to virtual hardware 7 and wanting to take advantage of the pvscsi controller for non-boot drives.