VMGuru.nl – I choose (a virtual) life!

This week I got the question if I could draw up a short lists of pro’s and cons for MED-V. Since I’m doing virtualization in the widest possible way, this fits well in my job description.

But heck, what a question! Before I could even try to  answer the question I really had to dive into the Microsoft Enterprise Desktop Virtualization solution (hence MED-V) which is part of the Microsoft Desktop Optimization Pack (MDOP). Sure, I already seen some comments on the internet about MED-V and I already was somewhat biased. Still I tried to make it an objective report.

Let’s start with what it is not in my opinion. Although it enables management of virtualized desktops it is not a full blown desktop virtualization solution like XenDesktop and VMware View.

(more…)

Yesterday I attended the ‘TechNet – Get Ready for all Microsoft virtualization products’ session in Utrecht (NL). This was a new style paid (€99,-) Technet session, max of 20-30 professionals in a classroom. The program consisted of Hyper-V, App-V, Med-V, Terminal services and System Center Virtual Machine Manager 2008.

Hyper-V
We started with an introduction to Hyper-V, luckily the trainer had updated his lab to Hyper-V 2, so we could check out the new features which should compete with VMware. After explaining the architecture, networking and storage it was very obvious that this was the standard Microsoft propaganda. They were comparing Hyper-V 2 to VI 3.5, which were practically the same, but of course Microsoft’s hyper-V solution was much cheaper. Grrrrr! Again, when you do a comparison, do a fair comparison and compare Hyper-V to vSphere 4 (because the release is not far away I will allow Microsoft to use Hyper-V 2 in this comparison). Then the numbers are very different and maybe the VMware solution costs more but obviously you will get a lot more.

I also disliked the insinuation that when they compare a microkernel hypervisor to a monolithic hypervisor Microsoft  makes it look like VMware’s hypervisor is one out of the stone ages. Play fair, win the fight based on your own strong points.

When he explained the Hyper-V I/O architecture with the parent partition, VM Bus, synthetic drivers, etc, I asked him if this didn’t introduce a singe point of failure and a possible I/O bottleneck. In true MS fashion he denied both, claiming that I/O was tested and you shouldn’t install Exchange in the parent partition. Duh!

(more…)