What is virtualization?

You need a place to practise where breaking things is safe and legal. Virtualization gives you exactly that: a disposable second computer you fully own, living inside your real one.

The core idea

Virtualization is a clever trick: running a whole second computer inside your real one, in a window. That simulated computer is called a virtual machine (VM). It has its own operating system, its own files, its own network settings — but it's really just software running on your actual machine.

[Host, hypervisor, and guest VMs]

Why this is perfect for learning security

  • It's safe. If you break the VM — infect it, misconfigure it, delete everything — your real computer is untouched. You just reset the VM.
  • It's isolated. Attacks and tools stay inside the VM's window and can't reach your real files (as long as you set the network correctly, which we'll cover).
  • It's free. The software that creates VMs costs nothing.
  • It's disposable and repeatable. Take a snapshot (a saved state) and jump back to it instantly, or throw a VM away and make a fresh one in minutes.

The vocabulary

  • Hypervisor — the software that creates and runs virtual machines. The beginner-friendly free one is VirtualBox (by Oracle). Alternatives: VMware Workstation Player (free for personal use), Parallels (Mac), Hyper-V (Windows Pro), KVM (Linux).
  • Host — your real computer (the one running VirtualBox).
  • Guest — the virtual machine running inside it (your Kali, in a moment).
  • Snapshot — a saved photo of a VM's state you can restore later.
  • VM image — a downloadable pre-built VM (like the Kali OVA you'll use).

Type 1 vs Type 2 hypervisors

  • Type 1 (bare-metal) — runs directly on the hardware, no host OS underneath. VMware ESXi, Hyper-V Server. Used in data centres.
  • Type 2 (hosted) — runs as an app on top of your normal OS. VirtualBox is Type 2. This is what you'll use.

Type 2 is much easier to set up; Type 1 is more efficient but industrial.

Virtual networking modes — a preview of a setting you'll configure soon

When you create a VM, you'll choose how it connects to networks — a setting worth understanding conceptually now, since Path 16's cloud networking lesson and this course's own lab setups reference it constantly:

  • NAT — the VM can reach the internet, but your host and other devices can't directly reach into the VM. The default, and the safest choice for most learning labs.
  • Bridged — the VM appears as its own independent device directly on your physical network, with its own IP address, as if it were a separate physical computer plugged into your router.
  • Host-only — the VM can only talk to your host machine (and other host-only VMs), completely cut off from the wider internet — exactly the isolated setup Path 17's malware analysis lessons insist on for safely running untrusted samples.

Choosing the right mode for the right task is a genuinely important habit: host-only for anything potentially dangerous (malware analysis), NAT for general safe practice, and bridged only when you specifically need the VM to look like an independent device on your real network.

Containers vs. virtual machines — a term you'll hear constantly later

You'll frequently hear "containers" (Docker, referenced throughout Path 16's containers/Kubernetes lab) mentioned alongside VMs — worth distinguishing now even briefly. A VM virtualizes an entire computer, including its own full operating system kernel, making it heavier but very strongly isolated. A container instead shares the host machine's kernel, packaging just an application and its dependencies — much lighter and faster to start, but with a thinner isolation boundary between container and host than a full VM provides. This tradeoff — VMs prioritize strong isolation, containers prioritize speed and efficiency — is exactly why Path 16's container security lab spends real time on container escape techniques: the isolation boundary, while real, is genuinely weaker than a full VM's.

The professional habit

Real security professionals never run risky tools or open suspicious files on their real machine. They always use a VM. You're about to learn the exact same setup the pros use daily. Building this lab is a genuine milestone.

A VM is a sealed, transparent box on your desk. You can do anything inside the box — even set off a firework — and your desk stays clean. If the box gets wrecked, you grab a fresh identical box. That safety is what makes fearless learning possible.

System requirements to check

Before you install VirtualBox, make sure your machine can handle it:

  • RAM: 8 GB or more is comfortable. 4 GB works but tight.
  • Disk: 30–40 GB free.
  • CPU: must support hardware virtualization (VT-x on Intel, AMD-V on AMD) — nearly all modern CPUs do. May need to enable in BIOS (we cover this next lesson).
  • If you have less: use TryHackMe or Hack The Box in your browser instead. The whole course still works.

In virtualization terms, what do we call your real computer, and what do we call the virtual machine running inside it?

Show answerYour real computer is the host; the virtual machine is the guest.

Key terms

  • Virtualization — running a computer inside a computer.
  • Virtual machine (VM) — the simulated computer.
  • Hypervisor — software that runs VMs (e.g., VirtualBox).
  • Host / guest — your real machine vs the VM.
  • Snapshot — a restorable saved state of a VM.
  • Type 1 / Type 2 — bare-metal vs hosted hypervisor.

Recap

  • Virtualization runs a second computer (a VM) inside your real one.
  • It's safe, isolated, free, and disposable — perfect for practice.
  • VirtualBox (Type 2 hypervisor) runs the VM; your machine is the host, the VM is the guest.
  • Pros always test in VMs — you're about to do the same.

References

Next up → Install VirtualBox