Weblog of Mark Vaughn, and IT professional and vExpert specializing in Enterprise Architecture, virtualization, web architecture and general technology evangelism

Tag: Microsoft

Multiple Hypervisors Ahead: Proceed with Caution

Multi-hypervisor management tools are great for common provisioning and monitoring tasks, but they fall flat when it comes to deeper functionality, which provide the most value.

Looking past the feature parity and marketing hype in the hypervisor market, there are compelling reasons to deploy a heterogeneous virtualization environment (i.e., reducing costs, improving compatibility with certain applications, avoiding vendor lock-in). Do you keep fighting it off? Do you concede and draw lines of delineation between the hypervisors? Do you throw your hands up and simply let them all in?

The answer certainly depends on your skillsets, needs and tolerance for pain. But if you’re looking for an easy way out through a multi-hypervisor management tool, you may be disappointed.

For more on this topic, check out my TechTarget article at “Proceed with caution: Multi-hypervisor management tools“, then come back here and leave a comment.

Microsoft Hypervisor and OS Support Conflict of Interest

A few weeks ago, I followed some back and forth commentaries comparing Microsoft’s Hyper-V to VMware’s vSphere. There was a lot of discussion on the features of Hyper-V and vSphere, which touched on the support of guest operating systems. It was in the discussion of guest OS support that I realized there was a conflict of interest, on the part of Microsoft, as both the creator of the Windows operating systems and the Hyper-V hypervisor.

You can read my article on this on TechTarget at http://searchservervirtualization.techtarget.com/news/column/0,294698,sid94_gci1443339,00.html

Here is some background data that was not in the article. These are the “back and forth commentaries” that I mentioned:

This started with an InformationWeek article by Elias Khnaser, that inspired a response by Chris Steffen on the Microsoft Virtualization Team Blog. From there, Eric Gray added his thoughts and then Nicholas Weaver did a great write-up of his thoughts on the topic. At this point, Ben Armstrong (Virtualization Program Manager at Microsoft) added a comment to Nicholas’ blog and Nicholas followed that with a second post. Follow all of that? Now you see why it is not in the article.