A hypervisor is software that allocates a physical server’s resources to virtual machines (VMs) and keeps them logically isolated. This lets multiple operating systems run on one machine, so a problem in one VM can be contained without disrupting the others. section 13.4.2
Hypervisors are grouped by where they run:
- Type 1, or bare-metal, runs directly on physical hardware. It offers better performance and is common in enterprise and cloud environments. section 13.4.2
- Type 2, or hosted, runs on an existing operating system and is typically used on desktops, such as for developers running multiple operating systems. section 13.4.2
One server, four university services
A university can run an exam platform, a research notebook hub, legacy applications, and its public website on separate VMs on one server. If the website VM crashes under heavy traffic, the other VMs remain unaffected. This makes better use of hardware while helping contain failures or compromises. section 13.4.2
|
|
Virtual
Machines (VMs)
|
Containers
|
|
Virtualization
|
Full
(Hypervisor emulates entire hardware stack)
|
Lightweight
(Container engine shares the host OS)
|
|
Isolation
|
Strong
(each VM instance has its own OS)
|
Moderate
(each container is a runtime environment on the same shared OS)
|
|
Startup Time
|
Slow
(minutes)
|
Fast
(seconds)
|
|
Performance
|
~15% loss
|
<2% loss
|
|
Density
|
10–100
instances per host
|
100–1000
instance per host
|
|
Security Risks
|
Compromise
of OS is typically contained to that VM
|
Shared OS
increases potential blast radius on OS security attacks
|
|
Ideal Use Case
|
Running
multiple fully independent OS environments
|
Rapid
deployment of microservices and applications
|
|
Virtualization
|
Full
(Hypervisor emulates entire hardware stack)
|
Lightweight
(Container engine shares the host OS)
|
|
Isolation
|
Strong
(each VM instance has its own OS)
|
Moderate
(each container is a runtime environment on the same shared OS)
|
Compare VMs with containers by isolation, performance, density, risks, and ideal use cases. section 13.4.2




