- LPU MCA Semester 1
- CAP470
- Unit 3
CAP470 · Unit 3: Cloud virtualization
Hypervisors and their types
10 practice questions · in the MTE and ETE syllabus
Key points
- Type 1 runs directly on hardware, Type 2 on a host OS
- Type 1 is preferred in data centres
- ESXi, Hyper-V, Xen and KVM are Type 1
- VirtualBox is Type 2
A hypervisor, or virtual machine monitor (VMM), is software that creates VMs and allocates CPU, memory and I/O among them.
| Type | Runs on | Examples | Typical use |
|---|---|---|---|
| Type 1 (bare-metal) | directly on hardware | VMware ESXi, Microsoft Hyper-V, Xen, KVM | data centres and clouds |
| Type 2 (hosted) | on top of a host operating system | Oracle VirtualBox, VMware Workstation | desktops, testing and learning |
Type 1 has less overhead and a smaller attack surface because it has no host OS layer, so it is preferred for production. Type 2 is easy to install on an existing OS but adds an extra layer.
Because all VMs depend on the hypervisor, a hypervisor failure can affect every VM it hosts.
Exam trap: Type 1 means bare-metal, not first-generation; do not mix up the two types.
Try two questions
A developer wants to try a Linux VM quickly on a Windows laptop. Which hypervisor type is most convenient?
- Type 1, which must replace the laptop's operating system
- Type 2, such as VirtualBox
- Neither, because Windows cannot host any VMs
- A tape library, which stores virtual machines
Show the answer
B. Type 2 hypervisors install like normal applications, so they suit desktops and testing.
Why not A: A bare-metal hypervisor takes over the hardware and removes the convenience.
Why not C: Windows can host VMs through Type 2 hypervisors.
Why not D: A tape library stores backups, not running VMs.
Which hypervisor type runs on top of a host operating system?
- Type 1
- Type 0
- Type 3
- Type 2
Show the answer
D. Type 2, or hosted, hypervisors depend on a host operating system.
Why not A: Type 1 runs directly on hardware.
Why not B: Type 0 is not a standard hypervisor type.
Why not C: Type 3 is not a standard hypervisor type.