# Virtualization Setup and Deployment

> Chapter 13 of the Courseiva A-PLUS-220-1201 curriculum — https://courseiva.com/learn/a-plus-220-1201/virtualization-setup-and-deployment

**Official objective:** 4.2 — Given a scenario, set up and configure client-side virtualization.

## Introduction

Exam objective 4.2 requires you to set up and configure client-side virtualization. This concept solves the problem of running multiple isolated operating systems on a single physical computer without needing a separate machine for each one. For a 220-1201 candidate, understanding virtualization is crucial because it appears in exam questions about resource allocation, hypervisor types, and deployment scenarios — and because real IT support roles use it every day to test software, simulate networks, and sandbox malware.

## The Apartment Block Water Meter Analogy

A single apartment block has one main water pipe coming into the building. Each apartment has its own kitchen, bathroom, and taps. The building manager installs a smart water meter that can create separate virtual water meters for each individual apartment. Each virtual meter sees its own independent water supply, its own pressure, and its own usage history, even though they all share the same physical pipe. When a tenant moves out, the manager can instantly delete that virtual meter and create a new one for a new tenant without touching any physical plumbing. The manager can also allocate different flow rates to different apartments — 10 litres per minute to one, 20 to another — and monitor each one remotely. One apartment might run Linux, so to speak, by using cold water only, while another runs Windows with hot water. If a tenant overuses water, the manager can throttle theirs without affecting anyone else. The physical pipe and meter never change. This is exactly how a hypervisor creates virtual machines (VMs) on a single physical host. The physical server is the apartment block. Each VM is an apartment with its own operating system and applications. The hypervisor is the smart water meter — it carves up the physical resources (CPU cores, RAM, storage, network) into isolated, configurable virtual versions, each believing it has its own hardware.

The hypervisor does not replace the physical hardware. It sits between the hardware and the VMs, managing access just like the water meter manages flow. The key insight for the 220-1201 exam is that VMs are software-based simulations of a computer. They share the real CPU, memory, and disks of the host machine, but the hypervisor makes sure they do not interfere with each other. If one VM crashes, the others keep running. If you need a test environment for a new app, you clone a VM in seconds instead of buying a second physical server.

## Core explanation

Virtualisation is the process of creating a software-based (virtual) version of a computer — complete with a virtual CPU, virtual memory, virtual hard drive, and virtual network card — that runs inside your real physical computer. The physical computer is called the host, and each virtual computer is called a virtual machine (VM). The software that creates and manages these VMs is called a hypervisor.

Why does virtualisation exist? Before virtualisation, if an IT department wanted to run three different operating systems — say Windows Server for email, Linux for web hosting, and another Linux for a database — they had to buy three separate physical servers. Each server used only a fraction of its capacity, wasted electricity, and took up physical space. Virtualisation lets you consolidate all three operating systems onto one powerful server, each running in its own isolated VM. This saves money, space, and energy. For client-side virtualisation (the focus of this chapter), the same idea applies to a single desktop or laptop. You can run Windows as your main OS and then spin up a Linux VM inside it to learn coding without rebooting.

How does it work? The hypervisor is the heart of virtualisation. There are two types you need to know for the 220-1201 exam:

- Type 1 hypervisor (bare-metal): This runs directly on the physical hardware with no underlying operating system. The hypervisor itself acts as a lightweight operating system. Examples include VMware ESXi, Microsoft Hyper-V (when installed as a role on Windows Server, or on a standalone Hyper-V Server), and Proxmox VE. Type 1 hypervisors are used in data centres and enterprise environments because they offer better performance and stability.

- Type 2 hypervisor (hosted): This runs on top of an existing operating system, like a regular application. The host OS (Windows, macOS, Linux) manages the physical hardware, and the hypervisor runs as a program within that OS. Examples include Oracle VirtualBox, VMware Workstation, and Microsoft Hyper-V on Windows 10/11 (when enabled as a Windows feature). Type 2 is common for client-side virtualisation — a technician can run a VM on their laptop for testing.

Once the hypervisor is installed, you create a VM by allocating virtual resources. You specify how many virtual CPU cores the VM gets (usually 1 or 2 for a lightweight VM), how much RAM (e.g., 2 GB or 4 GB), and the size of the virtual hard disk (e.g., 20 GB or 40 GB). The hypervisor then creates a software container that mimics the hardware of a real computer. You then install an operating system into that VM — exactly the same way you would install it on a physical machine — by booting from an ISO file (a disk image) or a physical installation disc.

