You cannot learn to drive by reading the car manual. At some point you have to sit in the seat, stall the engine a few times, and get the feel of it. A home lab is your driving seat. It is a flight simulator for infrastructure work: a safe place to break things, panic a little, fix them, and actually understand why the steps in this series matter. Every engineer worth hiring has one.
For a while this got harder. When Broadcom moved everything to subscriptions, the free tools many of us learned on disappeared. The good part of the 2025 story is that they came back. Today you can build a working VMware lab without paying anyone, and this part walks you through exactly how.
The tools are free again, and that matters
Two changes put real VMware back within reach of a student. First, in November 2024 Broadcom made VMware Workstation Pro free for everyone, including personal, educational and commercial use. No license key, no trial clock. You download it from the Broadcom support portal with a free account and run it on Windows or Linux. Workstation lets you run virtual machines on your own laptop, including a trick we will use in a moment.
Second, the free ESXi hypervisor returned. Broadcom pulled the free edition in February 2024, then brought it back in April 2025 as part of ESXi 8.0 Update 3e. It carries an embedded license with the same lab-friendly features as the old free version. So you can install real ESXi, the same hypervisor from Part 3, at no cost. The history is worth knowing because it explains why older guides told you free ESXi was dead. It is alive again.
Two ways to build your lab
There are two sensible routes, and a fresher should usually pick the first one. The trick that makes a single laptop enough is called nested virtualization: you run ESXi as a virtual machine inside Workstation, then run more virtual machines inside that. A hypervisor running on top of a hypervisor. It is slower than real hardware, but for learning it is perfect.
| Approach | You need | Best for |
|---|---|---|
| Nested in Workstation | One laptop or PC, free Workstation Pro, plenty of RAM | Almost every fresher. Start here. |
| ESXi on a spare physical box | A second machine you can wipe, free ESXi 8.0U3e | When you have old hardware lying around and want it always on |
Start with nested in Workstation. It keeps everything on one machine, you can snapshot the whole lab and roll back when you break it, and you do not need a spare computer. Move to a physical ESXi box later if you want a lab that runs all the time.
The hardware that actually matters
Freshers often worry about the wrong thing. They ask about the CPU when they should ask about memory. Any modern processor with virtualization extensions turned on, Intel VT-x or AMD-V, will do the job. That setting sometimes needs enabling in the BIOS, and a lab that refuses to power on a 64-bit VM is almost always this switch being off. The real limit is RAM.
Why RAM, not CPU, decides your lab
Here are the real numbers. ESXi 8 wants at least 8 GB of memory just to install. The vCenter appliance, even in its smallest Tiny size, asks for 14 GB of RAM on its own. Add the laptop's own operating system on top, and you can see how a 16 GB machine runs out of room fast. This is the single fact that decides whether your lab is pleasant or painful. A laptop with 32 GB is comfortable. With 16 GB you can still learn plenty, as long as you are careful about what you run at once.
Gotcha
vCenter is the memory hog, not ESXi. People assume the hypervisor is the heavy part and are surprised when the management appliance demands 14 GB by itself. That number is exactly why the next section tells you to leave vCenter out of your very first lab.
Worked example
Say you have a laptop with 32 GB of RAM. A sensible slice for a first lab looks like this.
Windows or Linux host: about 6 GB.
Nested ESXi virtual machine: 10 GB, which lets it run a couple of small test VMs inside.
A second nested ESXi (for later, to practice vMotion): another 10 GB.
That leaves a little headroom and no vCenter yet. Two ESXi hosts and some guests on a single 32 GB laptop is a genuinely useful lab.
Build your first lab this weekend
Here is the shortest path from nothing to a running VM. None of it costs money.
- Make a free Broadcom support portal account and download VMware Workstation Pro. Install it.
- From the same portal, download the free ESXi 8.0U3e ISO.
- In Workstation, create a new virtual machine, choose the ESXi installer type, point it at the ISO, and give it at least 8 GB of RAM and two CPUs.
- Power it on and install ESXi. When it finishes, it shows a grey and yellow console screen with an IP address. That screen is the same one you saw in Part 3.
- Open that IP address in your browser to reach the ESXi host client, then create a small Linux VM inside it. You have just run a VM on a hypervisor that is itself a VM.
Two limits of the free ESXi edition are worth knowing before they confuse you. A single VM can use at most 8 vCPUs, which is fine for a lab. There is no virtual TPM, so you cannot run a Windows 11 install that insists on TPM. And the management APIs are read-only, so automation tools that try to change the host will fail. None of these block learning the fundamentals. They only bite if you try to push the free edition into things it was never meant for.
Skip vCenter at first, yes really
Most home lab guides tell you to deploy vCenter on day one. I disagree for a beginner, and here is why. vCenter eats 14 GB of RAM, takes a while to deploy, and adds a layer of complexity before you have even got comfortable with a single host. Learn ESXi standalone first. Create VMs, take snapshots, poke around the host client until it feels familiar. Add vCenter only when you specifically want to practice the things that need it, like vMotion, HA or DRS from the earlier parts. Bringing in vCenter too early is the most common way freshers overwhelm themselves and give up. Earn it.
Real interview question
"Do you have a home lab, and what have you built in it?"
This comes up constantly for fresher infrastructure roles, and a real answer beats any certificate. Describe your actual setup: Workstation on your laptop, a nested ESXi host, a couple of test VMs, and one concrete thing you broke and fixed. The story of fixing a VM that would not boot tells an interviewer far more than reciting a feature list. If you do not have a lab yet, this part is your reason to build one before your next interview.
Try it yourself
Build the five-step lab above, then do one thing more: take a snapshot of your guest VM, delete a file inside it, and roll back to the snapshot to bring the file back. That single exercise makes snapshots from Part 8 click in a way no diagram can.
You got it right if the file is gone after the delete and present again after the rollback. If your nested ESXi refuses to power on a VM, check that virtualization extensions are enabled in your laptop's BIOS. That is the usual culprit.
Five things to actually do once it boots
Installing ESXi is the start, not the finish. The learning happens when you use the lab to repeat the ideas from this series until they stop feeling like theory. Here is a short practice list, each item tied to an earlier part, that walks a beginner from clicking around nervously to actually knowing what they are doing. Work through them in order over a few evenings.
- Create a VM from scratch and install a small Linux distro on it, choosing the vCPU, memory and disk sizes yourself (Part 5). Notice how little a basic Linux guest actually needs to run.
- Take a snapshot before a change, break something inside the guest on purpose, then roll back (Part 8). This is the safety net you will lean on in real work, so build the habit early.
- Turn that VM into a template, then deploy a second guest from it (Part 8). Watch how much faster the second one is to stand up than the first.
- Add a second virtual disk to a VM and a second datastore on the host (Part 6). Move a VM file between datastores so that storage stops being an abstract word.
- Create an extra virtual switch and port group, put two VMs on it, and ping between them (Part 7). Networking clicks the moment your own packets actually move.
- Power off the nested ESXi host while a guest is running, then power it back on (Part 10). See what survives and what does not, and you will understand in your gut why HA exists.
- When one host feels easy, deploy a second nested ESXi and the vCenter appliance, add both hosts, and try a vMotion between them (Part 9). That is the moment the whole series comes together.
Do those seven and you will have touched compute, storage, networking and recovery with your own hands. That is the real gap between someone who has read about VMware and someone who can sit down at the console without freezing. Nobody expects a fresher to be fast. They do quietly notice who has obviously done it before and who is seeing the screen for the first time.
In practice
Keep a plain text file of what you tried and what broke each evening. When an interviewer asks about your lab, that log turns into specific stories, and a specific story beats a generic answer every single time.
FAQ
Is VMware Workstation really free now?
Yes. Since November 2024 Workstation Pro is free for personal, educational and commercial use, with no license key. You download it from the Broadcom support portal with a free account. The catch is that the free product comes with no official support.
How much RAM do I need to start?
You can begin a single-host nested lab on 16 GB if you skip vCenter and keep your VMs small. For a smoother experience with two hosts or vCenter, aim for 32 GB. Memory matters far more than the speed of your CPU here.
Can I run Windows 11 in my free ESXi lab?
Not if the install requires a TPM, because the free ESXi edition does not provide a virtual TPM. You can still run Linux guests and older Windows freely, which is plenty for learning. For a Windows 11 guest, run it directly in Workstation instead, which does support a virtual TPM.
Do I need a server or special hardware?
No. A regular laptop or desktop with enough RAM and virtualization extensions enabled is all you need for the nested approach. A spare physical machine is only worth it later, when you want a lab that stays on all the time.
References
- VMware Cloud Foundation Blog: Fusion and Workstation now free for all users
- Broadcom Knowledge: ESXi 8.0 Update 3e available as a free hypervisor
- Broadcom Knowledge: Minimum memory requirements for vCenter Server Appliance 8.0
About The Author
DrJha