Lab Environments Guides
An overview of the lab environment landscape — hypervisor foundations, network emulation platforms, vendor-official all-in-one tools, container-native labs, and cloud-hosted options — with deep dives on individual platforms to follow.
Posts
-
Lab Environments Part 1: Why Lab, and How to Choose
Opening a short series on the lab environment landscape with the question that actually decides which tool you want: what do you need the lab to be, not which GUI looks nicest.
-
Proxmox Deep Dive Part 1: Architecture and Installation
Opening the promised Proxmox deep dive: what Proxmox VE actually is under the hood (Debian, KVM, LXC, pmxcfs), the subscription model recapped in more depth, and how the pve host behind this site's own labs got its start.
-
Lab Environments Part 2: The Hypervisor Foundation
Before EVE-NG, GNS3, or CML, something has to run them. Proxmox, ESXi, and VMware Workstation compared as the compute layer underneath the rest of this series.
-
Proxmox Deep Dive Part 2: Storage Architecture
Every storage type Proxmox supports, what content each one can actually hold, and the local-versus-shared distinction that quietly decides whether live migration and HA are even possible later.
-
Lab Environments Part 3: Network Emulation Platforms - EVE-NG, GNS3, and pnetlab
The category most people mean by "network lab": real vendor images wired into a GUI topology, running on top of the hypervisor layer from Part 2. EVE-NG's 2026 licensing shift, the pnetlab fork it created room for, and where GNS3 sits outside all of it.
-
Proxmox Deep Dive Part 3: ZFS, the Default Recommendation
Pools, RAIDZ versus mirrors, the RAM math ZFS actually needs, and the one setting (ARC sizing) that trips up more homelab builds than any other single ZFS decision.
-
Lab Environments Part 4: Vendor-Official All-in-One - Cisco Modeling Labs and Packet Tracer
Two Cisco-only platforms that solve the image licensing problem a different way: they ship the images, or don't need real ones at all. CML's 2026 free tier, and where Packet Tracer's simulation approach is a feature rather than a compromise.
-
Proxmox Deep Dive Part 4: Networking - Bridges, VLANs, and SDN
From the single vmbr0 bridge the installer creates, through VLAN-aware bridges and bonding, to the newer SDN stack with EVPN and BGP over VXLAN, and where the extra complexity is actually worth it in a homelab.
-
Lab Environments Part 5: Container-Native - containerlab and netlab
No GUI topology canvas, no full VMs: network operating systems as containers, topology as a YAML file. The same primitives the Container Networking and OSPF on Linux series already used, applied to network-OS containers instead of app containers.
-
Proxmox Deep Dive Part 5: The Built-In Firewall
Three separate levels, datacenter, node, and VM, each guarding a different kind of traffic, plus security groups and IP sets for keeping rule sets manageable as a homelab grows.
-
Lab Environments Part 6: Cloud-Hosted Labs, and Picking One
Closing the overview: renting the compute layer instead of owning it, a comparison across all five categories, and a plain decision framework. Proxmox is next, with the deep dives to follow.
-
Proxmox Deep Dive Part 6: VMs vs LXC Containers
Full hardware virtualization and OS-level containers are both first-class in Proxmox. The actual decision between them, and why unprivileged containers should be the default rather than the exception.
-
Proxmox Deep Dive Part 7: Clustering and Quorum
What actually happens when a second node joins: corosync, pmxcfs synchronization made real, the quorum math behind how many nodes can fail before the cluster stops trusting itself, and why two nodes is a genuinely awkward number.
-
Proxmox Deep Dive Part 8: High Availability
HA groups, the watchdog-based fencing that makes automatic failover safe, and an honest answer to whether HA is worth the complexity in a homelab at all.
-
Proxmox Deep Dive Part 9: Ceph Hyperconverged Storage
Ceph turns the cluster's own nodes into shared storage, no external NAS required, at the cost of a genuinely higher complexity and hardware floor than most homelabs actually need.
-
Proxmox Deep Dive Part 10: Backup and Disaster Recovery
vzdump's three backup modes, retention scheduling that actually matches how homelabs get used, and Proxmox Backup Server as the companion product worth running instead of vzdump alone.
-
Proxmox Deep Dive Part 11: PCI and GPU Passthrough
Handing a real GPU or PCI device directly to a VM through IOMMU and VFIO, the IOMMU grouping problem that catches most first attempts, and the use cases that actually justify the setup work.
-
Proxmox Deep Dive Part 12: Users, Permissions, and the API
Realms, roles, and ACLs underneath the GUI, scoped API tokens for automation, and where Terraform and Ansible actually fit against the same API surface the web GUI itself uses.
-
Proxmox Deep Dive Part 13: Monitoring, Maintenance, and Homelab Best Practices
Closing the deep dive: watching the whole stack with Prometheus and Grafana, ongoing repository and certificate maintenance, and a homelab best-practices checklist pulling every part of this series into one place.