Virtualization products can use several different architectures to share a computer’s hardware resources among VMs. The earlier type of virtualization products, including Microsoft Windows Virtual PC and Microsoft Virtual Server, requires a standard OS installed on a computer. This becomes the “host” OS. Then you install the virtualization product, which adds the hypervisor component. The hypervisor essentially runs alongside the host OS, as shown in Figure 3-1, and enables you to create as many VMs as the computer has hardware to support.

Virtualization architectures

FIGURE 3-1 A hybrid VMM sharing hardware access with a host operating system

This arrangement, in which the hypervisor runs on top of a host OS, is called Type II virtualization. By using the Type II hypervisor, you create a virtual hardware environment for each VM. You can specify how much memory to allocate to each VM, create virtual disk drives by using space on the computer’s physical drives, and provide access to peripheral devices. You then install a “guest” OS on each VM, just as if you were deploying a new computer. The host OS then shares access to the computer’s processor with the hypervisor, with each taking the clock cycles it needs and passing control of the processor back to the other.

Type II virtualization can provide adequate VM performance, particularly in classroom and laboratory environments, but it does not provide performance equivalent to separate physical computers. Therefore, it is not generally recommended for high-traffic servers in production environments.

The virtualization capability built into Windows Server 2012 R2, called Hyper-V, uses a different type of architecture. Hyper-V uses Type I virtualization, in which the hypervisor is an abstraction layer that interacts directly with the computer’s physical hardware—that is, without an intervening host OS. The term hypervisor is intended to represent the level beyond the term supervisor, in regard to the responsibility for allocating a computer’s processor clock cycles.

The hypervisor creates individual environments called partitions, each of which has its own OS installed and accesses the computer’s hardware via the hypervisor. Unlike Type II virtualization, no host OS shares processor time with the hypervisor. Instead, the hypervisor designates the first partition it creates as the parent partition and all subsequent partitions as child partitions, as shown in Figure 3-2.

Virtualization architectures

FIGURE 3-2 A Type I VMM, with the hypervisor running directly on the hardware

The parent partition accesses the system hardware through the hypervisor, just as the child partitions do. The only difference is that the parent runs the virtualization stack, which creates and manages the child partitions. The parent partition is also responsible for the subsystems that directly affect the performance of the computer’s physical hardware, such as Plug and Play, power management, and error handling. These subsystems also run in the OSs on the child partitions, but they address only virtual hardware, whereas the parent, or root, partition handles the actual hardware.


It might not seem like the Hyper-V role in Windows Server 2012 R2 provides Type I virtualization,
because it requires the Windows Server OS to be installed and running. However, adding the Hyper-V role actually converts the installed instance of Windows Server 2012 R2 into the parent partition and causes the system to load the hypervisor before the OS.


This article is a part of 70-410 Installing and Configuring Windows Server 2012 Prep course, more articles in this course are :

Hyper-V implementations

Windows Server 2012 R2 includes the Hyper-V role only in the Standard and Datacenter editions. The Hyper-V role is required ...
Read More

Installing Hyper-V

Once you have the appropriate hardware, you can add the Hyper-V role to Windows Server 2012 R2 by using Server ...
Read More

Using Hyper-V Manager

Once you have installed the Hyper-V role and restarted the computer, you can begin to create VMs and deploy OSs ...
Read More

Configuring resource metering

Resource metering is a Windows PowerShell–based feature in Windows Server 2012 R2 Hyper-V that enables administrators to document VM usage ...
Read More

Virtual disk formats

Windows Server 2012 R2 Hyper-V supports the original VHD disk image file and the new VHDX format. The original VHD ...
Read More

Creating virtual disks

Windows Server 2012 R2 Hyper-V provides several ways to create virtual disk files. You can create them as part of ...
Read More

Configuring pass-through disks

This objective has thus far been concerned primarily with VHDs, areas of space on a physical disk drive allocated for ...
Read More

Modifying virtual disks

Windows Server 2012 R2 and Hyper-V provide several ways for administrators to manage and manipulate VHD images without mounting them ...
Read More

Creating checkpoints

In Hyper-V, a checkpoint is a captured image of the state, data, and hardware configuration of a VM at a ...
Read More

Configuring Storage Quality of Service (QoS)

Because it is common for there to be more than one virtual hard disk hosted by a single physical hard ...
Read More

70-410 Installing and Configuring Windows Server 2012 Prep course includes following practice tests:

No posts found.