Hello,

Whether the shared disks are accessed via iSCSI within the VM or externally you will should still follow the instructions within http://www.vmware.com/pdf/vi3_35/esx_3/vi3_35_25_u1_mscs.pdf for the proper setup of your non-shared disk virtual hardware.


Best regards,
Edward L. Haletky
VMware Communities User Moderator
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354
As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

It's obviously been some time since your last posts... but I figured I would share some of my experiences with this. According to VMware, VM clustering (MSCS) with iSCSI is not a supported configuration. I have set this up in my test lab environment however, and it's working just fine. I presented the iSCSI LUNs to the clustered ESX hosts. Then added the volumes as raw device mappings to the VMs SCSI controllers that are set with SCSI bus sharing. This way the VMs don't require the Microsoft iSCSI client to function, they simply use the VMware LSI logic virtual controller as per normal. I would advise against trying to use an iSCSI client within the VM. The application we successfully clustered with this method was Microsoft SQL 2005.

Hope this helps!

For such configuration I had to use Starwind`s iSCSI possibilities. I was clustering MS SQL and Exchange servers, according to their manuals, everything was fine, and works great.

Using it for myself! Great tool! Really recommend it to you!