Two weeks ago, I've posted a message about the Starwind iScsi software target.
And, thanks to Nautilus, I could test this software.
After deeper tests, I realize now that this software is not perfectly working fine with the latest release of ESX (3.0.2). No issues with 3.0.1.
And the Starwind technical support says that VMware has broken the iscsi support !!!
What to think about that ? Is it right that, actually, iScsi and 3.0.2 are not good friends ?!
On the 17th september, I've exchanged many e-mails with the Starwind technical support to try to understand why I was not able to launch any vm's.
The response of the boss is simple :
It's not StarWind being incompatible with the latest ESX, it's ESX iSCSI support being totally broken. Don't you think
these are quite different things to say? ?
I'm sorry for you being busy testing broken stuff. The only thing we can offer you - free NFR StarWind Professional
license so you could use it when VMware will fix their stuff.
Thank you and sorry
Anton A. Kolomyeysev
CEO, Rocket Division Software"
The 3.0.2 is up-to-date.
I'm also using the latest Starwind.exe I can download.
All is ok to install and configure the software, but when I'm creating a vm, ok, but, after, when I'm starting this vm to install - for example - a WinXP, WinXP tells me that he does not find any hdd.
For the Starwind technical support, it's "normal" and the only solution is to downgrade to 3.0.1 !!!
I am confused. So the ESX Host can see the iscsi target, you can create the VM on the target, you just can't install Windows onto the VM.
Once the Host sees the iscsi volume and writes vmfs to it, if it were an iscsi problems, you wouldn't be able to create the VM on it.
XP not finding a disk has absolutely nothing to do with the vmfs volume, but more to do with XP not having builtin drivers for XP. You should download the correct vmware scsi driver from vmware or even from lsilogic. Once you have the driver you can make a floppy image with winimage, attach it to the vm and press F6 at startup.
Good idea, Dave and Rumple.
I know the F6 procedure for traditional raid controllers.
But, with VMware, I've never used it because it's not usefull until there ! And I didn't think about it because the Starwind technical support was sure it's an ESX specific 3.0.2 issue...
I'll test that asap and I'll tell you the result.
Just for kicks have you tried using any other operating system but XP. Is XP the only guest giving you a headache?
I would try this drivers for the lsilogic as well