How to Set Up a Free VirtualBox Lab for CompTIA & CCNA

If you are studying for a CompTIA, Cisco, Linux, or cybersecurity certification, the single best thing you can do is build a hands-on lab. The good news is you do not need a second computer, expensive kit, or any paid software. With a free tool called VirtualBox, you can run Ubuntu, Kali Linux, Windows 11, and Windows Server 2025 side by side on the computer you already own and practice everything safely.

This guide walks you through the whole setup from scratch, the right way, and flags the mistakes that trip up beginners (black screens, broken file sharing, and networking confusion) so you can avoid them.

What is VirtualBox?

VirtualBox is a free hypervisor – software that lets your computer run other complete computers inside windows on your desktop. Each one is called a Virtual Machine (VM). Two words you will see throughout this guide:

• Host – your real, physical PC and its operating system (Windows, macOS or Linux). This is what VirtualBox installs onto.
• Guest – an operating system running inside a VM (for example, Ubuntu or Windows Server). It behaves exactly like a real PC, with its own disk, memory, and network card, but it is all simulated in software.

Why use VirtualBox for certification study?

• It is completely free and open source – run as many VMs as your PC can handle.
• Cross-platform – it runs on Windows, macOS and Linux hosts, so the labs are identical on any machine.
• Safe and isolated – break, hack or wipe a guest and your real PC is untouched. Mistakes cost you nothing, which is how you learn fastest.
• Snapshots – save a perfect moment and roll back in seconds when a lab goes wrong.
• Real networking – build multi-machine networks, such as a server and several clients talking to each other.
• Exam-realistic – you practice the hands-on skills that a large share of your exam marks depend on.

Before you start: can your PC run it?

VirtualBox needs CPU virtualization switched on. Intel calls this VT-x; AMD calls it AMD-V (or SVM Mode). This is the number one reason a beginner’s first VM refuses to boot.

If it says Disabled, you need to switch it on in your computer’s BIOS / UEFI firmware (not inside VirtualBox):

1. Reboot and tap the setup key during boot (often Del, F2, or F10).
2. Look under CPU or Advanced settings for Intel VT-x, Virtualization Technology, or AMD-V / SVM Mode.
3. Set it to Enabled, then save and exit.

Step 1 – Download and install VirtualBox

1. Go to virtualbox.org – and only the official site, because VirtualBox is a common target for fake download pages.
2. Click Downloads, then choose your host platform (Windows, macOS/Apple Silicon, or Linux).
3. Run the installer and accept the defaults. Your network will blink off for a second or two as it installs the virtual adapters – that is normal.

Do not skip the Extension Pack

Most tutorials leave this out. The basic install is missing features that modern IT labs rely on. From the same download page, grab the VirtualBox Extension Pack, then install it via File → Tools → Extension Pack Manager → Install. It adds:

• USB 2.0 and USB 3.0 device support
• Disk encryption for your VMs
• VirtualBox remote display (RDP)
• NVMe and PXE network-boot support

Step 2 – Get your lab operating systems (ISOs)

An ISO is just a downloadable disk image that the VM installs from. These four cover almost everything you will study, and they are all free:

Both Microsoft editions are fully featured and need no license key – just download from the Microsoft Evaluation Center.

Step 3 – Create your first virtual machine

1. Click New. Give the VM a clear name (for example, WS2025-DC) – the name is how you will find it once you have several.
2. Select the ISO; VirtualBox usually detects the operating system type and version automatically.
3. Set the memory and CPU (see the rule below), then create a virtual hard disk.

How much RAM and CPU should I give a VM?

As a guide: Ubuntu or Kali 2–4 GB; Windows 11 about 4 GB; Server 2025 about 4 GB. If you run several VMs at once, it is the combined total that has to leave the host comfortable.

Dynamic vs fixed storage

• Dynamically allocated (recommended) – the disk file starts tiny and grows only as the guest fills it. Best for laptops with limited space. In the current VirtualBox interface, this is the default; you simply leave Pre-allocate Full Size unticked.
• Fixed size – reserves the whole amount on your real drive immediately. Slightly faster, but it eats disk straight away (tick Pre-allocate Full Size).

Step 4 – VirtualBox networking explained

Choosing the right networking mode is what makes a lab work or fail. Each VM has its network set under Settings → Network. Here is what each mode does and when to use it.

NAT – the default (one VM, internet only)

The out-of-the-box setting. The VM shares the host’s internet connection, which is ideal for a single machine that just needs to connect to the internet for updates. The catch: VMs on NAT are isolated from each other, and the host cannot easily reach a VM without port forwarding.

NAT Network – VMs talk to each other and get internet

The multi-VM version of NAT is the one you will reach for most in a real networking lab. Several VMs share a named network so they can all communicate with each other and reach the internet simultaneously. As with plain NAT, the outside world cannot initiate a connection to them without port forwarding. Create it once under File → Tools → Network Manager.

Bridged Adapter – the VM joins your real network

