You can change the default storage pool path via Configuration -> Advanced Settings -> Storage Pool

Don't feel bad please.
Such minors are important because they confuse users without rich experience in iSCSI, high availability, multipathing.
Feel free and let us know about any things in StarWind you would like to see implemented in the different way. And we'll try to implement/fix it.

:) I guess it is a copy-paste localization error. This is the last wizard step which shows you what IP addresses and target names you should use on the iSCSI initiator side to connect the recently created multi-node (clustered) device. It should be "Use the following addresses to connect $devic...

In magabytes. We'll fix it ASAP.

Do you mean it is just necessary to leave the current domain and join the new one for these two machines?

What about the underlaying storage? I mean the location on which StarWind images are stored. Is it capable to show better numbers than 1Gb/s (128MB/s) locally?

Please re-download StarWind v8 build and update your current one. The issue should be solved.

Also make sure that 3260 and 3261 tcp ports are free on that machine.
You can check it launching cmd.exe and running "netstat -abn" command.

Three steps to add the device:

StarWind-VM feeds the storage for the pair of nested ESXi hosts. Yes, this is a non-production scenario. Update from me. I have the installation ISO. As soon as it: 1) happens for MS iSCSI target too and 2) does not happen for non-nested hypervisor environments; we are planing to research such scena...

Thanks for keeping us updated.

Developers are working on this. I'll let you know as soon as the improvements are available.

I changed cache size in the cfg file, but starwind still showes 128MB of Cache.

Did you restart StarWindService after editing the config file?

It appears on the systems with >16 CPUs. Is this your case?

You should connect it twice:
1) specifying initiator and target IP addresses from the x.x.212.x subnet
2) specifying initiator and target IP addresses from the x.x.213.x subnet

also make sure that you have Windows Mutipath functionality enabled for iSCSI devices.