The independent analyst firm Burton Group recently released a proposed set of standards for server virtualization -- some required, some preferred, some optional -- to help IT see beyond the data sheet marketing check boxes for EMC VMware's ESX, Microsoft's Hyper-V, and Citrix's XenServer. VMware supports 27 of the requirements and most of the preferred and optional standards, while Hyper-V supports 24 of the required standards and fewer of the others (my previous post "A new wrinkle -- and possible conclusion -- for the hypervisor wars" discusses who would be affected by those three "required" omissions in Hyper-V).
Note: Actually, according to Chris Wolf (Citrix CTP, MVP for Microsoft Virtualization, vExpert for VMWare), the author of the Burton Group criteria, Hyper-V meets 25 of the 27 requirements because he was able to successfully cluster SCVMM.
Recently I've examined closely the Burton Group criteria and it is quite impressive. Weighing in at 70 pages, the criteria has some debatable features in terms of placement (required, preferred or optional) but hits everything you can imagine that clients could ask for in a solution. As I've mulled over Burton Group's recommendations, I've come to believe that one of its preferred standards -- memory overcommit -- should be considered a requirement. Right now, only VMware ESX meets that condition.
[ InfoWorld's J. Peter Bruzzese takes a look at the hypervisor war and the new Hyper-V R2. | Keep up with the latest virtualization news with InfoWorld's virtualization newsletter and visit the InfoWorld Virtualization Topic Center for news, blogs, essentials, and information about InfoWorld virtualization events. ]
Get the independent advice and expertise you need to support a virtual workforce.
The increase in Linux popularity has increased the frequency and sophistication of malware attacks. Read this 2 page white paper now to learn how you can protect your Linux environment with real-time protection that is certified by all major Linux vendors.
Download now »
Ensuring acceptable application delivery will become even more difficult over the next few years. As a result, IT organizations need to ensure that the approach that they take to resolving the current application delivery challenges can scale to support the emerging challenges. This handbook elaborates on the key tasks associated with planning, optimization, management and control and provides decision criteria to help IT organizations choose appropriate solutions.
Download now »
A common misconception is that mid-range storage requirements are dramatically different than that of a larger enterprise. Mid-range storage users may require less capacity, but they have similar functionality and management requirements. This ESG paper examines mid-range storage needs and reviews a new solution that adjusts size while retaining value, performance and functionality.
Download now »
669 Recommendations
One issue that you need to look out for is clock skew. If you ARE in an over commit situation, and the Hypervisor is essentially paging to disk, it can miss updates to the various VMS, and they can get "behind" (in terms of the 'real time).
This can affect software builds that rely on Make and other time-stamped procedures. As long as it's what is called here "good" overcommit, and no paging occurs, it can be a good thing...Just watch out for the "bad" over commit, even if all it does is affect performance due to paging and slower access to "memory".