The VM behaves like a separate physical device on your home network and gets its own IP address from your router, just like your phone or laptop. Now your host, the VM and other devices can all see each other – great for SSH or RDP into a VM. Note that some work or campus networks block extra devices, and bridging exposes the VM to your LAN.

Internal Network (“intnet”) – the lab workhorse

A private, isolated network that only your chosen VMs share – no host, no internet. Give every VM in the lab the same internal network name (for example, intnet), and connect them to a private switch. This is the perfect, safe sandbox for a multi-machine lab such as Active Directory: put the domain controller and the client on the same network with static IPs, and nothing leaks onto your real network.

Host-only – host and VMs talk, no internet

A private network between your host and the VMs only. They can all talk to each other, but there is no internet, and nothing is exposed to your real LAN. Useful for managing or connecting to your VMs from the host without exposing them to the outside world.

Using more than one adapter

Each VM has up to four network adapters (Settings → Network, Adapter 1–4 tabs), and each can be a different type – so one VM can sit on several networks at once, exactly like a real router or server. Most VMs need just one; add a second when a machine must be on two networks at once. The classic combination: Adapter 1 = NAT / NAT Network (internet) and Adapter 2 = Internal Network / intnet (isolated lab), so a domain controller can download updates and serve the private client network.

Step 5 – Installing Windows 11 (Evaluation)

1. Download the Windows 11 Enterprise Evaluation ISO from the Microsoft Evaluation Center (90 days, no key required).
2. Create a new VM, select Microsoft Windows 11 (64-bit), and allocate at least 4 GB of RAM and 60 GB of disk space.
3. Important: Windows 11 requires TPM and Secure Boot; otherwise, the installer will display “This PC can’t run Windows 11.” In Settings → System, set the boot firmware to EFI, enable Secure Boot, and set TPM to v2.0 (VirtualBox 7 provides a virtual TPM).
4. Start the VM and boot from the ISO. Choose your language, then Install now.
5. When asked for a product key, choose I don’t have a product key, then select the Windows 11 Enterprise (Evaluation) edition.
6. Accept the license, choose Custom install, select the virtual disk, and let it install (it will reboot a few times).
7. Complete the setup, creating a local account when prompted. A handy lab convention is to use the password Password123! across your lab VMs so you never get locked out mid-exercise.
8. After installation, remove the ISO from the virtual optical drive so it boots from disk.

Step 6 – Installing Windows Server 2025 (Evaluation)

1. Download the Windows Server 2025 Evaluation ISO from the Microsoft Evaluation Center (180 days).
2. Create a new VM, type Microsoft Windows 2022/2025 (64-bit), with 4 GB of RAM and a 60 GB disk.
3. Skip the unattended install. When VirtualBox offers an automatic installation, choose to skip it so you boot the real Windows installer yourself.
4. Boot from the ISO and start the installer.
5. When choosing the edition, pick Windows Server 2025 Standard (Desktop Experience) – not the plain edition without Desktop Experience.
6. Accept the license, choose Custom install, select the disk, and let it install.
7. Set a strong Administrator password when prompted (the lab convention is Password123!).
8. Remove the ISO from the virtual drive afterward.

Ubuntu and Kali install the same way – boot from the ISO and follow the normal installer; both take a few minutes.

Step 7 – Install Guest Additions

Guest Additions is a small driver package you install inside the guest, and it transforms how the VM feels to use. It is the proper fix for tiny windows and 4 K monitor scaling, far better than manual workarounds. With the VM running, go to Devices → Insert Guest Additions CD image, run the installer inside the guest, and reboot. You then get:

• Dynamic resolution – the guest auto-resizes when you resize the window.
• Shared clipboard – copy a command on your host and paste it into the VM (a big time-saver).
• Drag & drop and shared folders – move files between host and guest easily.

Pro lab management: snapshots, clones, and groups

Snapshots – your undo button

A snapshot saves the exact state of a VM at a moment in time. Take one before anything risky – editing routing, Active Directory or the registry – and if the lab breaks, you can restore it in seconds. Tip: Take a snapshot right after a clean install plus Guest Additions and keep it as your known-good baseline.

Linked clones – save disk space

A full clone is a complete, independent copy that uses the disk space again. A linked clone shares the original’s disk and only stores the differences, so you can spin up several VMs using a fraction of the space – just keep the parent VM, because the linked clones depend on it.

Grouping

Once you have several VMs, select them, right-click, and choose Group to organize them by lab or certification (for example, “CompTIA Security+ Lab” or “CCNA Lab”). You can then start, stop, or snapshot a whole group at once.

You’re ready – now go and use it

You now have a professional-grade IT lab: VirtualBox and the Extension Pack installed correctly, virtualization enabled, Ubuntu, Kali, Windows 11 and Windows Server 2025 ready to run, the networking modes understood, Guest Additions installed, and snapshots and groups to manage it all.

The lab is the tool, not the goal. Head over to 101labs.net and start the hands-on labs that match the environment you have just built – CompTIA, Cisco, Linux, and cybersecurity. Everything you learn, you can now actually do.