Server 2012 Storage Spaces and Shared Cluster Volumes

In this segment we create a cluster and share a CSV between the host servers.

[nopenottalib]

So, basically if you wanted to have two Windows running Hyper-V with fail-over clustering for the Hyper-V side of things, you could have their storage duplicated across two physical storage servers. This would be done by adding equal storage capacity to both servers (running Windows Server as well) and then creating an iSCSI target pointing to the internal storage on each of your two storage servers.
Then you would setup Hyper-V with fail-over clustering by pointing them to your iSCSI volume. After that, you'd then go on one of the storage servers and select the big data disk and do your shared cluster storage on that.
I guess what I'm confused about is why don't you set up the clustered storage BEFORE you setup the Hyper-V clustering? Wouldn't this be necessary so that when you create the iSCSI target, it's generating a single target that logically points to two identical storage servers? In essence, the Hyper-V servers would look at a logical IP address that actually points to your clustered storage (containing an iSCSI target) so that, from the perspective of the Hyper-V servers, there is only one single storage server they're dealing with.
Does that make sense?

*EDIT* - I wanted to clarify that I'm talking about 4 total Windows Server boxes here. Two for the Hyper-V cluster, and two for the clustered storage. The Hyper-V servers would only be serving the virtual servers while the storage servers would only be serving raw storage as a cluster to the Hyper-V servers.

[AskewTarantula]

Exactly what I was looking for, thanks! Probably should mention you are using workstation because esx or vmware server would probably have looked different.

[Garegin]

you are using VMware instead of hyper-v. heresy!