In 2008 I wrote an article named “Hyper-V, not in my datacenter!” which was based on Hyper-V version 1. In 2009 I wrote an article named “Hyper-V, the laughter continues” and “ESX vs Hyper-V mythbusting myth” which was based on Hyper-V version 2.
Microsoft promised/warned us that with Windows Server 2012 Hyper-V version 3 this would all be history. But as Sander wrote in a more recent article named “Windows Server 2012 Hyper-V: overpromising and underdelivering” this turned out to be a marketing statement based on a premature product with no suitable management tools.
But now with the release of System Center 2012 Service Pack 1, Hyper -V version 3 should be the VMware vSphere-killer (according to MS).
Too bad, the sequel continues! Yesterday Edwin pointed me to a great article by Justin Paul, a fellow blogger, vExpert, VCP and EMC specialist, in which he describes his recent struggles with Windows Server 2012 Hyper-V.
True, in the last four point Justin refers to some information which is a bit outdated, but he has a valid point stating “Then explain why it happened to a 2012 hyperV cluster if it is fixed ?” when people in the comment section claim that Microsoft solved this in the new version of Hyper-V. Apparently they weren’t fixed.
When I read Justin’s comments on the CSV issues and the hassle to setup a Hyper-V environment, I stand by my earlier position, this is not a product which I trust to base my enterprise IT infrastructure on. So still, “Hyper-V? Not in my datacenter…”.