Kevin Remde's IT Pro Weblog
IT Pro Resources
TechNet EventsMicrosoft Security Response CenterTechNet IT Manager Community HubMicrosoft Virtual AcademyKevin’s Evaluation Download Center
IT Pro Evangelist Blogs
Blain Barton Blain Barton's Blog@BlainBar
Brian LewisMy Thoughts on IT...@BrianLewis_
Dan Stolts IT Pro Guru Blog@ITProGuru
Jennelle Crothers TechBunny@jkc137
Keith MayerIT Pros ROCK!@KeithMayer
Kevin Remde Full of I.T.@KevinRemde
Matt Hester Matthew Hester's WebLog@MatthewHester
Tommy PattersonVirtually Cloud 9@Tommy_Patterson
Yung Chou Yung Chou on Hybrid Cloud@YungChou
In the first of our articles in the “VMware or Microsoft?” series, I’m going to address some misconceptions and misinformation about what Hyper-V actually is.
In a currently available document that VMware provides, comparing vSphere 5 to the as-of-then beta of what is now Hyper-V in Windows Server 2012, VMware makes the claim that they have a “Purpose-Built Hypervisor”, with “no reliance on a general purpose OS”, whereas Microsoft depends upon the Server OS to be there.
[Insert annoyingly-loud buzzer sound indicating a wrong answer here]
To address VMware's claim, let’s answer a couple of questions: What is Hyper-V?
“It’s a virtualization hypervisor.”
Right. And where is it installed?
“On Windows Server.”
[Insert an even more annoyingly-loud buzzer sound indicating a wrong answer here]
Wrong! It is installed UNDER Windows Server. (And that’s just one option. More about that in a sec.) When you enable the Hyper-V Role on Windows Server, it inserts the hypervisor between the hardware and the host operating system; actually changing the host operating system into just another “Partition” – the operating system running on virtualization that has highest priority and control of the hardware, and the OS you see when you look at the console. But architecturally, it’s actually running on top of the hypervisor. And any virtual machines you host are “child partitions”.
(For an even more detailed description of the architecture, read this: Hyper-V Architecture)
“But it still requires Windows Server, doesn’t it?”
[Insert the most annoyingly-loud buzzer sound indicating an incorrect answer that you can imagine.]
NO! You also have the ability to install use the Hyper-V Server on bare metal, which is just the hypervisor, plus some bits to make it manageable. And it’s free.
“Ah, free.. so that means it’s not full-featured, right?”
[Insert the SAD TROMBONE sound here, just to mix things up a bit.]
Boy… you’re not very good at this. The Hyper-V Server is the same hypervisor, with all of the same scale, performance, high-availability (Windows Failover Clustering), flexibility (supporting Live Migration and Live Storage Migration)… everything that’s in the version of Hyper-V installed under Windows Server.
So does VMware really have a valid claim here – that Microsoft somehow has a disadvantage of depending upon a server OS?
[Insert the sound of jubilant trumpets blowing a fanfare of victory and success]
You got that right.
For more information…
I commented on Twitter (While running 0 VMware and 1000+ Hyper-V VMs):
This is not the full story! More honesty needed, and the real answer is not wrong.
Hyper-V does leverage from Server 2012 developed technology. It's not Server 2012, but does leverage from it.
Hence VMware remarks that it relies on Generic OS (which is also not the full story as described above by you).
So the answer is not Black/White/Yes/No, it's a mix, a mix that VMware was never able to develop (like leveraging from Windows Driver Foundation).
So, when VMware says they don't rely on a general purpose OS, it's because vSphere _IS_ their OS? How is that then any different than Hyper-V "leveraging" from Windows Server (without actually having Windows Server in Hyper-V Server)? Perhaps I still don't get what you're saying, Menno.
Thanks Kevin. This is exactly what I tell the VMware vfanbois, now instead of wasting my breath, I can print this off and give it to them.
I can't believe people STILL run VMware workstation, with client Hyper-V now available...
Networking features in VMWare workstation are better then client Hyper-V
Fair enough. You win. I give up. "Uncle!" I quit. :)
All joking aside, it depends upon what you really need. What aspects of VMware networking are you missing in Hyper-V on the client?
Isolated LAN with Internet access through the hosts default gateway. Doing that with Internet sharing on the host to the virtual NIC is mich more cumbersome compared to VMWare Workstation
Cumbersome? I never thought so. Works easily whenever I configure it. Can you be more specific?