Objective 4.2: Explain virtualization concepts

Cert: CompTIA A+ Core 1 (220-1201) V15 Domain: 4.0 Virtualization and Cloud Computing Weight: ~11% of Core 1 Depth: Explain. Understand what VMs are for, the hypervisor types, and the supporting requirements.

What this objective tests

You should be able to explain the purposes virtual machines serve (sandbox, test/dev, application virtualization, desktop virtualization, containers), the difference between Type 1 and Type 2 hypervisors, and the supporting infrastructure requirements (security, network, storage).

Key facts

Purpose of virtual machines:

• Sandbox. A safe isolated environment to run untrusted code or test risky changes without affecting the host or production. Common for malware analysis, evaluating new software, or experimenting with system configuration.
• Test/development. Spin up VMs that match production for testing without affecting live systems. Standard practice in software development.
• Application virtualization.
• Legacy software/OS. Run old applications that need an older operating system inside a VM on modern hardware. Common for line-of-business apps that the vendor never updated.
• Cross-platform virtualization. Run Windows software on a Mac, or vice versa, by hosting the other OS in a VM.
• Desktop virtualization (VDI). Instead of giving each user a physical desktop, host their desktop in a centralized server farm. Users connect to their desktop from any device. Simplifies management and supports thin clients or zero clients.
• Containers. A lighter-weight virtualization layer that shares the host OS kernel but isolates the application's filesystem and processes. Docker is the well-known platform. Containers start in seconds vs minutes for full VMs.

Hypervisors:

• Type 1 (bare metal). Runs directly on hardware with no underlying OS. Examples: VMware ESXi, Microsoft Hyper-V (when installed as the only OS), KVM (when used as the bare metal host), Proxmox VE. Used in data centers and server environments. Higher performance.
• Type 2 (hosted). Runs on top of a regular operating system as an application. Examples: VMware Workstation, Oracle VirtualBox, Parallels Desktop. Used on laptops and desktops for occasional VM use.

Requirements:

• Security. Isolation between VMs matters. A compromised VM should not be able to escape to the host or other VMs. Hypervisor patching, VM hardening, and segmenting hypervisor management traffic are all part of secure virtualization.
• Network. VMs need virtual network adapters bridged or NATed to the physical network. Virtual switches and VLAN tagging extend Layer 2 features into the virtualization layer.
• Storage. VMs need storage for their virtual disks. Options range from local disk on the host to shared SAN/NAS for VM mobility (live migration, high availability).

Common gotchas

• Hardware virtualization not enabled. Intel VT-x or AMD-V must be on in BIOS. Hypervisor either falls back to software emulation (slow) or refuses to start.
• Snapshot vs backup. A VM snapshot is a point-in-time image, useful for reverting after a risky change. Snapshots are not a backup; they live on the same storage as the VM. Always have an actual backup as well.
• Containers and persistence. Containers are designed to be stateless and disposable. Persistent data needs to be stored on mounted volumes outside the container.
• Type 1 vs Type 2 use cases. Type 1 for production server consolidation. Type 2 for desktop power users and developers. Mixing the two up on a deployment recommendation is a common exam trap.
• VDI bandwidth. VDI sessions need adequate bandwidth and low latency from the user to the data center. Poor network can make a VDI desktop feel sluggish even with a powerful back end.

Real-world context

For SMB Revtek customers:

• A small business might not run a hypervisor on premises. Many have moved to cloud-hosted equivalents (Microsoft 365, Google Workspace, hosted line-of-business apps).
• When on-prem virtualization is needed, Hyper-V (built into Windows Server) or VMware ESXi (now Broadcom-controlled, increasingly expensive) are common choices. Proxmox VE is gaining traction as a free alternative.
• Containers are typically a developer concern in SMB context, not a production IT concern.

Common helpdesk and consultation calls:

• "Why is my VM running so slow?" Often virtualization not enabled in BIOS, or under-allocated RAM/CPU, or storage IO bottleneck.
• "Can we still run our 2010-era line-of-business app?" Yes, in a Windows 7 (or whatever) VM. Carefully air-gap the VM from the network if security matters.
• "Should we move to virtual desktops?" Generally not for very small businesses (cost and complexity exceed the benefits). Worth considering for 50+ knowledge workers in highly mobile or compliance-driven environments.

Sources

• [CompTIA A+ 220-1201 Exam Objectives Version 4.0, Section 4.1](../../../../../../30-RevyTechJourney/CompTIA%20A%2B%20220-1201%20Exam%20Objectives%20%284.0%29.pdf)
• [Wikipedia: Hypervisor](https://en.wikipedia.org/wiki/Hypervisor)
• [Wikipedia: Virtual machine](https://en.wikipedia.org/wiki/Virtual_machine)
• [Wikipedia: OS-level virtualization (containers)](https://en.wikipedia.org/wiki/OS-level_virtualization)
• [Wikipedia: Virtual desktop infrastructure](https://en.wikipedia.org/wiki/Desktop_virtualization)
• [Microsoft Learn: Hyper-V Technology Overview](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-technology-overview)