1) 2/9 10:02:03.187 434 PR: LUN is SR reserved by iqn.1998-01.com.vmware:esx1-24f2f443,00023D000001.
2/9 10:02:03.187 434 PR: Std: Session 0x10, ScsiOp 0x2A - Reservation conflict.
2/9 10:04:07.140 434 PR: LUN is SR reserved by iqn.1998-01.com.vmware:esx1-24f2f443,00023D000001.
2/9 10:04:07.140 434 PR: Std: Session 0x10, ScsiOp 0x28 - Reservation conflict.
---
I assume this is related to a reserve/release issue with VMWare ESX? Basically I have heaps of these logged, usually when trying to create a guest OS ...
Linux guests get to checking package dependencies and just stop ... don't crash, but don't do anything either, I haven't looked into this further as windows guests do the same thing (sort of) On reboot from the text install to the GUI they sit there indefinitely with 33 mins remaining, again, they don't crash but don't get any further.
Strangely though, If I set up a guest on the local ESX vmfs disk then migrate the storage to the iSCSI volume, they work fine????
I am using IBV disks located on an Apple XServe RAID and directly connected to the StarWind server by FC. I tried Device Passthrough but this didn't work at all, i.e the ESX hosts did not see any available LUN's
---
2) When creating any Image based disk, if I try and specify a target name, the creation process fails every time with "Device Test Failed" Leaving the Target Name blank works fine, but, isn't an ideal situation as I have a bunch of obscure disks.
Running all of this on an Intel based server, 4GB RAM, 4x PRO/1000 NIC's setup as a SLA Team.
---
So yea, I'm confused! Thanks for any pointers some of you may be able to give!
