The Relationship and Differences Between Type I and Type II Virtualization

Virtualization can be thought of as “building a house”:

Type I (Bare Metal) directly builds a “virtualization layer” (Hypervisor) on the “foundation”—the bare metal hardware, and then treats each operating system as a “tenant”. There is no “landlord”; the house is directly on the foundation, providing the best performance. Typical representatives include: VMware ESXi, Xen, KVM.

Type II (Hosted)

first lays down a “landlord”—the host operating system, and then builds the “virtualization layer” on top of this layer, where the tenant OS can only reside on the second floor. The house has an additional layer between it and the foundation, resulting in slightly lower performance, but it can leverage the host OS’s drivers and toolchain for simpler deployment. Typical representatives include: VMware Workstation, VirtualBox, Parallels.

Relationship: Both use a Hypervisor to partition hardware resources, allowing multiple operating systems to share the same machine.Differences:

  1. Layer Level: Type I operates directly on hardware; Type II operates within the host OS.

  2. Performance: Type I is close to native; Type II has an additional layer of scheduling, resulting in slightly higher overhead.

  3. Usability: Type I requires specific drivers and tools; Type II can utilize the host ecosystem, making it ready to use upon installation.

Leave a Comment