Get System Center 2012 Eval Bits
Get Windows Server 2012 Eval
As I mentioned in a post on Friday, March 1st, the US IT Pro Evangelist team is embarking on another team Blog Series for the month of March – Server Virtualization. To get things going with Part 1 of 20, Kevin Remde did a quick introduction to Hyper-V. I’m sure there are folks who have already been using Hyper-V with Windows Server 2012, but there are also others who have not yet done so. I am including a brief snippet directly from Kevin’s blog post below, but you will want to go directly to Kevin’s Post on Part 1 to read the full article.
To kick off our series of “20+ Days of Server Virtualization” articles, I’m going to introduce you to Hyper-V.
“Introduce? It’s not new!”
True. But even though many of you may have heard of Microsoft’s virtualization solution, you may not know much about it. And so to start our series, a brief introduction and some related, useful resources to get you ready for the month are definitely worth sharing. So let’s answer the following questions: What is Hyper-V? How do I get Hyper-V? Is it hard to use? And then I’ll wrap up the article with some additional resource links.
WHAT IS IT HYPER-V?
Hyper-V is just a part of the full Microsoft virtualization solution. It is the engine that supports running multiple virtualized installations of operating systems on top of a single physical operating system. Hyper-V is a “microkernalized hypervisor”, which is fancy-talk for “it’s a very thin layer that runs underneath the installed operating system”, to support many “machines” (including the main OS) running on and sharing the resources of the hardware. Even though your Windows Server 2012 or even Windows 8 with Hyper-V enabled is installed on hardware, virtualization is actually even supporting that main operating system as what is known as the “Parent (or Root) Partition”; still running on top of virtualization, but having higher-priority than the “child partitions” that are the virtualized machines.
Here’s a detailed Hyper-V Architecture diagram showing this relationship between the hardware and the partitioning involved: