Hyper-V features the hypervisor-based architecture that is
shown in Figure 14. The hypervisor virtualizes processors and memory and mechanisms for the virtualization stack in the root partition to
manage child partitions (virtual machines) and expose services such as I/O
devices to the virtual machines.
The root partition owns and has direct access to the
physical I/O devices. The virtualization stack in the root partition provides a
memory manager for virtual machines, virtualized I/O devices and management APIs . It also implements emulated devices such as integrated device
electronics (IDE) and PS/2, but it supports Hyper-V-specific devices for
increased performance and reduced overhead.
The Hyper-V-specific I/O architecture consists of virtual
service providers in the root partition and virtual service clients in the
child partition. Each service is exposed as a device over VMBus, that acts as
an I/O bus and enables optimum-performance communication between virtual machines
that use mechanisms such as shared memory. Plug and Play computes these
devices, including VMBus, and loads the appropriate device drivers (virtual
service clients). Services other than I/O are also exposed through hyper-V architecture.
Windows Server-2008 R2,Windows Server-2012and Windows Server 2008 feature enlightenment to the operating system to
optimize its behavior when it is running in virtual machines. The benefits
include reducing the cost of memory virtualization, improving multicore
scalability, and decreasing the background CPU usage of the guest operating
system.
No comments:
Post a Comment