Feature lists don't mean much. In many cases you wont come close to the maximums each allow. We have both. (Hyper V 3 2012 and VMware 5.1). IMHO it comes down to how reliable and how resource intensive it is to manage each Hypervisor.
If its a stand alone host, with local storage Hyper V has the edge in my opinion (version 2012). It has live migration built in, Hyper V replica etc. These features work. Managing Hyper V on a stand alone host is simple. VMware on a stand alone host with local storage is also easy to mange. However moving a VM to another host takes downtime. Also if you are using free ESXi then you could run into max memory issues as it only supports 32gigs of RAM.
If you want to cluster each one VMware is WAY better IMHO. Hyper V uses Microsoft Failover clustering. While it is better in 2012 it is pretty much a joke overall. In a Enterprise environment clustered Hyper V has 3 tools to manage it. Hyper V manager on the hosts, Failover cluster manager and SCVMM. While you can do most things in SCVMM, often you must use the other tools when you have issues. Changing things in say Failover cluster manager, can cause issues in SCVMM ending up with your running SQL scripts to clean things up.
Building a proper Hyper V cluster takes many times longer in Hyper V vs VMware. The complexity is 100 times more as well. Trouble shooting issues with a Hyper V cluster is complex and even with Microsoft Premiere support its not always easy as they must bring in a Hyper V expert, of a FOC expert, or a SCVMM expert...all of them on different teams.
These are things you wont see in a feature list. You cant quantify, properly, your time spent building and maintaining each environment in a feature list. Other things like upgrading to a new version in a clustered environment are crazy complex in Hyper V and take much, much longer than in VMware. (week/s vs hours). Again you can put that on a feature list.
Lastly 3rd party support from storage vendors and application vendors are much better with VMware, as would be expected since its been around longer. When would tell a application vendor that their app would be hosted on a Hyper V VM, many would tell us "no" or "well if it does not work you will need to switch to vmware or a real server".
