Converting a Win XP image to use LSI and not BusLogic

[Fulcrum72]

Is there a way inside of VMware Converter to make the destination virtual disks use an LSI controller as opposed to the BusLogic controller?

The situation that I'm in is that I've created a "template" image of Windows XP, but I accidentially used an IDE disk instead of a SCSI disk, so there isn't a way to directly import into ESX. Since I had VM converter, I'd thought I'd try that method, and although it imported the file successfully, it is using the BusLogic SCSI controller. I've changed the controller to LSI, but then the VM won't boot (inaccessible boot device). If I switch it back to buslogic, it works fine, though.

[admin]

Converter will use the SCSI controller that is defaulted by what the VMware platform creates. For XP, the default is BusLogic and the VMware SCSI driver.

[oreeh]

Try the following

Add a second disk to the VM which uses the lsilogic controller (this will add the controller to the VM too)

Boot the VM and install the LSI driver.

Shut down the VM and remove the second disk

Modify the first disk (make a backup first) to point it to the LSI

[Fulcrum72]

At the risk of sounding stupid, how do you do that?

I cannot add any additional SCSI controllers; it says that "There are no non-disk SCSI devices available on the host".

[oreeh]

Create a VM with a small disk using the lsilogic controller.

Point your existing VM to use this additional disk.

Another way is to manually add the lsilogic controller to the vmx-file

scsi1.virtualDev = "lsilogic"

[Fulcrum72]

I see now what I did wrong...

My problem was that I was adding another harddrive to the same controller -- that is, scsi0:1. What I should have done was add an additional drive on a different controller -- scsi1:1. When I did that, it added an additional SCSI controller just like everyone said it would.

Thanks for your help!