How to create a Windows Server 2008 Cluster within Hyper-V using simulated iSCSI storage
February 22, 2008 – 10:00 amWindows Server 2008 failover clusters support Serial Attached SCSI (SAS), iSCSI and Fibre Channel disks as storage options. So, how would you go about setting up a virtual Windows Server 2008 test cluster using the new Hyper-V virtualisation product? The method I am about to outline is a little differnt to what you might be used to Virtual Server 2005. The following steps detail how I managed to setup a test cluster using simulated iSCSI storage. Before beginning it’s worth reviewing this article that outlines the storage options that are available to Hyper-V. By the end of this post you should have a simple two node cluster up and running using simulated iSCSI storage.
Tools for the job:
- A Windows Server 2008 server x64 server with the Hyper-V role enabled (I used a Dell Precision 390)
- One Windows Server 2008 VM to act as a Domain Controller (Clusters must be part of a domain)
- Two Windows Server 2008 VMs to act as Cluster Nodes
- One Windows Server 2003 SP2 VM (or you could use Windows Server 2008 in a Core install to maximise VM performance)
- iSCSI Target Software: I used Rocket Divisions StarWind product that is available as a 30 day eval and is reasonably priced
- iSCSI Initiator software (built into Windows Server 2008)
I wont go into how to create a VM but you can find more info from Virtual Guys weblog.
Before I began looking into the iSCSI simulated storage option for my cluster nodes I tried to expose a single VHD to each of my cluster nodes in the hopes that they would share it. I didnt get very far and was presented with the following error when powering on the VMs:

This error is by design (thanks Justin Zarb for point this out) as Windows Server 2008 Hyper-V does not support this sort of storage (see link above for Hyper-V storage options). The above error is simply a file system error as the VHD “is being used by another process” … should have spotted that
