Exchange 2010 DAG and Hyper-v Cluster supportability statement - Supported but how

We all have been tought that Exchange 2010 DAG cannot be installed on a hyper-v Cluster or ESX Cluster (generally any hypervisor clustering), this is a correct statement but not entirely true.
the correct statement that Installing Exchange 2010 DAG is not supported on Hypervisor Clustering only when you confiure the VM that hosts the Exchange as highly available machine, thus you control the High availability of he VM using clustering.

if you Install Hyper-v or ESX clustering, you can Install Exchange 2010 DAG normally on a VM that is hosted on any single host of the Hypervisor cluster as long as this machine is not highly available from the Hypervisor point of view meaning that you cannot move it using live migration or Vmotion.
you can now install the DAG on your Hypervisor Cluster physical server normally, don't make the VM highly available, size the IOPs and Memory and you are fine.
Hope that this helps you in your virtualization and Exchange Project

Hyper-v Windows 2008 R2 read and write is very slow and copy operations is extremely slow

I was working on a Windows 2008 R2 Hyper-v Deployment, using 2 HP DL 380 G6 Servers with 16 GB of memory and HP MSA 2000, after setting up the hyper-v Cluster and Installed the VM I noticed that copy, read/write operations against the SAN is very slow, and boot time takes about 2-3 minutes to complete.
little troubleshooting led me to know where, HBA drivers where updated, everything is ok, more debugging led me to the following:
to fix this issue you will need to open the MSA 2000 web admin, go to manage, configuration, disks and go to read configuration as I recall and change the mode from standard to super sequential, once done everything worked fine and performance was as expected.

really tricky one.