Virtualization Concepts

What Virtualization Means on the Exam

Virtualization is the creation of software-based versions of physical resources such as servers, storage, networks, and entire operating systems. A single physical host can run several virtual machines (VMs), each acting as an isolated computer with its own guest OS, applications, and virtual hardware. CompTIA A+ Core 1 (exam 220-1201, the V15 edition launched March 25, 2025) tests virtualization in Domain 4, which is weighted at 11 percent of the 90-question, 90-minute exam.

The core benefit is consolidation: instead of ten under-used physical servers, one powerful host runs ten VMs, cutting hardware, power, cooling, and rack costs. Other tested benefits include sandboxing (running risky software in isolation), legacy-application support, cross-platform development, fast disaster recovery via snapshots, and resource efficiency.

Hypervisors: Type 1 vs Type 2

A hypervisor (also called a virtual machine monitor) is the software layer that creates, schedules, and isolates VMs. Knowing the two types cold is a guaranteed exam point.

Type 1 (Bare-Metal)

Type 2 (Hosted)

Trap: CompTIA classifies Microsoft Hyper-V as a Type 1 hypervisor even though you enable it from inside Windows 11 Pro. When Hyper-V starts, Windows itself becomes a privileged management partition and the hypervisor sits beneath it. Do not call Hyper-V "Type 2" just because it appears on a desktop OS.

Virtual Machine Components

Each VM receives software versions of real hardware. Recognize these by name and file extension:

Virtual networking modes you must distinguish:

• Bridged — the VM gets its own IP address directly on the physical LAN and appears as a separate device.
• NAT — the VM hides behind the host IP; it reaches the internet but is not directly reachable from the LAN.
• Host-only — the VM talks only to the host (no internet, no LAN), ideal for malware analysis.
• Internal — VMs talk only to each other.

Hardware Virtualization Requirement

Before any hypervisor can run modern 64-bit guests, the CPU's hardware-assisted virtualization feature must be turned on in firmware: Intel VT-x (sometimes branded VT-d for I/O) or AMD-V. This setting often ships disabled. If a customer reports "my VM won't start" or VirtualBox shows a VT-x error, your first step is to reboot, enter BIOS/UEFI, and enable virtualization. On Windows hosts, Hyper-V, the Windows Hypervisor Platform, and Memory Integrity can also lock VT-x away from VirtualBox/VMware, producing the same symptom.

Containers vs Virtual Machines

Because containers reuse the host kernel, you cannot run a Windows container on a Linux host without a hidden VM. That shared-kernel trade-off explains both their speed and their weaker isolation versus VMs.

Use Cases You Will See on the Exam

Domain 4 questions are usually scenario-based, so connect each benefit to a real situation:

• Server consolidation — replace many idle physical servers with VMs on one host to cut power, cooling, and rack space.
• Development and testing — spin up disposable environments that exactly mirror production, then discard them.
• Legacy application support — keep an old line-of-business app alive by running its required Windows XP or 7 guest in a VM long after the hardware is gone.
• Sandboxing — open suspicious email attachments or unknown installers inside an isolated VM so any infection never touches the real machine.
• Cross-platform testing — a web developer checks a site against Windows, macOS, and several Linux distributions from a single laptop.
• Disaster recovery — because a VM is just files, you snapshot it, copy it offsite, and restore it on different hardware in minutes.
• Training and labs — students practice destructive tasks (repartitioning, registry edits) with no risk to a shared classroom PC.

How Resource Sharing Actually Works

A host with 8 physical cores can present far more than 8 vCPUs across its VMs because most guests are idle most of the time; the hypervisor schedules real cores only when a guest needs one. This is CPU oversubscription. Memory can be oversubscribed too, but RAM is far less forgiving than CPU: if active VMs demand more than the host physically has, the hypervisor must swap memory to disk and performance collapses. For the exam, remember that adequate physical RAM, fast SSD-backed storage for the virtual disks, and a multi-core CPU with VT-x/AMD-V are the four host requirements that make a usable virtualization platform.