Foundations — Virtualization — type 1 and type 2 hypervisors

Before you can judge where a hypervisor sits (that's the whole Type-1-vs-Type-2 question in Virtualization — type 1 and type 2 hypervisors), you must own a small pile of words the parent note quietly assumes. We build each from zero, in an order where every new idea only leans on ones already standing.

1. Hardware / "bare metal"

The picture: imagine a flat slab at the bottom of a tower. Everything we build in this topic stacks on top of this slab.

Why the topic needs it: the entire Type 1 vs Type 2 split is the single question "what software touches this slab directly?" If you don't have a mental slab, the question is meaningless.

2. Instruction

The picture: a conveyor belt of little cards; the CPU picks up one card, does exactly what it says, and grabs the next.

Why the topic needs it: a hypervisor's job is to watch the conveyor belt and grab certain dangerous cards before the CPU does something the guest shouldn't be allowed to do.

3. Kernel mode vs user mode (CPU privilege rings)

Not all instruction-cards are equally dangerous. "Add 2 + 2" is harmless. "Reconfigure all of memory" or "talk directly to the disk" could crash the whole machine. So the CPU physically refuses to run the dangerous ones unless it is in a special trusted state.

The picture: two rings, one inside the other. The inner ring (kernel) can do anything; the outer ring (user) is fenced off from the dangerous controls. This is exactly the model in CPU Privilege Rings.

Why the topic needs it: the hypervisor's trick is to run itself in the innermost ring and shove each guest OS out to a less powerful ring — even though the guest OS thinks it's still king. That demotion is the heart of "trap-and-emulate".

4. Privileged instruction & the "trap"

The picture: a tripwire. The guest walks along running instructions; the moment it steps on a privileged instruction while in the low-privilege ring, a wire trips and control is flung down to the hypervisor.

Why the topic needs it: "trap-and-emulate" is the parent note's core mechanism. Trap = the tripwire firing. Emulate = the hypervisor faking a believable result and handing control back. No trap concept, no understanding of how one machine safely pretends to be many.

5. Sensitive instruction

The picture: on the conveyor belt, colour the cards. Grey cards are harmless. Red cards are sensitive — they touch shared machine state.

Why the topic needs it: the Popek & Goldberg rule (parent note) says a machine is cleanly virtualizable only if every red (sensitive) card is also a tripwire-card (privileged). If some red card is not a tripwire, it slips past the hypervisor unnoticed — and that is exactly the old-x86 POPF problem the parent describes. Symbols in words:

6. Operating system, host OS, guest OS

The picture: a Russian nesting doll. In Type 2, the outer doll is the host OS; inside it sits the hypervisor; inside that sits the guest OS. In Type 1 there is no outer host doll — the hypervisor is the outermost software itself.

Why the topic needs it: "host OS present or absent" is literally the Type 2 vs Type 1 distinction. These two words are the vocabulary the whole comparison table is written in.

7. Virtual machine (VM)

The picture: a sealed glass box. Inside, a guest OS runs happily believing the box is a real computer. The hypervisor is the glass — it lets the guest see a reflection of hardware, never the real thing directly. Contrast this heavy full-machine box with the lighter approach in Containers vs Virtual Machines.

Why the topic needs it: this is the product a hypervisor makes. Everything above is the machinery; the VM is the output.

8. Layer & "layers to silicon"

The picture: a relay race. Every extra runner (layer) who must receive and pass the baton adds delay before it reaches the finish line (the hardware).

Why the topic needs it: this counting is the entire quantitative argument for "Type 1 is faster", including Example 3 in the parent note.

The prerequisite map

Read top to bottom: raw hardware gives us instructions; the danger of some instructions forces privilege modes; that gives us traps and sensitive instructions, whose relationship (Popek–Goldberg) makes safe virtualization possible; layered software then produces VMs, and how many layers is the Type 1 / Type 2 answer.

Equipment checklist

Cover the right side and test yourself. If any answer surprises you, re-read that section above.