A key concept is that the VM's operating system is completely unaware it is virtualised. It thinks it has real RAM, a real hard disk, and a real network card. The hypervisor intercepts every request the VM makes to the hardware (like reading from the hard drive) and translates it to the real physical hardware. This translation adds a small performance overhead, but modern hypervisors are very efficient.

What does virtualisation replace? It replaces the old model of one physical server per workload. In a business setting, virtualisation also enables features like snapshots (saving the exact state of a VM so you can revert to it after a change), live migration (moving a running VM to another host with no downtime), and sandboxing (running untrusted applications in an isolated VM so they cannot harm the host). For the 220-1201 exam, you also need to know about resource requirements: VMs need enough RAM and CPU on the host to run all of them simultaneously. If you allocate 4 GB of RAM to a VM, the host must physically have that RAM available — it is reserved for the VM and cannot be used by the host while the VM is running.

The foundational idea for the exam is that a virtual machine is a container that behaves like a real computer but is entirely software-defined. You can delete it, clone it, move it, and snap it back to a previous state, all without ever touching physical hardware.

## Real-world context

Imagine you are a junior IT support technician at a mid-sized company called 'GreenLeaf Logistics'. Your boss asks you to test a new inventory management application that only runs on Windows 10. However, your work laptop runs Windows 11, and the app is not compatible with Windows 11. You also need to keep using Windows 11 for your daily tasks (email, ticketing system, document editing). Client-side virtualisation solves this problem.

Step by step, here is what you do:

First, you check your laptop's specifications. Your host machine has 16 GB of RAM, a quad-core CPU, and a 512 GB SSD. You estimate the VM needs 4 GB of RAM and 2 virtual CPU cores to run the inventory app smoothly. You ensure hardware virtualisation features (Intel VT-x or AMD-V) are enabled in your laptop's BIOS/UEFI — this is a common exam question trap: if these features are disabled, the hypervisor may refuse to create VMs, or they will run extremely slowly.

Second, you enable Hyper-V on your Windows 11 machine. In Windows 10/11, Hyper-V is a Type 2 hypervisor (though technically it is a Type 1 hybrid when the Hyper-V role is enabled). You go to 'Turn Windows features on or off', check 'Hyper-V', and reboot. Alternatively, if Hyper-V is not available (it requires Windows Pro or Enterprise), you could install Oracle VirtualBox, which runs on any edition.

Third, you create a new VM in Hyper-V Manager. You name it 'Inventory-Test'. You allocate 4 GB of startup memory (remember, this is reserved memory, not dynamic). You create a virtual switch — a software network switch that connects the VM to your physical network. For this test, you choose an external virtual switch so the VM can access the company network and the internet.

Fourth, you attach a Windows 10 ISO file to the VM's virtual DVD drive and start the VM. The VM boots from the ISO and you install Windows 10 normally. Once installed, you install the inventory app inside the VM.

Fifth, you test the app. It works perfectly. You then take a snapshot of the VM — this saves the exact state so you can revert to this clean install if the app's configuration later breaks. You also configure a checkpoint (Hyper-V's version of a snapshot). You document the process.

Later, the developer releases a patch for the app. Instead of applying the patch to your main VM, you clone the VM first (right-click and choose 'Export' in Hyper-V), test the patch on the clone, and only if it works, apply it to the production VM. If the patch breaks something, you simply use the snapshot to roll back in seconds.

This entire workflow — checking hardware requirements, choosing a hypervisor, allocating resources, creating a virtual switch, installing an OS, taking snapshots, and cloning VMs — is exactly what the 220-1201 exam expects you to know. In a real job, you would routinely use these steps for software testing, training environments, and running legacy applications.

## Exam focus

The 220-1201 exam tests client-side virtualisation under objective 4.2 with a specific set of question types. Expect scenario-based multiple-choice questions where you are given a situation — 'A technician needs to run a Linux application on a Windows 10 laptop' — and must choose the correct hypervisor type or configuration step.

Here are the exact concepts they love to test:

- Hypervisor types: You must know the difference between Type 1 (bare-metal, runs directly on hardware, used in servers) and Type 2 (hosted, runs on an OS, used on clients). A common trap question gives you a scenario that describes a Type 1 use case (like a data centre with multiple VMs for different departments) but lists a Type 2 hypervisor as an option. The correct answer is the appropriate Type 1 hypervisor.

- Resource requirements: Questions will ask how much RAM or CPU to allocate to a VM given a host specification. They love to ask what happens if you allocate too much RAM — the host may become unstable, or the VM may not start. Another trap: you must enable hardware virtualisation (Intel VT-x/AMD-V) in BIOS/UEFI before using any hypervisor. If a question describes a VM that fails to start or is very slow, the solution is often this BIOS setting.

- Virtual switches: You need to know the three types of virtual switches in Hyper-V:
  - External: connects the VM to the physical network (internet, other computers)
  - Internal: connects only to the host and other VMs on the same host
  - Private: connects only VMs on the same host, not even the host itself
  A question might ask which switch type to use for a VM that must not have internet access but still communicate with other VMs.

- Snapshots and checkpoints: The exam tests that a snapshot saves the VM's entire state (memory, disk, settings) and allows rollback. They may ask what happens if you apply a snapshot — the VM returns to its exact prior state, losing any changes made after the snapshot.

- File formats: Be familiar with .vhd and .vhdx (virtual hard disk files in Hyper-V) and .vmdk (VMware). A question might ask which file stores the VM's operating system and data.

- Differences between virtualisation and emulation: The exam expects you to know that virtualisation uses the host's CPU directly (with the same architecture), while emulation simulates a different CPU architecture (e.g., running ARM software on an x86 host) and is much slower. Most 220-1201 questions focus on virtualisation, but a trap may mention 'emulation' for a scenario that needs virtualisation.

- Common deployment errors: Over-allocating resources, forgetting BIOS settings, choosing the wrong virtual switch type, or using a dynamic memory setting that conflicts with a performance requirement.

Exam traps to watch for:
  - Confusing Type 1 and Type 2 hypervisors in a scenario.
  - Thinking that a VM's allocated RAM is always available to the host — it is reserved.
  - Believing that VMs on the same host by default can communicate — they need the same virtual switch.
  - Assuming that enabling Hyper-V on a client OS makes it Type 1 — in Windows 10/11 it is effectively Type 2 for the user, though the architecture is hybrid.

Memorise these: Type 1 = bare-metal (ESXi, Hyper-V Server, Proxmox). Type 2 = hosted (VirtualBox, VMware Workstation, Windows Client Hyper-V). The hypervisor allocates physical resources to VMs. VMs are isolated. Check BIOS for VT-x/AMD-V.

## Step by step

1. **Check BIOS/UEFI for hardware virtualisation support** — Before any hypervisor can run, the host CPU must support and have enabled Intel VT-x (for Intel) or AMD-V (for AMD). Enter the BIOS/UEFI at boot (usually by pressing F2, Del, or F10) and navigate to the virtualisation settings. Enable 'Intel Virtualisation Technology' or 'SVM Mode'. Without this, the hypervisor will either fail to install or run at unusably slow speeds. This is the single most overlooked step and a favourite exam trap.
2. **Choose and install a hypervisor** — Based on your host OS and requirements, select a Type 2 hypervisor for client-side use. On Windows Pro/Enterprise, enable Hyper-V via 'Turn Windows features on or off'. On Windows Home or macOS, install Oracle VirtualBox or VMware Workstation. Download the installer from the official site and run it. The hypervisor installs as a regular application and may require a reboot. After installation, you will see the hypervisor management console (e.g., Hyper-V Manager, VirtualBox Manager).
3. **Configure a virtual switch** — Before creating a VM, set up networking. In Hyper-V Manager, open 'Virtual Switch Manager'. Choose: External (connects VM to your physical network and internet), Internal (connects VM to the host only), or Private (connects only between VMs on same host). For most client-side testing, select External so the VM can download updates and access network resources. In VirtualBox, this is done during VM creation by choosing 'Bridged Adapter' or 'NAT'.
4. **Create a new virtual machine and allocate resources** — In the hypervisor console, click 'New' then 'Virtual Machine'. Name the VM (e.g., 'Test-Env'). Choose the generation (Gen 2 for UEFI-based modern OS like Windows 10/11; Gen 1 for legacy OS like Windows 7). Allocate startup memory: for a Windows 10 VM, at least 2 GB (2048 MB), but 4 GB is recommended. Set the number of virtual processors — 1 or 2 for most client VMs. Create a virtual hard disk: choose a size (e.g., 40 GB) and a file type (.vhdx for Hyper-V). Finally, attach an ISO file for the operating system installation.
5. **Install the operating system and configure the VM** — Start the VM. It will boot from the attached ISO. Install the OS exactly as you would on physical hardware — partition the virtual disk, enter licence key, create user account. After installation, install the hypervisor guest additions (e.g., Hyper-V Integration Services, VirtualBox Guest Additions). These drivers improve performance, enable mouse integration, and allow shared folders. Once installed, take a snapshot of the clean OS state. This allows you to revert if you install problematic software later.

