If you are planning to deploy your Exchange Server 2010 Database Availability Group on VMware environment, there is a certain misunderstanding about the configuration.
While the use of database availability groups on top of hypervisor based clustering is not a formerly (sic) supported configuration, internal VMware tests have shown that the two technologies can co-exist and can be a viable solution to ensure maximum recoverability in the case of a host failure
Microsoft doesn’t support combining Exchange high availability solutions (database availability groups (DAGs)) with hypervisor-based clustering, high availability, or migration solutions that will move or automatically failover mailbox servers that are members of a DAG between clustered root servers. DAGs are supported in hardware virtualization environments provided that the virtualization environment doesn’t employ clustered root servers, or the clustered root servers have been configured to never failover or automatically move mailbox servers that are members of a DAG to another root server.
That means, VMware says that it isn’t supported but we think you are ok.
But Microsoft says, this type of configuration is not supported by us.
So be careful about planning Exchange if your environment contains clustered virtualization root servers.