Share via

Hyper-V Terminology: Update

  • Article

A while ago I posted an original guide to Hyper-V Terminology.  Well, there have been a couple of new terms that have come on to the scene that I would like to clarify for people:

  • Microsoft Hyper-V Server

    When you see people talk about “Microsoft Hyper-V Server” they are talking about the stand alone version of Hyper-V.  The simple rule here is the “Microsoft” means that you are not talking about a full Windows installation.  From a Microsoft lexicon point of view software is either part of Windows – and gets the Windows naming (e.g. Windows Powershell) or is not part of Windows and gets the Microsoft naming (e.g. Microsoft Office).

  • Windows Server 2008 without Hyper-V

    This is an actual name of a Windows SKU and refers to a version of Windows Server 2008 which does not include any Hyper-V components.  Note that people are often tripped up by the fact that this also means that there are no Hyper-V management tools in this SKU.

  • Hyper-V on Windows Server 2008 / Windows Server 2008 with the Hyper-V role enabled

    The part is a little clumsy.  While we have the “Windows Server 2008 without Hyper-V” SKU, its alternative is just “Windows Server 2008”.  But in order to avoid confusing people into thinking there is another SKU you will never see Microsoft say “Windows Server 2008 with Hyper-V” as that sounds to close to the aforementioned SKU name.  As a result you will see the above terms used to refer to a Windows Server 2008 system that has Hyper-V enabled (as compared to a Windows Server 2008 system that does not have Hyper-V enabled).

  • Hyper-V

    This is a generic term to refer to the Hyper-V technology, whether it is Hyper-V on Windows Server 2008 or Microsoft Hyper-V Server.

  • Management Operating System

    This is a new term that we are introducing in Windows Server 2008 R2.  We have been struggling without a good term here – as with Virtual PC / Virtual Server we had a nice set of terms where we could talk about the physical computer / virtual machine and the host operating system / guest operating system.  However this became muddier with Hyper-V – because we no longer really have a host operating system, and all operating systems run on top of the hypervisor.  Most people have been just using the term “Parent” or “Parent partition” to refer to what we used to call the host operating system – but this is not really architecturally correct.  Unfortunately the architecturally correct terms are – frankly – hideous; they are the “parent partition guest operating system” and the “child partition guest operating system”.  Yuck.  So after a lot of thought we decided to call the “parent partition guest operating system” the “Management operating system” as this is the operating system you use to manage your virtual machines, and “guest operating system” will be reserved to mean the operating system running inside virtual machines.

Cheers,
Ben

Comments

  • Anonymous
    March 05, 2009
    Here's to confusion! The terms "Host/Guest machine/OS" had been very clear (to me) since at least VirtualPC 2004. I also dig VS2005's "Virtual/Physical Computer/OS". The fact that you changed the internal implementation to use a "HyperVisor" instead of "emulation" is interesting to a very small fraction of the population - those who write HyperVisors (Xen, etc). I think that introducing new user-facing terms just to appease a small group of Uber-hackers in Microsoft and elsewhere will only lead to confusion. BTW, same goes for the Terminal Services team, which changed "/console" into "/admin" (and the comparable COM property!) for no reason apparent to the customers.

  • Anonymous
    March 05, 2009
    So, since "Microsoft Hyper-V Server" isn't Windows, what is its "Management Operating System"?

  • Anonymous
    March 05, 2009
    I'd go for clarity over technical correctnet any day (although I do correct Windows 2003/8 server to Windows Server 2003/8) and I for one will be sticking with guest and host.

  • Anonymous
    March 18, 2009
    @Bob - lol, nice one. C'mon Ben, does that mean Windows PE is becoming "Microsoft Preinstallation Environment"?