## Comparisons

### Type 1 Hypervisor vs Type 2 Hypervisor

**Type 1 Hypervisor:**
- Runs directly on physical hardware without a host OS
- Commonly used in data centres and server environments
- Examples: VMware ESXi, Microsoft Hyper-V Server, Proxmox VE

**Type 2 Hypervisor:**
- Runs as a program on top of an existing operating system
- Commonly used on client desktops and laptops for testing
- Examples: Oracle VirtualBox, VMware Workstation, Hyper-V on Windows 10 Pro

### Virtual Hard Disk (VHD) vs Physical Hard Disk

**Virtual Hard Disk (VHD):**
- A file (e.g., .vhdx) that stores a VM's OS and data
- Can be easily cloned, moved, or snapshotted
- Size is defined at creation and can be fixed or dynamically expanding

**Physical Hard Disk:**
- A physical device with platters or flash chips
- Requires physical installation and cabling
- Cannot be cloned or snapshotted without specialised hardware tools

### External Virtual Switch vs Internal Virtual Switch

**External Virtual Switch:**
- Connects VMs to the physical network and internet
- Uses the host's physical network adapter
- VMs can communicate with other networked devices and the internet

**Internal Virtual Switch:**
- Connects VMs only to the host computer
- Does not use the physical network adapter
- VMs cannot access the internet or other network devices, only the host

### Snapshots (Checkpoints) vs Full VM Backup

**Snapshots (Checkpoints):**
- Captures the VM's memory, disk, and settings at a moment
- Fast to create and requires minimal storage if using differential disks
- Intended for short-term rollback during testing

**Full VM Backup:**
- Copies entire VM files to an external location (e.g., NAS, tape)
- Takes longer and uses more storage space
- Intended for long-term disaster recovery

## Diagram

_This diagram shows how a Type 2 hypervisor sits on top of the host OS and creates three VMs, each with a different virtual switch type for network connectivity._

```mermaid
flowchart TD
    A[Physical Host Hardware] --> B[Type 2 Hypervisor]
    A --> C[Host OS]
    B --> D[VM 1: Windows 10]
    B --> E[VM 2: Ubuntu Linux]
    B --> F[VM 3: Windows Server]
    D --> G[Virtual Switch: External]
    E --> H[Virtual Switch: Internal]
    F --> I[Virtual Switch: Private]
    G --> J[Physical Network / Internet]
    H --> K[Host OS only]
    I --> L[VM-to-VM only]
```

## Common misconceptions

- **Misconception:** Virtual machines and the host operating system always share RAM equally and dynamically, so the host can borrow RAM from a VM when needed. **Reality:** RAM allocated to a VM is reserved by the hypervisor and is unavailable to the host OS. If you allocate 4 GB to a VM, the host only sees 12 GB of its 16 GB total. (Beginner learners often assume that RAM works like a pooled resource that can be reallocated on the fly, similar to how cloud services pool memory. In client-side virtualisation, however, static reservation is the default for reliability.)
- **Misconception:** Any version of Windows 10 or Windows 11 can run Hyper-V. **Reality:** Hyper-V is only available on Windows 10/11 Pro, Enterprise, or Education editions. Windows Home does not include Hyper-V. (Users often think that because a feature is related to Windows, it is available on all editions. The exam tests edition-specific limitations, and beginners overlook the licensing restriction.)
- **Misconception:** If you install a hypervisor on a laptop, the laptop's battery life remains the same because the VMs are not doing anything when idle. **Reality:** Running a hypervisor (even with idle VMs) consumes additional CPU and memory overhead, which reduces battery life. The hypervisor itself uses system resources to manage the VMs, and allocated RAM remains reserved. (People assume that 'idle' software uses negligible power. The hypervisor's background processes and memory reservation have a measurable impact on energy consumption, which is tested indirectly in power-management scenarios.)
- **Misconception:** A virtual machine can use a different virtual switch type for each network adapter, but all adapters in one VM must use the same switch type. **Reality:** A single VM can have multiple virtual network adapters, each connected to a different virtual switch type. For example, one adapter can be External (internet) and another Private (VM-to-VM only). (Beginners think a VM has one 'network connection' and that the switch type applies to the whole VM. The exam tests that you can add multiple virtual network adapters with different configurations within one VM.)

## Key takeaways

- A hypervisor is software that creates and manages virtual machines by allocating physical hardware resources (CPU, RAM, storage, network) to each VM in an isolated manner.
- Type 1 hypervisors run directly on the physical hardware with no underlying OS, while Type 2 hypervisors run on top of an existing operating system.
- For client-side virtualisation on a Windows 10/11 laptop, you must have hardware virtualisation (Intel VT-x or AMD-V) enabled in the BIOS/UEFI.
- Virtual switch types (External, Internal, Private) determine whether a VM can connect to the physical network, only the host, or only other VMs on the same host.
- A snapshot saves the complete state of a virtual machine, including memory, disk contents, and settings, allowing you to revert to that exact state later.
- A VM's allocated RAM is reserved by the hypervisor and cannot be used by the host OS or by other VMs while that VM is powered on.
- Virtual hard disk files (like .vhd, .vhdx, .vmdk) store the operating system and all data for a virtual machine.
- Cloning a VM creates an identical copy that can be used for testing or deployment without affecting the original VM.

## FAQ

**What is the difference between a Type 1 and Type 2 hypervisor for the 220-1201 exam?**

A Type 1 hypervisor runs directly on the physical hardware with no underlying OS (like VMware ESXi). A Type 2 hypervisor runs as a program on top of an existing OS (like VirtualBox on Windows). The exam tests you on knowing which type is used in a given scenario.

**Can I run Hyper-V on Windows 10 Home?**

No. Hyper-V is only available on Windows 10/11 Pro, Enterprise, or Education editions. Windows Home does not include it. You can use Oracle VirtualBox instead.

**What happens if I allocate too much RAM to a virtual machine?**

If you allocate more RAM than the host physically has, the hypervisor will refuse to start the VM, or the VM will fail to boot. If you allocate too much but still within the host's total RAM, the host OS will have fewer resources and may become sluggish or unstable.

**How do I get internet access inside a virtual machine?**

You need to configure the VM's virtual network adapter to use an External virtual switch (Hyper-V) or a Bridged Adapter or NAT (VirtualBox). An External switch connects directly to your physical network adapter.

**What is a snapshot and how do I use it?**

A snapshot captures the complete state of a VM at a point in time, including memory and disk. You can revert to that state later if something goes wrong. In Hyper-V, it is called a 'Checkpoint'. Use it before making risky changes like installing new software.

**My VM is extremely slow. What should I check first?**

First, check that hardware virtualisation (Intel VT-x or AMD-V) is enabled in the BIOS/UEFI. Then verify you have allocated sufficient RAM and CPU cores to the VM. Also ensure you have installed the hypervisor's guest additions drivers inside the VM.

## Check your understanding

1. **What must be enabled in the BIOS/UEFI for a virtual machine to run efficiently with a Type 2 hypervisor?**

   Answer: Hardware virtualisation features such as Intel VT-x or AMD-V must be enabled.

2. **Which hypervisor type is most appropriate for a client-side laptop that needs to run a single test VM while the host OS is Windows 11 Home?**

   Answer: Type 2 hypervisor, such as Oracle VirtualBox, because Hyper-V is not available on Windows Home.

3. **What happens to the memory allocated to a VM when the VM is powered off?**

   Answer: The memory is released back to the host and becomes available for other processes and VMs.

4. **A technician needs two VMs on the same host to communicate with each other but not with the host or the internet. Which virtual switch type should be used?**

   Answer: A Private virtual switch should be used, as it allows communication only between VMs on the same host.

5. **What is the purpose of installing guest additions (e.g., Hyper-V Integration Services) inside a VM?**

   Answer: Guest additions improve performance, enable mouse integration, allow shared folders, and synchronise time between the host and VM.

---

Interactive version with quiz and diagrams: https://courseiva.com/learn/a-plus-220-1201/virtualization-setup-and-deployment