Both Microsoft and VMware have revamped their product suites and therefore their licensing once more and how you buy will dictate how you license (as always). It has taken a bit of time for all the information to percolate through to each corporate site and all the issues to be addressed. As we did before, let us look at licensing. We will look at first the old model of Hyper-V vs VMware vSphere vs Citrix Xen vs RedHat KVM. Then in a follow-on article we will look at the new cloud suite models.
Now that VMword 2012 San Francisco is over and I have some time to reflect on my virtualization thoughts in general before getting ready for VMworld Barcelona. One thing I took noticed with the recent announcements about vSphere 5.1 and Hyper-V 2012. Microsoft and VMware both released a specific new feature to each platform respectfully at basically the same time. Is this a sign that Microsoft is really closing the gap on VMware? I think we are getting there but I have also made some other personal observations on how I think both see virtualization in the future and I foresee a completely different method and mindset for the future between these two companies.
Some interesting news about VMWare was made public on Sunday 26th August – the day before VMWorld – that VMware joins OpenStack. This appears to be driven largely by the acquisition of Nicira – and the role that Nicira currently plays in the implementation of virtual networking in OpenStack.
The vSphere 5.1 enhancements are more designed to better fit vSphere into the vCloud Suite as well as move the bar further on virtualizable workloads. vSphere 5.1 allows the virtualization of high performance graphics, real-time, HPC, and big data workloads.
While looking around the web for anything new with virtualization, I kept seeing more and more posts and articles about the new type of virtual hypervisor. Type 0, now this sounds interesting and I found these definitions for each type of hypervisor.
The drive to virtualize business critical workloads is going to require more vSphere licenses. Shifting low hanging fruit workloads to Hyper-V may free up licenses. But it creates a cross-hypervisor management problem that could erode all of the savings from Hyper-V licensing. This puts a premium on cross-hypervisor management solutions.