True, definitely more a Microsoft question than StarWind, but I figured there would be plenty of similar size admins here - moving from 2 or 3 host standalone Hyper-V or VMware Essentials to 2 or 3 node VSAN Hyper-V clusters, without the big tools like SCVMM. In our case I usually know when the powe...

We've recently switched our prod cluster from VMware to Hyper-V and I would like to know what everyone else does to handle VM startup after a major power failure. With both VMware and standalone Hyper-V I could set VM startup sequence/delay, and it was just part of my process that if I moved the VM ...

Upping the testing VM to 8 vCPU didn't make any difference. The starwind scheduler for sdb was set to cfq, I tried both noop and deadline with no significant difference in either case. Just for kicks I also ran an iperf test against the iSCSI NIC on the starwind server to verify it was indeed capabl...

The VMs I'm using to test are 4 vCPU, 8GB RAM, LSI SAS, 100GB Thick Eager Zeroed, NTFS I've tested now with 2 and 3 VMs and while there are overall improvements with qty, the results are still consistent with the original tests. Read and write are pretty much the same so I'm just showing read speeds...

So I'm testing this using the CentOS appliances on vSphere and right away I'm hitting a significant disk penalty with either the extra VM layer or the iSCSI connection. Using a Windows VM and diskspd, with one disk on the underlying VMFS datastore I get read and write each averaging 240 MiB/s. A sec...