Hyper-V R2. I know best practices say to give Hyper-V and all its guests separate spindles, but that gets costly pretty quickly.

What are your thoughts on running Hyper-V plus one domain controller and one member server on a single 2 disk RAID1 with 10K SAS drives? No application-level data will be on the array. The server will have an abundance of memory for this task.


If you aren't putting anything on those disks but the OSs that shouldn't be a problem. Just keep in mind that if you boot both VMs at the same time performance will tank for the host, and the VMs will take a long time to boot.

| improve this answer | |

The management OS won't need much I/O once it's running, except when you start or stop VMs, take snapshots, etc. Give as much memory as you can to the guest OSes and they won't need as much I/O as they otherwise would.

Your major problem will be that there won't be much separation between the needs of one workload and the needs of another. Hyper-V will attempt to ensure that every guest OS gets fair time on the drive array. But that still won't ensure that performance is truly sufficient.

I'm not sure which recommendation you're siting. But note that the most common production Hyper-V configuration (with Windows Server 2008 R2) involves sharing a single LUN from some storage array with multiple hosts and putting all the VMs in the cluster on that shared LUN. So clearly separate spindles for each guest aren't required. What is required is sufficient IOPS for your workloads.

| improve this answer | |
  • Thanks. I've been reading so much about different hypervisors that I may be getting some wires crossed. It doesn't help that in Hyper-V VMs seem to be referred to as partitions. :) – Boden Jan 27 '10 at 19:20

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.