CSE4011 - Module 2 - 1

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 18

Virtual Machine Monitor (VMM)

 Abstracts the virtual machine (VM) hardware


 Presents a complete set of emulated hardware
 Provides isolation
 Runs the Guest OS
 Manages access of resources of the host system
Hypervisor

 Software that
 enables virtualization
 recreates the hardware
 is responsible for hosting multiple VMs on a single machine
 resides below the VMs and above the hardware
 provides support for different OSs to run at a specific time
 manages interaction between each VM & the shared hardware
Comparison

Typical Server Server with Hypervisor

Guest Guest Guest


OS OS OS
Operating System Hypervisor

Hardware Hardware
Basics

 Works with the VMM


 scheduling access to underlying hardware
 Lightweight operating shell
 Primary role: host VMs
 offers better performance
 fewer security vulnerabilities
 Vendor specific
 patches or security updates will come directly from the virtualization
software vendor
Characteristics

 Based on the properties defined by Popek and Goldberg, a


hypervisor should ensure that
 the hardware emulated to the VM is identical to a physical machine
with the same specification
 the VM experiences minimal performance overhead
 it has complete control over the underlying hardware
Source: Net
Types

Type 1 / Bare metal Type 2 / Hosted

VM VM VM VM VM VM

Hypervisor Hypervisor
Operating System
Hardware Hardware
Type 1 Hypervisor

 Runs directly on the hardware


 Takes the place of the OS
 Directly interact with the ISA exposed by the underlying hardware
 Overhead caused by virtualization is less
 Preferred in organizations, where huge servers are to be virtualized
 Over-allocation is possible
 Advantage: any problem in a VM will not affect other VMs
Type 2 Hypervisor

 Installed on top of the OS


 Managed by the OS
 Completely dependent on host OS for its operations
 Emulate the ISA of virtual hardware
 Preferred to virtualize resources of personal desktops
 Performance overhead is high
 Any problem in the base OS affects the hypervisor even if it is secure
Examples
Type 1 / Bare metal Type 2 / Hosted
 VMware ESXi Server  VMware Workstation
 Microsoft Hyper-V  Microsoft Virtual PC
 Citrix/Xen Server  Oracle Virtual Box
Source: Net
Virtual machine manager
 Dispatcher
 Entry point to VMM
 Reroutes the instructions issued by VMM
 Allocator
 Decides the system resource provision
 Interpreter
 Executed when VM execute privileged instruction
 Trap is triggered when corresponding routine is executed
Popek and Goldberg Virtualization Requirements
 The Popek and Goldberg virtualization requirements are a set of
conditions sufficient for a computer architecture to support system
virtualization efficiently.
 They were introduced by Gerald J. Popek and Robert P. Goldberg in
1974
 "Formal Requirements for Virtualizable Third Generation
Architectures".
 Even though the requirements are derived under simplifying
assumptions, they still represent a convenient way of determining
whether a computer architecture supports efficient virtualization and
provide guidelines for the design of virtualized computer architectures

You might also like