Virtualization allows multiple operating systems to run simultaneously on a single physical machine. CompTIA A+ 220-1101 tests virtualization concepts, hypervisor types, virtual machine characteristics, and cloud relationships. Technicians use virtualization for software testing, running legacy apps, sandbox environments, and server consolidation — understanding the fundamentals enables effective setup and troubleshooting.
Practice this topic
Hypervisor: software that creates and manages virtual machines (VMs). Type 1 hypervisor (bare-metal): runs directly on the hardware without an underlying OS — more efficient, used in enterprise. Examples: VMware ESXi, Microsoft Hyper-V Server, Citrix XenServer. Type 2 hypervisor (hosted): runs as an application within a host OS — easier to install, convenient for desktop use. Examples: VMware Workstation Pro, VMware Workstation Player, Oracle VirtualBox, Parallels Desktop (macOS).
Virtual machine (VM): a software-emulated computer with its own virtual CPU, RAM, disk, and network adapter — completely isolated from the host and other VMs. Each VM runs its own OS (guest OS). VMs use disk image files (.vmdk for VMware, .vhd/.vhdx for Hyper-V, .vdi for VirtualBox) to store the virtual hard drive. Snapshots: capture the current state of a VM — can roll back to any snapshot instantly. Essential for testing changes and malware analysis.
Resource requirements: virtualization requires enabling hardware virtualization in BIOS (Intel VT-x or AMD-V). Without this, Type 2 hypervisors either won't run 64-bit VMs or run significantly slower (software emulation). Verify in Task Manager → Performance → CPU — 'Virtualization: Enabled'. VMs share physical RAM and CPU — host needs enough resources for both host and guest OSes running simultaneously.
VM isolation and security: VMs are isolated from each other and from the host. A malware-infected VM typically cannot escape to infect the host or other VMs — this is why VMs are used for malware analysis (sandboxing). Guest additions / VMware Tools: software installed in the guest OS that enables clipboard sharing, drag-and-drop, better display drivers, and time synchronization between host and guest.
Desktop use cases: application testing in an isolated environment, running legacy applications that don't work on modern OS, development and testing, security research/malware analysis in sandboxed VMs, running multiple OS versions simultaneously (Windows + Linux on same machine), training labs.
Server virtualization: consolidating multiple physical servers into VMs on fewer physical hosts — reduces hardware costs, power consumption, and data center space. Each VM acts as an independent server. Migration: move running VMs between physical hosts (vMotion, Live Migration) without downtime. High availability: VMs can automatically restart on another host if the physical host fails.
Containers vs VMs: containers (Docker, Kubernetes) share the host OS kernel — much lighter weight than VMs (MB vs GB), faster startup (seconds vs minutes). VMs have complete OS isolation — stronger security boundary. Containers are better for microservices and rapid deployment. VMs better for complete OS isolation requirements. A+ covers container awareness; in-depth container knowledge is beyond A+ scope.
A VM has direct access to the host's physical hardware
A VM uses virtual hardware emulated by the hypervisor — the guest OS interacts with virtual devices, not the physical hardware directly. The hypervisor translates virtual hardware requests to real hardware operations. This isolation is what makes VMs safe for testing — the guest can't directly access host hardware or other VMs' resources
These questions are representative of what you will see on A+ exams. The correct answer and explanation are shown immediately below each question.
A technician installs VirtualBox on a Windows 10 laptop but cannot create 64-bit VMs — only 32-bit options are available. What is the most likely cause?
Explanation: 64-bit guest VMs require hardware virtualization support (Intel VT-x or AMD-V) to be enabled in the CPU and in the BIOS/UEFI firmware. Without it, Type 2 hypervisors like VirtualBox can only run 32-bit VMs using software emulation. Solution: restart, enter BIOS/UEFI (typically F2 or Delete), find the virtualization settings (may be called Intel Virtualization Technology, VT-x, SVM Mode, or AMD-V), enable it, save and restart. VirtualBox is fully capable of 64-bit VMs — hardware support just must be enabled.
A snapshot captures the current state of a VM (memory, disk state, settings) at a point in time — reverting to a snapshot is nearly instantaneous. Snapshots are stored as incremental delta files linked to the base disk. However, long-running snapshots accumulate incremental data and can cause performance degradation and consume significant disk space. A backup creates an independent full copy of the VM files — complete, portable, and restorable even if the original hypervisor infrastructure is lost. Best practice: use snapshots for short-term change testing; use backups for long-term data protection.
Try free Virtualization practice questions with explanations, topic links and progress tracking.