vm-scsi-2.6.29.1.tcz was just a subset of the scsi drivers (BusLogic and LSI Logic) for 2.x. The scsi-2.6.33.3-tinycore.tcz extension provides that functionality for 3.x, so I've not released a new vm-scsi extension.
To duplicate your results, I tested the four SCSI controllers available with VMware ESXi 4.1:
1) BusLogic Parallel (works)
2) LSI Logic Parallel (failed)
3) LSI Logic SAS (failed)
4) VMware Paravirtual (works)
The default for Linux is typically #2, so that explains your failure. In order to fix LSI Logic, I think curaga will need to update the extension to include the 2.6.33.3 version of the files listed in the vm-scsi extension:
kernel/drivers/message/fusion/mptspi.ko.gz
kernel/drivers/message/fusion/mptscsih.ko.gz
kernel/drivers/message/fusion/mptsas.ko.gz
kernel/drivers/message/fusion/mptfc.ko.gz
kernel/drivers/message/fusion/mptbase.ko.gz
As an immediate solution, you can change your scsi controller to either BusLogic Parallel or VMware Paravirtual. Check the performance on each and go with what works best.