Showing posts with label Proxmox. Show all posts
Showing posts with label Proxmox. Show all posts

Snapshot vs Backup: How to Prove Your Home Server Backup Actually Works

Illustration comparing a snapshot on the same server with backups stored elsewhere and a tested restore

You took a snapshot of your home server before an update, so you feel safe. Then the disk dies, and the snapshot dies with it. That is the core of snapshot vs backup. A snapshot is a quick undo point that lives on the same storage as the original. A backup is a separate, complete copy you can restore somewhere else. You need both, and you only know a backup works after you restore it once.

Who this is for: you run a home server, a NAS or a Proxmox box with things you care about, such as family photos, a password vault or a smart home setup. Who it is not for: you only run throwaway test machines that you can rebuild in ten minutes. You can still read on, but you need less of it.

What a snapshot is

A snapshot freezes the state of a virtual machine (VM) or a disk at one moment. After that, the system writes new changes to a separate layer. If an update goes wrong, you roll back, and the VM returns to the frozen state, usually quickly. A rollback also throws away everything written since the snapshot, such as new photos or passwords. Save or back up recent changes before you roll back.

Proxmox can snapshot both VMs and containers, if the storage supports it. The guide to containers vs virtual machines explains the two. Snapshots are great for one job: a short-term undo button before a risky change. Take one before an upgrade. Test the upgrade. Then delete the snapshot when you are happy.

What a backup is

A backup is a full, independent copy of your data, stored somewhere else. It does not need the original disk to exist. If the server burns, you can restore the backup onto new hardware.

In Proxmox VE, the docs say plainly that its backups "are always full backups", with the VM or container configuration and all data. See the Proxmox VE backup and restore docs. Tools such as Proxmox Backup Server then store those backups in a smart way, so later runs only send what changed.

Snapshot vs backup: four reasons a snapshot is not a backup

  1. It lives on the same storage. A snapshot sits on the same disk or storage pool as the VM. If that disk fails, you lose the VM and every snapshot at once.
  2. It depends on the original. Most snapshots store only the changes since the freeze. They are not a complete copy, so they mean nothing without the original disk.
  3. It shares the same mistakes. Delete the VM by accident, and its snapshots usually go too. Ransomware (malware that locks your files and asks for money) that reaches the host can reach the snapshots too.
  4. It is not off-site and not long-term. Snapshots stay in the house, on the box. Old snapshots also grow as data changes, and they can slow the VM and fill the disk.

One more trap. An older Proxmox wiki page on live snapshots notes that "snapshots are not included in the backup", and current backup logs still report snapshots as not included. So a backup does not save your snapshot history either. Treat the two as separate tools.

A word on naming: Proxmox has a backup mode called "snapshot mode". It is still a real backup. The name only means the backup runs while the VM keeps working, so you have little downtime.

QuestionSnapshotBackup
Where does it live?Same storage as the VMSeparate storage, ideally another box and another place
Is it a complete copy?Usually no, it records changesYes
Survives a dead disk?NoYes, if stored elsewhere
Best useUndo before an updateRecover from loss, theft, fire or ransomware
How long to keepHours or daysWeeks, months or longer, by a plan

The 3-2-1 backup rule, in plain words

The US Cybersecurity and Infrastructure Security Agency (CISA) gives a simple rule. On its guide to backing up business data, it says to keep:

  • 3 copies of important files,
  • on 2 different types of storage (like a hard drive and the cloud),
  • with 1 copy stored off-site, away from your home or business.

For a home server, that can look like this. The live data sits on the server. A backup sits on a second box or a USB drive at home. A third copy sits off-site, such as a drive at a relative's house or an encrypted cloud copy. CISA also tells you to test your backups, make sure you can restore data fully and partly, and be able to roll back at least seven days. That test is the part most people skip.

Some app makers say the same. The Immich photo project's own README warns you to always follow a 3-2-1 backup plan for your photos and videos. If you followed the guide to self hosting in 2026, this is the step that makes it safe.

What you need for a first restore drill

  • Hardware: your server, plus a separate place for backups. A second small box, a NAS or an external drive all work. Do not count a second folder on the same disk.
  • Software: any backup tool that can restore. This guide uses Proxmox VE with Proxmox Backup Server as the worked example. On Synology, Unraid or TrueNAS, use the same drill: restore to a new location, never over the original, then check your marker.
  • Skill: you can click through the Proxmox web page and start a VM.
  • Time: set aside an evening. A small test VM restores faster than a big one.
  • Cost: Proxmox Backup Server is free and open source (AGPLv3), per its official introduction. Optional paid subscriptions exist for support and the enterprise update channel. Your real cost is the backup disk or second box. Check current terms on the Proxmox site, as of October 2026.

Proxmox Backup Server stores incremental, deduplicated backups (it skips data it already has), can encrypt them on your side before they leave the host, and checks them with checksums. It can also run "verify jobs" on a schedule to catch damaged backup data. It is new to many home users, so read its docs before you trust it with irreplaceable files. For the bigger picture of where this box fits, see the home server setup guide.

How to test a backup restore: a step-by-step drill

The goal is simple. Prove that a real backup turns back into a working machine, without touching the live one.

  1. Pick a test subject. Choose one VM or container that matters but is small. A password vault or a photo app is a good choice.
  2. Plant a marker. Create a small text file inside it, or note one recent photo or record. You will look for it after the restore.
  3. Run a backup now. In Proxmox VE, open the VM, go to Backup, and choose "Backup now" to your Proxmox Backup Server storage. Wait for the task to finish with no errors.
  4. Verify the backup. On Proxmox Backup Server, run a verify on that backup, or check that your scheduled verify job passed.
  5. Restore to a new ID. In Proxmox VE, open your backup storage, select the backup and choose Restore. Give it a new, unused VM ID, so you never overwrite the live VM. Check "Unique" so the copy gets new network hardware (MAC) addresses. Leave "Start after restore" unchecked.
  6. Keep it off the network. Before you start the copy, open its Hardware tab and disconnect its network card. Two copies of the same server on one network can clash. In Options, also turn off "Start at boot", or the copy may start with the host after a reboot.
  7. Start it and check it. Boot the restored VM. Log in from the console. Find your marker file or record. Open the app if you can.
  8. Try a single-file restore. On the backup storage, use the "File Restore" button to browse inside the backup and download one file. This is the restore you will need most often.
  9. Write down the results. Record the date, what you restored, how long it took and any problem.
  10. Clean up. Delete the test VM when you are done, so it does not run by mistake later.

If you prefer the command line, Proxmox VE also restores with qmrestore for VMs and pct restore for containers. Both accept a new ID. Check the docs for the exact options on your version.

The risky bit: how restore drills go wrong

  • Restoring over the live VM. Always use a new VM ID for a drill. One wrong click on the original ID replaces your live machine with an older copy.
  • Two servers, one network. A restored copy can grab the same IP address or talk to the same devices. Keep it disconnected.
  • Backups on the same disk. A "backup" stored next to the original fails with it. Move it to another device.
  • Lost encryption key. If you encrypt backups and lose the key, nobody can restore them. Store the key in at least two safe places, away from the server.
  • Snapshots left running. A forgotten snapshot keeps growing and can fill the disk. Delete snapshots once an update proves fine.
  • No off-site copy. Fire, flood and theft take every device in the house. Proxmox Backup Server can sync to a second Proxmox Backup Server (a "remote") with a sync job, which is one way to get a copy off-site.

The recovery step: make the drill a habit

One drill proves today's backup. It does not prove next month's. Put a reminder in your calendar and repeat the drill on a schedule. Rotate which VM you test. After any big change (new disk, new backup target, major upgrade), run a drill again. The guide to what Proxmox VE is covers the platform itself if you are still choosing.

Printable restore drill checklist

  1. I have 3 copies of my important data, on 2 types of storage, with 1 off-site.
  2. No backup lives on the same disk as the data it protects.
  3. Backup jobs ran without errors this week.
  4. A verify job checked the backups recently.
  5. I restored one VM or container to a new ID and it booted.
  6. I found my marker file inside the restored copy.
  7. I restored one single file from a backup.
  8. My encryption key is stored in two safe places off the server.
  9. No old snapshots are left over from past updates.
  10. I wrote down the date, the time it took and any problems.
  11. The next drill is in my calendar.

FAQ

Is a snapshot a backup?

No. A snapshot is a short-term undo point on the same storage as the original. If that storage fails, the snapshot is gone too. A backup is a separate, complete copy you can restore elsewhere.

Should I use snapshots or backups?

Use both, for different jobs. Take a snapshot right before an update so you can roll back fast. Keep scheduled backups on another device, with one copy off-site, for real disasters.

What is the 3-2-1 backup rule?

Keep 3 copies of important files, on 2 different types of storage, with 1 copy off-site. CISA recommends it for small businesses, and it works well for a home server too.

How often should I test a backup restore?

Test on a regular schedule, and after any big change to your server or backup setup. Pick a rhythm you will keep, and put it in your calendar. A small, regular drill beats a big one you never do.

Can Proxmox Backup Server restore a single file?

Yes. In Proxmox VE, the File Restore button on the backup storage lets you browse a backup stored on Proxmox Backup Server and download single files. Check the docs for your version.

Does a Proxmox backup include my snapshots?

No. Proxmox backups do not include snapshots, and the backup log says so when it finds them. The backup holds the VM's current state and configuration, not its snapshot history.

Related guides

Virtualization Software: Free and Paid Options Compared

Illustration of desktop and server virtualization software running virtual machines on a laptop and a server

Virtualization software lets one computer run many virtual machines (VMs). It comes in two groups. Desktop apps, such as VirtualBox, VMware Workstation and Parallels, run VMs on the computer you already use. Server platforms, such as Proxmox VE, VMware ESXi, Hyper-V and XCP-ng, turn a dedicated machine into a host for many VMs. Many good options are free as of October 2026.

Updated October 2026. This guide replaces the 2012 version with current tools and a home lab focus.

Who this is for: you want to run VMs at home or for a small team, and you need a short list of software to try.

Desktop vs server virtualization software

The first choice is not a brand. It is where the software runs.

  • Desktop apps (type 2 hypervisors) install on Windows, macOS or Linux like any other program. You use them for test VMs, a second OS or learning. Your VMs stop when you shut the laptop.
  • Server platforms (type 1 hypervisors) install directly on the hardware. The machine runs all day, and you manage it from a web browser or a console on another computer.

If the terms type 1 and type 2 are new, read what a hypervisor is and how the two types differ. Hyper-V is a special case. It is a type 1 hypervisor, but you can turn it on inside Windows 11 Pro.

Virtualization software comparison table

This table reflects vendor pages as of October 2026. License terms change often. Verify every row on the vendor's site before you decide.

SoftwareTypeRuns onLicense as of October 2026 (verify)Best for
VMware Workstation ProDesktopWindows, LinuxFree for all use, no paid supportPolished desktop VMs, VMware skills
VMware Fusion ProDesktopmacOSFree for all use, no paid supportMac users who want VMware
Oracle VirtualBoxDesktopWindows, macOS, LinuxOpen source (GPLv3); Extension Pack under separate licenseFree cross-platform lab
Parallels DesktopDesktopmacOSPaid (one-time or subscription by edition)Windows on a Mac, ease of use
UTMDesktopmacOSFree and open sourceFree VMs and emulation on a Mac
GNOME BoxesDesktopLinuxFree and open sourceSimple VMs on a Linux desktop
Hyper-V (client)Type 1, in WindowsWindows 10/11 Pro or EnterpriseIncluded with WindowsWindows users, WSL2 and Windows Sandbox users
Proxmox VEServerBare metal (x86)Open source (AGPLv3), optional subscriptionHome labs and small teams
VMware ESXi / vSphereServerBare metal (x86)Commercial subscription; limited free ESXi 8 editionTeams tied to the VMware ecosystem
Hyper-V (Windows Server)ServerBare metal (x86)Part of paid Windows ServerMicrosoft-based businesses
XCP-ngServerBare metal (x86)Open source, optional paid supportA Xen-based, VMware-like model
KVM with libvirtServerAny Linux hostOpen source, part of LinuxLinux admins who want full control
Nutanix Community EditionServerBare metal (x86)Free, community-supportedLearning Nutanix

Free virtualization software for your desktop

If you want to run VMs on the computer you own, start here. The VMware vs VirtualBox vs Proxmox comparison covers the top two in depth, with nested Proxmox steps. This section gives the short version and adds the others.

VMware Workstation Pro and Fusion Pro

Workstation Pro runs on Windows and Linux. Fusion Pro runs on macOS. On 11 November 2024, Broadcom made both free for commercial, educational and personal use. The paid versions are no longer sold. Free users get community forums and docs, not support tickets. Read the VMware announcement, then check the current download steps on Broadcom's site.

Oracle VirtualBox

VirtualBox runs on Windows, macOS and Linux. The base package is open source under the GNU GPL version 3. The Extension Pack is different. It is free for personal and educational use under the PUEL. Commercial use needs a paid enterprise license. See the VirtualBox licensing FAQ before you install the Extension Pack at work.

Hyper-V on Windows 11

Hyper-V is built into Windows 10 and Windows 11 Pro and Enterprise. There is nothing to download. You turn it on as a Windows feature. It cannot be installed on the Home editions. Your CPU needs Second Level Address Translation (SLAT). Microsoft lists 4 GB of memory as the minimum.

One warning. When the Hyper-V hypervisor runs, VMware Workstation and VirtualBox must run on top of it. They often run slower, and some features may not work. Microsoft's Hyper-V install guide warns that their VMs may not start or may run unreliably. Test your setup before you rely on it.

UTM and Parallels Desktop on a Mac

UTM is a free, open-source app for macOS built on QEMU. It can run VMs and can also emulate other CPU types, such as x86 Windows on an Apple Silicon Mac (slowly). Parallels Desktop is a paid app. As of October 2026, it comes in Standard, Pro and Business editions, with Standard sold as a one-time purchase and the others by subscription. Check the Parallels site for current prices.

GNOME Boxes on Linux

GNOME Boxes is a simple VM app for the GNOME desktop. It uses QEMU, KVM and libvirt underneath. You point it at an ISO, and it builds the VM with few questions. It suits quick tests. For more control on Linux, use virt-manager or a server platform.

Server virtualization software

A server platform needs its own machine. In return, your VMs run all day, and you get features such as snapshots, backups, clustering and live migration.

Proxmox VE

Proxmox VE is a Debian-based platform that runs KVM virtual machines and LXC containers from one web interface. As of October 2026, it is free and open source under the GNU AGPLv3. The full feature set works without a subscription. Paid subscriptions add the enterprise repository and, on most plans, technical support. See the Proxmox VE subscription page for the current plans.

For a home lab, this is the platform I would start with. Read what Proxmox VE is and why home labs run it for the full picture.

VMware ESXi and vSphere

ESXi is VMware's bare-metal hypervisor. vCenter manages many ESXi hosts together. As of October 2026, Broadcom sells vSphere as per-core subscription bundles. Get a current quote from Broadcom or a partner.

Free ESXi was withdrawn in February 2024. On 10 April 2025, Broadcom released ESXi 8.0 Update 3e as a free download from its support portal. Reported limits are 2 physical CPUs, 8 vCPUs per VM, no vCenter and no support. As of October 2026, no free ESXi 9 was found. For a full two-way comparison, read Proxmox vs VMware in 2026.

Microsoft Hyper-V on Windows Server

On a server, Hyper-V is a role you add to Windows Server. Microsoft Hyper-V Server 2019 was the last free, standalone Hyper-V product. On Windows Server 2025, Hyper-V comes with a paid Windows Server license. As of October 2026, Microsoft's Windows Server licensing says a fully licensed Standard host covers 2 Windows Server VMs. Datacenter covers unlimited Windows Server VMs. Licenses are per core. Check the current guidance with Microsoft or your reseller.

XCP-ng

XCP-ng is an open-source type 1 hypervisor based on Xen. Vates develops it, and the project is hosted by the Linux Foundation. You manage it with Xen Orchestra, a web tool for management and backups. Its model feels close to vSphere, with one management layer over many hosts. Vates sells support if you need it.

KVM with libvirt

KVM is the hypervisor built into the Linux kernel. Proxmox uses it, and so do many cloud providers. You can also use it directly on any Linux server, with libvirt to manage VMs and virt-manager or Cockpit as a front end. It is free and flexible. You build the parts that Proxmox gives you out of the box, such as backups and clustering.

XenServer (formerly Citrix Hypervisor)

XenServer (once called Citrix Hypervisor) is a commercial Xen-based platform. As of October 2026, it is licensed through Citrix subscriptions, and its branding has changed more than once. The guide to Hyper-V vs VMware vs Proxmox covers its history. Check the XenServer site for current editions and trial terms.

Nutanix Community Edition

Nutanix Community Edition (CE) is a free, community-supported version of the Nutanix platform with the AHV hypervisor. It is a good way to learn Nutanix if your employer uses it. As of October 2026, it needs a free Nutanix account to download, and much more memory and disk than Proxmox. Read the Nutanix CE getting-started guide for current requirements before you try it.

How to choose virtualization software

Answer these questions in order.

  1. Do you need VMs only while you work at your computer? Use a desktop app. VirtualBox is free everywhere. VMware Workstation or Fusion is free and polished. On a Mac, also look at UTM and Parallels.
  2. Do you run Windows Pro and use WSL2 or Windows Sandbox? Hyper-V is already there. Use it to avoid clashes.
  3. Do you want services that run all day? Use a server platform on a spare PC or mini PC. Proxmox VE is the easiest start for most home labs.
  4. Is your workplace on VMware, Hyper-V or Nutanix? Learn that platform, nested or on spare hardware, for job skills.
  5. Are you a small business choosing a platform? Read the side-by-side of Hyper-V vs VMware vs Proxmox before you buy.

What to watch for

  • Old license advice. VMware, VirtualBox and Citrix terms changed in 2024 to 2026. Read the vendor page, not a forum post (or this one) as the final word.
  • Two hypervisors on one PC. Hyper-V, WSL2 and some Windows security features take over the CPU's virtualization features. Other desktop apps then run slower or fail.
  • Hardware support. ESXi has a strict hardware list. Proxmox and KVM follow Linux drivers. Check network cards and storage controllers before you buy.
  • The Extension Pack at work. The VirtualBox base package is free for any use. The Extension Pack is not free for commercial use.
  • Apple Silicon. An M-series Mac runs ARM guests at near-native speed. x86 guests need emulation, which is slow.

FAQ

What is the best free virtualization software?

For a desktop, VirtualBox and VMware Workstation Pro are both free as of October 2026. For a dedicated server, Proxmox VE is free with every feature. The best one depends on whether you need VMs on your own computer or on a separate host.

Which virtualization software is free for commercial use?

As of October 2026, VMware Workstation Pro and Fusion Pro, the VirtualBox base package, Proxmox VE, XCP-ng and KVM are free for commercial use. The VirtualBox Extension Pack and Parallels Desktop are not. Verify each license on the vendor's site before you use it at work.

Which virtualization software runs on Linux?

On a Linux desktop, use VirtualBox, VMware Workstation Pro, GNOME Boxes or virt-manager. On a Linux server, KVM with libvirt is built in, and Proxmox VE is a full platform built on Debian. All of these are free as of October 2026.

Which virtualization software is best for a Mac?

On Apple Silicon, VMware Fusion Pro and UTM are free, and Parallels Desktop is a paid option. All three run ARM guests well. Proxmox VE does not run on a Mac, so learn it on a spare x86 PC.

Can I run virtualization software on a laptop?

Yes. Any desktop app in this guide runs on a modern laptop with hardware virtualization turned on. Memory is the usual limit, so check what each VM needs. For VMs that run all day, use a server platform on a separate machine.

Related guides

VMware vs VirtualBox vs Proxmox for a Desktop Lab

Illustration of a laptop running three desktop virtualization apps, each hosting a virtual machine

For VMware vs VirtualBox on a desktop lab, both are good, free type 2 apps. VMware Workstation (Windows, Linux) and Fusion (Mac) are polished and, as of October 2026, free for personal and commercial use (verify on Broadcom's site). VirtualBox is open source and runs on all three platforms. Proxmox is a server platform, not a desktop app, but you can run it inside either one to learn it.

Who this is for: you want to run virtual machines on the computer you already own, and you need to pick one tool to start.

What a desktop lab is

A desktop lab is a set of virtual machines on your everyday laptop or desktop. You install a hypervisor app, create VMs, and break things without risk to your main system. It is the cheapest way to start a home lab, because you need no extra hardware.

VMware Workstation, VMware Fusion and VirtualBox are type 2 hypervisors. They run as apps on top of your normal OS. Proxmox VE is a type 1 hypervisor. It installs on bare metal and becomes the OS. If those terms are new, read type 1 vs type 2 hypervisors explained first. The difference shapes everything below.

VMware Workstation and Fusion

VMware makes two desktop products. Workstation Pro runs on Windows and Linux hosts. Fusion Pro runs on macOS. Broadcom now owns VMware.

License

In May 2024, Broadcom dropped the price of Workstation Pro and Fusion Pro to zero for home users. On 11 November 2024, it made them free for all use: personal, commercial and educational. You need no license key. Broadcom sells no support for these free versions. As of October 2026, verify the current license, download steps and any commercial-use rules on Broadcom's site. Start from the Broadcom TechDocs portal and search for Workstation or Fusion. Do not rely on an old blog post (this one included) for license terms.

Strengths

  • Mature, stable and well documented.
  • Good graphics support for desktop guests.
  • Snapshots, clones and virtual networks that are easy to set up.
  • A familiar path if you work with VMware at your job.

Limits

  • Closed source. You depend on Broadcom's choices about pricing and downloads.
  • The download process needs an account on Broadcom's portal. Some users find it confusing.
  • Fusion on Apple Silicon Macs runs ARM guests. You need ARM builds of Windows or Linux, not the usual x86 ISOs. Check the current docs for what is supported.

Oracle VirtualBox

VirtualBox is Oracle's free hypervisor app. It runs on Windows, macOS and Linux hosts. The base package is open source under the GPL.

License

The core VirtualBox package is free for any use. The Extension Pack is different. It adds features such as some USB and remote display support, and it has its own license (the PUEL). That license has limits on use in organizations. As of October 2026, read the license terms on the VirtualBox downloads page before you install the Extension Pack at work.

Strengths

  • Free and open source for the core package.
  • One tool on all three desktop platforms.
  • Large community and many guides.
  • Works well with Vagrant and other automation tools.

Limits

  • Graphics and desktop feel can be less smooth than VMware for some guests.
  • On Windows, VirtualBox can clash with Hyper-V features (WSL2, Windows Sandbox, some security settings). It can run on top of the Windows hypervisor, but performance may drop. Check the VirtualBox manual for the current guidance.
  • Apple Silicon host support is newer than the x86 version. Check the current docs for which guests work.

Proxmox VE: not a desktop tool, but worth learning

Proxmox VE is a server platform. It is based on Debian Linux, uses KVM for VMs and LXC for containers, and you manage it from a web browser. You do not install it as an app on Windows or macOS. You install it on its own machine. The guide to what Proxmox VE is covers the details.

So why is it in this comparison? Because many people start with a desktop app, then move to Proxmox on a spare PC or mini PC. You can try Proxmox first inside VMware or VirtualBox. This is called nested virtualization. A VM runs Proxmox, and Proxmox runs its own VMs inside it.

How to run Proxmox nested

  1. Check that your CPU supports hardware virtualization (Intel VT-x or AMD-V). Turn it on in the BIOS or UEFI.
  2. Download the Proxmox VE ISO from the official site.
  3. Create a VM in VMware or VirtualBox with at least two CPU cores and enough memory for Proxmox plus one small guest.
  4. Turn on nested virtualization in the VM settings. VMware calls it "Virtualize Intel VT-x/EPT or AMD-V/RVI". VirtualBox calls it "Enable Nested VT-x/AMD-V".
  5. Boot the ISO and install Proxmox. Then open its web interface from your host browser.

Menu names change between versions. If a setting is missing, check the docs for your version. Nested guests run slower than guests on bare metal. Use nesting to learn, not to host services you rely on.

Apple Silicon Macs are different. Proxmox VE is built for x86 (Intel and AMD) processors. An M-series Mac uses an ARM processor, so it cannot run Proxmox with hardware virtualization. You can only run it under full x86 emulation, which is very slow. On an Apple Silicon Mac, learn Proxmox on a spare x86 PC or a rented server instead.

For install steps, system requirements and the current release, use the Proxmox VE documentation. As of October 2026, Proxmox VE is free and open source, with an optional paid subscription for the enterprise repository. Verify the current terms on the Proxmox site.

VMware vs VirtualBox vs Proxmox: comparison table

This table reflects the products as of October 2026. Verify every row on the vendor page before you decide. License terms in particular change often.

FactorVMware Workstation / FusionVirtualBoxProxmox VE
Hypervisor typeType 2 (app on your OS)Type 2 (app on your OS)Type 1 (bare metal)
Windows hostYes (Workstation)YesNo (runs nested only)
macOS hostYes (Fusion)Yes (check Apple Silicon support)Intel Macs: nested only. Apple Silicon: emulation only, very slow
Linux hostYes (Workstation)YesIt is the host OS
SourceClosedOpen (core), Extension Pack separateOpen source
CostFree for all use, no paid support (verify)Free core (verify Extension Pack terms)Free, optional paid subscription (verify)
ContainersNoNoYes (LXC)
Web managementNoNoYes
Best forPolished desktop VMs, VMware skillsFree cross-platform labA dedicated home server

What your computer needs

All three tools need a 64-bit CPU with hardware virtualization turned on. Most desktop and laptop CPUs from the last decade have it. Check your BIOS or UEFI if VMs refuse to start.

Memory is the real limit. Your host OS needs its share, and each VM needs its own. Plan for your host plus every VM you want to run at the same time. A fast SSD also helps, since several VMs reading from one slow disk feel sluggish. I do not quote exact numbers here, because they depend on the guests you run. Check each guest OS for its own minimum.

Which one should you pick?

Start from the computer you have and the goal you want.

  • You are on Windows or Linux and want the smoothest desktop VMs. Try VMware Workstation Pro, after you confirm the current license.
  • You want free, open source and the same tool everywhere. Pick VirtualBox.
  • You are on an Apple Silicon Mac. Fusion is the more mature choice for ARM guests today. Check VirtualBox's current Mac support before you rule it out.
  • You use Windows Pro and already need Hyper-V. Consider Microsoft Hyper-V itself. It avoids the clash with other hypervisors.
  • You want a server that runs 24/7. Skip the desktop apps. Put Proxmox on a spare PC. The guide to home server setup walks through the hardware.

My view: install one desktop app, then nest Proxmox inside it for a weekend. If you like Proxmox, move it to real hardware. If you work in a VMware shop, the Proxmox vs VMware comparison covers the server side.

What to watch for

  • Two hypervisors on one host. Running VMware and VirtualBox at the same time can fail or run slowly. Close one before you start the other.
  • Hyper-V features on Windows. WSL2, Docker Desktop and Core Isolation can turn on the Windows hypervisor. Your desktop app then runs on top of it, often slower.
  • Too little memory. Every VM takes RAM from your host. Leave enough for your own OS, or the whole machine slows down.
  • Laptop sleep. Close or suspend VMs before your laptop sleeps. A VM caught mid-write can corrupt its disk.
  • Old license advice. VMware and VirtualBox license terms have changed. Always read the vendor page, not a forum post.

FAQ

Is VMware Workstation free?

Yes, for personal and commercial use since November 2024. Verify on Broadcom's site. As of October 2026, Workstation Pro and Fusion Pro need no license key, and Broadcom sells no support for them. Terms have changed before and may change again.

Is VirtualBox better than VMware?

Neither is better for everyone. VirtualBox is open source and runs on all three desktop platforms. VMware is often smoother for desktop guests and matches skills used at work.

Can I run Proxmox in VirtualBox?

Yes, on an x86 host (Intel or AMD). Turn on nested VT-x/AMD-V in the VM settings and install Proxmox from its ISO. Guests inside the nested Proxmox run slower, so use it for learning only. On an Apple Silicon Mac, Proxmox runs only under x86 emulation, which is too slow for real use.

Can VMware and VirtualBox run on the same computer?

You can install both. Running VMs in both at the same time may fail or run slowly. Close one app before you start VMs in the other.

Is the VirtualBox Extension Pack free?

It is free for personal and educational use, under a different license (the PUEL) from the core package. Commercial use needs a paid license. Since version 7.1, there is no free 30-day evaluation for business use. As of October 2026, read the current terms on the VirtualBox site.

What is the best desktop virtualization software for a beginner?

VirtualBox is a safe first step, since it is free and runs everywhere. VMware Workstation or Fusion is a good choice if you want more polish. On an x86 PC, either one can host a nested Proxmox when you are ready.

Related guides

Containers vs Virtual Machines: When to Use Which

Illustration comparing virtual machines, each with its own operating system layer, to containers sharing one kernel

The core difference in container vs virtual machine is the kernel. A virtual machine (VM) runs a full operating system on virtual hardware, with its own kernel. A container shares the host's kernel and isolates only the processes, files and network. Use a VM when you need strong isolation or a different OS. Use a container when you want to run many Linux services with little overhead.

Who this is for: you run a home lab or a small-team server, and you want to know where each workload should live.

What a virtual machine is

A virtual machine is a complete computer made of software. A hypervisor gives it virtual CPUs, memory, disks and network cards. The VM boots its own operating system, with its own kernel, from its own virtual disk. The guest OS does not know (or care) that the hardware is not real.

The hypervisor is the layer that makes this work. If you want the full picture, read how a hypervisor shares one machine between VMs. For this post, you only need one fact. Each VM carries a full OS, so each VM costs you memory, disk and boot time.

That cost buys you three things:

  • Any OS. A Linux host can run Windows, BSD or a different Linux kernel in a VM.
  • Strong isolation. A crash or a kernel exploit inside the VM stays inside the VM, in most cases.
  • Full control. You can load kernel modules, pass through a GPU or a disk controller, and snapshot the whole machine.

What a container is

A container is a group of processes that the host kernel isolates from everything else. The kernel gives the container its own view of the file system, the process list, the network and the users. Linux does this with namespaces and control groups (cgroups). There is no second kernel and no virtual hardware.

Because there is no guest OS to boot, a container starts fast and uses little memory. You can run many more containers than VMs on the same machine. The limit is simple: a container must use the host's kernel. A Linux host runs Linux containers. It cannot run a Windows container natively.

Containers are one form of OS-level virtualization. The guide to types of virtualization shows where they sit next to server, desktop, storage and network virtualization.

Two kinds of container

Not all containers do the same job. Home lab users meet two kinds:

  • System containers (LXC). An LXC container looks like a small Linux machine. It runs an init system, several services and a shell you log in to. You manage it like a lightweight VM.
  • Application containers (Docker, Podman). A Docker container usually runs one application from an image. You do not log in and patch it. You replace it with a new image when an update comes out.

This split matters when you compare LXC vs Docker. They use the same kernel features, but they suit different habits. See the LXC documentation and the Docker documentation for the details of each.

Container vs virtual machine: side by side

This table sums up the trade-offs. The words "faster" and "lighter" are relative. Real numbers depend on your hardware and workload, so measure your own.

FactorVirtual machineSystem container (LXC)Application container (Docker)
KernelIts ownShared with hostShared with host
Guest OS choiceAny OS the hypervisor supportsLinux only (on a Linux host)Linux images on a Linux host
IsolationStrong (hardware-level)Good, weaker than a VMGood, weaker than a VM
Start timeSlower (full boot)FastFast
Memory overheadHigher (full OS)LowLow
How you update itPatch the OS insidePatch the OS insidePull a new image, recreate
Hardware passthroughYes (GPU, disks, USB, PCIe)Limited, needs host configLimited, needs host config
Best forWindows, appliances, untrusted codeSmall Linux services you manage by handPackaged apps with ready-made images

When a virtual machine wins

Pick a VM when one of these is true:

  • You need a different OS. Windows, pfSense, OPNsense, TrueNAS and many appliances need their own kernel.
  • You run code you do not trust. A test box for downloads or a public-facing service gets more protection in a VM.
  • You need hardware passthrough. A GPU for a media server or a disk controller for a storage VM is simpler in a VM.
  • You need a custom kernel. Some VPN and storage tools need kernel modules the host does not load.
  • You want clean snapshots of a whole system. A VM snapshot covers the OS, the apps and the data disk together.

When a container wins

Pick a container when these are true:

  • The app runs on Linux. Most self-hosted apps do.
  • You want to run many small services. DNS, a reverse proxy, a dashboard and a password manager do not each need a full OS.
  • You have limited memory. A mini PC or an old laptop goes much further with containers.
  • The app ships as a Docker image. If the project publishes an image and a compose file, use them. You get updates the way the developers test them.

In my view, most home labs end up with a mix. A few VMs carry the heavy or sensitive jobs. Many containers carry the small services.

How Proxmox runs both

Proxmox VE is a good place to learn this, because it runs both models from one web interface. It uses KVM for virtual machines and LXC for system containers. If you are new to it, start with what Proxmox VE is and why home labs run it.

In Proxmox, you create a VM or a container from the same menu. Both get an ID, storage, a network bridge and backup jobs. The difference is under the hood. A VM gets virtual hardware. A container shares the Proxmox host kernel.

Proxmox vs Docker: the wrong question

People often search "Proxmox vs Docker". The two are not rivals. Proxmox is a platform that hosts VMs and LXC containers. Docker is a tool that runs application containers inside a Linux system. You can run Docker on Proxmox. The real question is where Docker should live.

Where to run Docker on Proxmox

You have four choices:

  1. Docker inside a VM. Create a Linux VM and install Docker in it. This is the safest option. As of October 2026, the Proxmox documentation says a VM remains a recommended practice for isolation and live migration. Verify this in the Proxmox VE documentation before you decide.
  2. Docker inside an LXC container. This uses less memory. It also needs extra settings (such as nesting), and updates to the host or Docker can break it. Many people run it this way. Treat it as a choice you test, not a default.
  3. Docker on the Proxmox host itself. Do not do this. It mixes your app layer with your hypervisor. A bad update or a firewall rule can take down every guest.
  4. OCI images as app containers. As of October 2026, Proxmox can pull an OCI image (the format Docker uses) and run it as an application container, converted to LXC. This is a technology preview, not for production. Check the Proxmox docs for its current status.

A simple pattern works for most labs. Run one Linux VM for all your Docker apps. Run LXC containers for small standalone services. Run separate VMs for Windows, firewalls and anything that needs passthrough.

Common mistakes

  • Thinking a container is as isolated as a VM. It is not. All containers share one kernel. A kernel flaw can affect every container on the host. Keep risky workloads in VMs.
  • Running containers as root without need. Use unprivileged LXC containers where you can. For Docker, read the security section of the Docker docs.
  • Putting one app per VM by habit. Ten VMs for ten small apps wastes memory. Group small Linux apps in containers.
  • Storing data inside the container. When you recreate a Docker container, data inside it goes away. Use volumes or bind mounts, and back them up.
  • Skipping backups because containers are "disposable". The container is disposable. Your data and your config are not.
  • Forgetting the host is a single point of failure. VMs and containers on one box all stop when the box stops. The post on disadvantages of server virtualization covers how to plan for this.

A quick way to decide

Ask these questions in order. Stop at the first "yes".

  1. Does it need a non-Linux OS or its own kernel? Use a VM.
  2. Does it need GPU or disk passthrough? Use a VM.
  3. Is it untrusted, or exposed to the internet with no proxy in front? Use a VM.
  4. Does the project ship an official Docker image? Run it in Docker, inside a VM.
  5. Is it a small Linux service you want to manage like a server? Use an LXC container.

This is a starting rule, not a law. Change it when your own tests show a better fit.

FAQ

Is a container faster than a virtual machine?

A container usually starts faster and uses less memory, because it does not boot a second OS. For CPU-heavy work, the gap is often small, since modern VMs use hardware virtualization. Measure your own workload before you decide on speed alone.

Is a container more secure than a VM?

No. A VM has stronger isolation, because each VM has its own kernel. Containers share the host kernel, so one kernel flaw can reach all of them. Containers can still be safe when you keep them unprivileged and patched.

What is the difference between LXC and Docker?

Both use the same Linux kernel features. LXC runs a full Linux userland that you manage like a small server. Docker runs one packaged application from an image, and you replace the container to update it.

Can I run Docker inside a virtual machine?

Yes, and it is a common setup. You install a Linux VM, then install Docker in it. On Proxmox this keeps Docker away from the host and makes backups simple.

Can a container run Windows on a Linux host?

No. A container shares the host kernel, so a Linux host runs Linux containers. To run Windows on a Linux host, use a VM.

Do I need Proxmox to use containers?

No. You can run Docker or LXC on any Linux system. Proxmox adds a web interface, backups and VMs in one place, which helps when your lab grows.

Related guides

Proxmox vs VMware in 2026: For Home Labs and Small Teams

Illustration comparing two virtualization platforms on a balance scale with a virtual machine migrating between them

Proxmox vs VMware comes down to license terms, cost, ecosystem and support. For most home labs and small teams in 2026, Proxmox VE is the easier choice, since it is open source with every feature in the free version. VMware vSphere and ESXi are still strong, mature products, but Broadcom changed the licensing after it bought VMware. VMware now makes the most sense for teams that already depend on its ecosystem and can accept the new terms.

Who this is for: you run a home lab or a small IT team, and you are choosing a platform or planning a move.

Proxmox vs VMware: the short version

Both are type 1 hypervisors. Both run on bare metal and host many virtual machines. If you want the background, read the plain-English guide to hypervisors.

The real differences are not in raw features. They are in licensing, cost, ecosystem and support.

  • Proxmox VE is Debian Linux with KVM for VMs and LXC for containers. It has a built-in web interface and clustering. It is open source. You pay only if you want the enterprise repository or support. See what Proxmox VE is for the full overview.
  • VMware ESXi is the hypervisor at the core of VMware vSphere. You manage many hosts with vCenter. It has a huge base of enterprise tools, staff skills and vendor support. It is commercial software sold by Broadcom.

What changed at VMware under Broadcom

Broadcom completed its purchase of VMware in late 2023. Since then it has made large changes to how VMware is sold. As of October 2026, the broad changes I am aware of are:

  • VMware moved away from perpetual licenses toward subscriptions.
  • The product line was cut down into a small number of bundled offerings.
  • Many partners and resellers saw their programs change.
  • The free ESXi edition was withdrawn in February 2024. On 10 April 2025, a free edition returned as ESXi 8.0 Update 3e, a download from the Broadcom support portal. Reported limits are 2 physical CPUs, 8 vCPUs per VM, no vCenter, no support and no production use. As of October 2026, I found no free ESXi 9. Verify the current status on Broadcom's site before you plan around it.

I do not quote prices or core minimums here. They have changed more than once, and they depend on your contract. Verify current terms and prices directly on Broadcom's site or with a Broadcom partner. Product details are in the VMware vSphere documentation.

For home labs, the change matters most. Many people learned VMware on a free ESXi host or on low-cost lab licenses. When that path became uncertain, many home lab users moved to Proxmox VE. That is my reading of the forums, not a measured figure.

Feature comparison table

This table compares the parts that matter for home labs and small teams. Check both vendors' docs for current details as of October 2026.

AreaProxmox VEVMware vSphere / ESXi
License modelOpen source (AGPL v3), optional paid subscriptionCommercial subscription from Broadcom (verify current terms)
Cost to start a home labZeroDepends on current free or lab license options (verify)
Hypervisor baseLinux KVMVMware's own kernel
ContainersLXC built inNot built into ESXi
ManagementWeb UI on every node, no extra serverHost client per host, vCenter for many hosts
Clustering and live migrationBuilt inNeeds vCenter and the right license
High availabilityBuilt in, needs a cluster with quorumvSphere HA, needs vCenter and the right license
Software-defined storageZFS and Ceph built invSAN (licensed separately or in bundles, verify)
BackupsBuilt-in jobs, plus Proxmox Backup ServerRelies on third-party backup products
Hardware supportBroad, follows Linux driversStrict hardware compatibility list
Third-party ecosystemGrowingVery large and mature
SupportVendor subscription or communityBroadcom and partners

Proxmox vs ESXi for a home lab

For a home lab, Proxmox VE wins on most points.

Cost and access

Proxmox VE is free with all features. You can install it today with no account and no license key. VMware access for home labs depends on Broadcom's current offers, which have changed several times.

Hardware

Proxmox VE runs on almost any x86 machine that Linux supports. That includes mini PCs with consumer network cards. ESXi has a strict hardware list. Some consumer network cards and storage controllers are not supported. Check before you buy.

Learning value

This is where VMware still has a case. If your job uses VMware, or you want a VMware job, hands-on time with vSphere is valuable. Many employers still run it. If that is you, keep a small VMware lab if you can get licenses, and run Proxmox for everything else.

If you want a desktop tool instead of a bare-metal host, see VMware vs VirtualBox vs Proxmox for a desktop lab.

Proxmox vs VMware for small teams

For a small team, the answer is less clear. Think about these five questions.

  1. What does your renewal look like? Get a written quote under the current Broadcom terms. Compare it with a Proxmox subscription at the support level you need.
  2. What tools depend on VMware? List your backup, monitoring, disaster recovery and automation tools. Check if each one supports Proxmox VE.
  3. What skills does your team have? Proxmox VE is Debian underneath. A team with Linux skills will adapt quickly. A team with only VMware and Windows skills needs training time.
  4. What support do you need? Check the hours, languages and response times of each support option. Decide what you need when something breaks at night.
  5. What does compliance require? Some contracts or audits name approved platforms. Check yours.

How to migrate from VMware to Proxmox

A migration path exists. In 2024, Proxmox added an import tool that can connect to an ESXi host and import VMs into Proxmox VE. Check the current Proxmox VE docs and the migration pages on the Proxmox wiki for the exact steps and limits.

A safe migration follows a simple order:

  1. Inventory. List every VM, its OS, disk size, network and dependencies.
  2. Back up. Take a full backup of every VM before you touch it.
  3. Build a test host. Install Proxmox VE on spare hardware.
  4. Move a low-risk VM first. Import it, boot it and check it works.
  5. Fix drivers. Windows VMs need VirtIO drivers for good disk and network speed. Remove VMware Tools after the move.
  6. Check networking. Network interface names and MAC addresses may change. Update any static settings inside the VM.
  7. Move the rest in waves. Plan a rollback for each wave.

Do not migrate a production system on a Friday afternoon. Test the restore of your backups before you start.

Other VMware alternatives to consider

Proxmox VE is not the only way out of VMware. Look at two others before you decide.

Microsoft Hyper-V

Hyper-V is part of Windows Server. If your team runs a Microsoft stack and already pays for Windows Server licenses, Hyper-V may cost little extra. Clustering uses Windows failover clustering. Check the current license rules for your Windows Server edition. The Hyper-V docs are the place to start.

XCP-ng

XCP-ng is an open-source hypervisor based on Xen. You manage it with Xen Orchestra, a separate tool. Its model feels closer to VMware's, with a central management layer over many hosts. Its home lab community is smaller than Proxmox's.

Containers instead of VMs

Some workloads do not need a VM at all. A modern web app may run better as containers on a small Linux host. Moving off VMware is a good moment to ask which VMs could become containers.

For a home lab, Proxmox VE is, in my view, the strongest choice of the group. It runs VMs and containers in one place. If you are building that lab from scratch, the home server setup guide covers hardware and the first services.

Who should stay on VMware

VMware is still the right answer for some teams. Stay, at least for now, if:

  • Your critical tools only support VMware, and there is no good replacement.
  • Your team has deep VMware skills and no Linux skills, and you cannot fund training.
  • You depend on advanced features such as vSAN stretched clusters, NSX networking or VMware-specific disaster recovery.
  • A contract, audit or vendor support rule requires VMware.
  • Your renewal under the current terms is affordable for your business.

Staying is not a failure. Moving a working platform has real costs and risks. Make the choice on your own numbers, not on forum mood.

What to watch for

  • Comparing list prices only. Include support, training, migration time and tool changes in the total cost.
  • Two-node Proxmox clusters. A cluster needs a quorum. With two nodes, add a third vote (a QDevice) or the cluster can stop when one node fails.
  • Storage design. VMware shops often use a shared SAN. Proxmox can use it too, but snapshot support depends on the storage type. Read the storage section of the docs first.
  • Backup tools. Your VMware backup product may not support Proxmox VE. Plan the new backup method before you move anything.
  • Old information. Licensing news from 2024 may be out of date. Always check the vendor's current page.

FAQ

Is Proxmox a good VMware alternative?

For home labs and many small teams, yes. Proxmox VE covers VMs, containers, clustering, high availability and backups with no license fee to start. Large enterprises with deep VMware tool chains need a careful review before they switch.

Is ESXi still free?

Partly. Broadcom withdrew free ESXi in February 2024, then released ESXi 8.0 Update 3e as a free download in April 2025. As of October 2026, it reportedly allows 2 physical CPUs and 8 vCPUs per VM, with no vCenter, no support and no production use. Verify the current terms on Broadcom's site.

Can Proxmox import VMware VMs?

Yes. Since 2024, Proxmox VE has an import tool that can pull VMs from an ESXi host. You can also convert VMDK disk files by hand. Check the current Proxmox docs for steps and limits.

Is Proxmox as stable as VMware?

Proxmox VE is built on Debian and KVM, both mature and widely used. Many businesses run it in production. Stability depends more on your hardware, storage design and update process than on the brand.

Is Proxmox harder to learn than VMware?

Not much, for daily tasks. Both have a web interface. Proxmox expects more Linux knowledge for advanced jobs. VMware expects more knowledge of its own tools and licensing.

Can I run Proxmox and VMware side by side?

Yes. Many teams run both during a migration. Keep them on separate hosts, and move VMs in planned waves. In a home lab, you can also run ESXi nested inside a Proxmox VM. This keeps your VMware skills fresh. You need a valid license.

Related guides

Home Server Setup: Hardware, OS and Your First Services

Illustration of a home server sharing photos, media and files with a phone, TV and laptop

A home server setup has five steps. Decide what the server will do, then pick hardware that fits that job. Pick an operating system, such as Proxmox VE, Ubuntu Server, TrueNAS or Unraid. Then add a few services, set up backups and make remote access safe.

Who this is for: you want one always-on machine for files, media, backups or self-hosted apps.

What is a home server?

A home server is a computer at home that runs all the time and provides services to other devices. Your phone backs up photos to it. Your TV streams movies from it. Your laptop saves files to it.

It is close to a home lab, but the goal is different. A home lab is for learning and breaking things. A home server is for services that you and your family depend on. Many people run both on one box. If you want the lab side, read what a home lab is and how to start one.

Step 1: decide what the server will do

Write down the jobs before you buy anything. The jobs decide the hardware and the OS. Common jobs are:

  • File storage. A shared drive for the household.
  • Photo and phone backup. A private copy of every photo.
  • Media server. Movies, TV and music streamed to every screen.
  • Network services. An ad blocker or DNS filter for the whole house.
  • Home automation. A local hub for lights, sensors and heating.
  • Self-hosted apps. A password manager, notes, a wiki or a recipe app.
  • A test space. VMs for learning, kept apart from the services above.

Then ask two questions. How much storage do you need now, and in three years? Do you need to convert video on the fly (transcoding) for phones and TVs? Large storage needs drive bays. Transcoding needs a CPU with a good built-in graphics unit, or a separate GPU.

Step 2: pick hardware for your home server setup

There are four common classes of home server hardware. Each one fits a different set of jobs.

Old laptop

Free if you have one. It is quiet and uses little power. The limits are storage (usually one internal drive) and a single network port. It suits network services and a few small apps.

Old desktop

Free or cheap. It has room for several drives and more memory. It can be loud and use more power than you expect. It suits file storage, media and a first virtualization host.

Mini PC

Small, quiet and efficient. Many recent models have a CPU with good video transcoding. The limits are drive bays and network ports. Some have memory soldered to the board, so check the upgrade path before you buy. It suits apps, media and a small Proxmox host, with bulk storage kept on a separate box.

NAS box

A network-attached storage box is built for drives. It has several bays, hot-swap trays and its own OS. The CPU is often weak, so check it can run the apps you want. It suits storage first, with a few light apps.

Whatever you pick, check three things. The CPU must support hardware virtualization (Intel VT-x or AMD-V) if you plan to run VMs. You need a wired network port. And you need at least one SSD for the OS and apps.

Step 3: pick an operating system

The OS is the biggest choice in a home server setup. Four options cover most home servers. Check each vendor's site for current features and license terms as of October 2026.

OSWhat it isCost (verify)Best atWatch for
Proxmox VEHypervisor for VMs and LXC containersFree, optional paid subscriptionRunning many isolated services and test VMsStorage sharing needs extra setup
Ubuntu ServerGeneral Linux server OSFree, optional paid supportDocker hosts, simple setups, learning LinuxNo web UI by default, you use the command line
TrueNASStorage OS built on ZFSFree community edition, paid enterprise optionsReliable file storage with snapshotsApp and VM features are secondary to storage
UnraidStorage and app OSPaid licenseMixing drives of different sizes, easy appsNot open source, license cost

Here is a simple rule. If you want many separate services and test VMs, start with Proxmox VE. Read what Proxmox VE is and why home labs run it first. If storage is the main job, start with TrueNAS or Unraid. If you only want Docker containers, start with Ubuntu Server.

Official docs: Proxmox VE, Ubuntu Server, TrueNAS and Unraid.

You can also combine them. A common pattern is Proxmox VE on the host, with a TrueNAS VM for storage and LXC containers for apps. It adds steps and risk. The TrueNAS hardware guide says a virtualized TrueNAS is not safe for critical data. If you try it, pass the real disks or the whole disk controller (HBA) to the VM, never virtual disks, and keep a separate backup.

Before you add services: network basics

A home server lives on your home network. Spend twenty minutes on the network now and you avoid hours of confusion later.

  • Give the server a fixed IP address. Set a DHCP reservation in your router. Or set a static address on the server; if you do, pick an address outside the range your router hands out.
  • Use a wired connection. Plug the server into the router or a switch. Wi-Fi drops and slows file copies.
  • Name things. Give the server a short host name. Use the same naming pattern for every VM and container.
  • Know your router. Find the admin page, the DHCP range and the DNS settings. You will need them for the ad blocker.
  • Keep a fallback. If you point the whole house at a DNS server on your home server, keep a second DNS server set. Then the internet still works when the server reboots.

Later, you may want separate networks (VLANs) for the lab, smart home devices and guests. That needs a router and switch that support VLANs. It is a good second project, not a first one.

Step 4: your first five services

Do not install twenty apps on day one. Start with five that give real value. Add more once these run well.

  1. A DNS ad blocker. Pi-hole or AdGuard Home blocks ads and trackers for every device on the network. It is small and teaches you about DNS.
  2. File sharing. An SMB share for the household. On Proxmox, a small container can serve it. On TrueNAS or Unraid, it is built in.
  3. Photo backup. An app such as Immich backs up phones automatically. Treat this data as precious and back it up twice.
  4. A media server. Jellyfin or Plex streams your media library to TVs and phones.
  5. A dashboard or monitoring tool. Uptime Kuma or a simple dashboard shows what runs and what is down.

Many of these run as Docker containers. Read the Docker docs before you start. On Proxmox, decide if each service runs in an LXC container or in a VM. The guide to containers vs virtual machines helps you choose. For a wider view of what "virtualization" covers, see the types of virtualization.

Step 5: backups and remote access

Backups

Follow the 3-2-1 rule. Keep three copies of important data. Store them on two different types of media or devices. Keep one copy off site.

  • Use RAID or ZFS mirrors to survive a dead disk. Remember that RAID is not a backup. It does not protect you from deletion, ransomware or fire.
  • Back up VMs and containers on a schedule. Proxmox VE has backup jobs built in.
  • Copy the most important data off site. A cloud storage bucket or a drive at a relative's house both work.
  • Restore a file every month to prove the backup works.

Remote access

You will want to reach your server from outside the house. Do it safely.

  • Do not open ports on your router for admin pages. Never expose the Proxmox, TrueNAS or Unraid web interface to the internet.
  • Use a VPN. Tailscale, or a WireGuard server (which needs one forwarded UDP port), lets your phone and laptop join your home network securely.
  • Use strong, unique passwords and turn on two-factor login where the OS supports it.
  • Keep the system updated. Set a regular time each month to apply updates.

Common mistakes

  • Buying before deciding the jobs. You end up with the wrong drive count or a CPU that cannot transcode.
  • Mixing the lab and the family services. A test VM that eats all the memory can take down the photo backup. Set memory limits, or use separate hosts.
  • Treating RAID as a backup. It is not. Keep separate backup copies.
  • Exposing admin pages to the internet. Use a VPN instead.
  • No backup power. A small UPS protects the drives during a power outage and gives the server time to shut down cleanly.
  • No notes. Write down IP addresses, drive layouts and what each service does. Future you will thank you.

FAQ

What is the best OS for a home server?

It depends on the main job. Proxmox VE suits many separate services and VMs. TrueNAS suits storage first. Unraid suits mixed drive sizes and easy apps. Ubuntu Server suits a simple Docker host.

Can I use an old PC as a home server?

Yes. An old desktop is one of the best ways to start. Add an SSD for the OS and check the power use. If it is loud or uses a lot of power, a mini PC may cost less to run over time.

How much does a home server cost to run?

It depends on the hardware and your power price. A low-power mini PC uses far less than a full tower with many drives. Measure your server with a plug-in power meter and multiply by your rate.

Is a NAS the same as a home server?

A NAS is a home server built mainly for storage. Most modern NAS boxes can also run apps. A general home server is often stronger at apps and VMs but needs more setup for storage.

Do I need a static IP from my internet provider?

No. A VPN service such as Tailscale works without one. Inside your home, give the server a fixed local IP address so your devices can always find it.

Should I run Docker or Proxmox?

You can run both. Proxmox VE is the host. Docker runs inside a VM or an LXC container on top of it. If you only ever want Docker containers, a plain Ubuntu Server is simpler.

Related guides

What Is Proxmox VE? Why Home Labs Run It

Illustration of one physical server running several virtual machines and lightweight containers, the idea behind Proxmox VE

What is Proxmox? Proxmox VE (Proxmox Virtual Environment) is a free, open-source platform for running virtual machines and containers. It installs directly on a server, like an operating system. It uses KVM for full virtual machines and LXC for lightweight Linux containers, and you manage both from a web browser. Home labs and small teams use it because it does most of what paid hypervisors do, with no license fee to start.

Who this is for: you want to know if Proxmox fits your home lab or small business.

What is Proxmox, exactly?

Proxmox VE is a type 1 hypervisor. That means it runs directly on the hardware, not inside Windows or macOS. If the terms are new, start with the type 1 vs type 2 hypervisor guide.

Under the hood, Proxmox VE is Debian Linux with extra parts on top. The main parts are:

  • KVM and QEMU. These run full virtual machines. A VM can run Windows, Linux, BSD or most other x86 operating systems.
  • LXC. This runs Linux system containers. A container shares the host's Linux kernel, so it uses less memory and starts faster than a VM.
  • A web interface. You create, start, stop, back up and move VMs and containers from a browser.
  • Storage and network tools. Proxmox VE supports local disks, ZFS, LVM, NFS, iSCSI and Ceph, among others. It uses Linux bridges for networking.
  • Clustering. You can join several Proxmox hosts into one cluster and manage them from one screen.
  • Backups. Built-in backup jobs can save VMs and containers to a local disk, a network share or a separate Proxmox Backup Server.

The company behind it is Proxmox Server Solutions, based in Vienna, Austria. The product page and docs are at proxmox.com and pve.proxmox.com.

How the Proxmox VE license works

As of October 2026, Proxmox VE is open-source software released under the GNU AGPL v3 license. You can download it, install it and use it at no cost. All features are in the free version. There is no "lite" edition with features locked away.

The company earns money from optional subscriptions. Based on the vendor site, a subscription gives you:

  • Access to the enterprise package repository, which receives updates after more testing.
  • Technical support, at higher subscription levels.

Without a subscription, you use the "no-subscription" repository. It gets updates sooner and with less testing. Many home labs run this way. The web interface shows a reminder that you have no subscription. That reminder is normal.

License terms and subscription prices can change. Verify the current terms on the Proxmox website before you plan a business deployment. I do not quote prices here.

Who uses Proxmox VE?

Proxmox VE has three main groups of users.

Home labs

In my view, this is the most visible group online. Home lab users like Proxmox because it is free, runs on modest hardware and does VMs and containers in one place. A single mini PC can run a file server, a media server, an ad blocker and a few test VMs at once. The guide to what a home lab is and how to start one shows where Proxmox fits.

Small businesses and teams

Small IT teams use Proxmox VE to run file servers, domain controllers, line-of-business apps and backups. Many moved to it after VMware licensing changed. See Proxmox vs VMware in 2026 for a direct comparison.

Hosting providers and larger sites

Some hosting companies, schools and public bodies run Proxmox clusters at scale. They often pair it with Ceph for shared storage and buy subscriptions for support.

Strengths of Proxmox VE

  • No license fee to start. You can run every feature without paying.
  • VMs and containers side by side. You pick the right tool for each job on one host. Read containers vs virtual machines to choose between them.
  • Web interface for most tasks. You rarely need the command line for daily work.
  • Built-in clustering and live migration. With a cluster and shared storage, you can move a running VM to another host.
  • ZFS support out of the box. ZFS gives you checksums, snapshots and software RAID without extra tools.
  • Linux underneath. If you know Debian, you can fix most problems with skills you already have.
  • Active community. The official forum and the home lab community answer most beginner questions.

Limits and trade-offs

Proxmox VE is not perfect. Know the limits before you commit.

  • Some jobs need the command line. GPU passthrough, some storage setups and network tuning often need you to edit config files.
  • Support is not the same as a big vendor. Support comes from the subscription or from the community. Check that the support hours and response times suit your business.
  • Fewer third-party integrations. Many enterprise backup and monitoring tools support VMware first. Support for Proxmox is growing, but check each tool you depend on.
  • Clusters need care. A Proxmox cluster uses quorum. A two-node cluster needs an extra vote (a QDevice) or it can stop when one node goes down. Plan for three votes.
  • LXC containers are Linux only. You cannot run a Windows container in LXC. Use a VM for Windows.
  • Docker is not built in. Proxmox does not run Docker directly in its interface. You run Docker inside a VM or an LXC container. See the Docker docs for setup. As of October 2026, Proxmox also offers OCI images as application containers (converted to LXC) as a technology preview. Check the Proxmox docs before you rely on it.

Proxmox vs other hypervisors

People often search "Proxmox vs" a rival. Here is a short view of the four most common choices. License terms change, so treat the license column as a starting point. Check each vendor's site for current terms as of October 2026.

FeatureProxmox VEVMware ESXiMicrosoft Hyper-VXCP-ng
BaseDebian Linux with KVMVMware's own kernelWindows (Windows Server or client Hyper-V)Xen hypervisor
License modelOpen source, optional paid subscriptionCommercial, sold by Broadcom (verify current terms)Part of Windows licensing (verify current terms)Open source, optional paid support
Containers built inYes (LXC)NoWindows containers (separate feature)No
ManagementBuilt-in web UIHost web UI, vCenter for many hostsHyper-V Manager, Windows Admin CenterXen Orchestra (separate tool)
ClusteringBuilt inNeeds vCenterWindows failover clusteringBuilt-in pools
Best fitHome labs, small and mid-size teamsShops already deep in VMwareMicrosoft-centered shopsTeams that prefer Xen

For VMware's current editions, see the VMware vSphere docs. For Hyper-V, see the Microsoft Hyper-V docs.

What you need to run Proxmox VE

The hardware bar is low. Check the current minimum and recommended specs in the Proxmox docs. In broad terms you need:

  • A 64-bit x86 CPU with hardware virtualization (Intel VT-x or AMD-V). Turn it on in the firmware settings.
  • Enough memory for the host plus every VM and container you plan to run. Memory is the first limit most labs hit.
  • An SSD for the system and VM disks. Hard drives work but feel slow.
  • A wired network connection. Wi-Fi is not supported well for the host.

If you are choosing hardware from scratch, the home server setup guide compares old PCs, mini PCs and NAS boxes.

How to try Proxmox VE this week

You do not need spare hardware to try Proxmox VE. You can test it in three steps of growing commitment.

  1. Run it nested. Create a VM in a desktop hypervisor on your current computer. Give it at least two CPU cores, a few GB of memory and a 32 GB disk. Turn on nested virtualization for that VM. Install Proxmox VE inside it from the ISO image. This needs an x86 (Intel or AMD) computer. On an Apple Silicon Mac, Proxmox runs only under slow x86 emulation, so use a spare PC instead.
  2. Move to a spare machine. When you like what you see, install Proxmox VE on an old PC or a mini PC. This wipes the disk, so back up anything you need first.
  3. Run one real service. Pick one small service you will actually use, such as a network ad blocker or a file share. Put it in an LXC container. Live with it for a month.

Each step teaches you something new. The nested test teaches the interface. The spare machine teaches storage and networking. The real service teaches you how updates and backups feel over time.

Download the installer only from the official Proxmox website. Check the file checksum against the one the site publishes. Then write the image to a USB stick with a tool such as balenaEtcher or Rufus.

After install, the host shows a web address on its console screen. It uses port 8006 by default. Open it from another computer, log in as root with the password you set, and you are in.

What to watch for as a new user

  • The subscription reminder. It appears at login when you have no subscription. It does not limit features. Do not run random scripts from the internet just to hide it.
  • Repository settings. A fresh install does point at the enterprise repository. Without a subscription, updates from it fail. Switch to the no-subscription repository as the docs describe.
  • Consumer SSD wear with ZFS. ZFS and Proxmox write logs often. Cheap SSDs can wear faster. Watch the SSD health values over time.
  • Third-party helper scripts. Community scripts can save time. They also run as root on your host. Read a script before you run it.
  • Backups on the same disk. A backup on the same disk as the VM does not protect you from disk failure. Store backups somewhere else.

FAQ

Is Proxmox free?

Yes. As of October 2026, Proxmox VE is open source and free to download and use, with all features included. The company sells optional subscriptions for the enterprise repository and support. Verify current terms on the Proxmox website.

Is Proxmox a type 1 or type 2 hypervisor?

Proxmox VE is a type 1 hypervisor. It installs directly on the hardware and uses the KVM module in the Linux kernel. You do not install it inside Windows or macOS for daily use, though you can run it nested in a VM to learn it.

Can Proxmox run Windows VMs?

Yes. Proxmox VE runs Windows as a full VM through KVM. For good disk and network speed, install the VirtIO drivers inside the Windows VM. The Proxmox docs explain the steps.

Is Proxmox good for production?

Many businesses run Proxmox VE in production. For production, use the enterprise repository, plan your backups and test restores. Decide if you need a paid subscription for support before something breaks.

What is the difference between Proxmox and Docker?

Proxmox VE is a hypervisor that runs VMs and LXC system containers. Docker runs application containers on a Linux host. Many people run Docker inside a VM or LXC container on Proxmox, so they use both together. As of October 2026, Proxmox also runs OCI images as app containers as a technology preview. Verify its status in the Proxmox docs.

Does Proxmox need a powerful server?

No. Proxmox VE runs on a mini PC or an old desktop. What you need depends on your workloads. Memory and fast storage matter more than CPU for most home labs.

Related guides

What Is a Home Lab? How to Start One in 2026

Illustration of a small home lab on a shelf with a mini PC, network switch, NAS and a laptop managing virtual machines

A home lab is a small set of computers at home that you use to learn, test and run your own services. It can be one old laptop or a short rack of servers. Most home labs run a hypervisor, so one machine can host many virtual machines and containers. You can start one for zero dollars with hardware you already own.

Who this is for: you want to learn servers, networking or self-hosting, and you want a safe place to break things.

What is a home lab, in plain terms?

A home lab is a practice space for IT skills. It is like a workshop in a garage, but for software and networks. You build things, break them and fix them. Nothing you do there can take down a production system at work.

The word "homelab" (one word) means the same thing. People use both spellings.

Most home labs share three parts:

  • A host. This is the physical computer. It can be a laptop, a desktop, a mini PC or a used server.
  • A virtualization layer. This is the software that splits one host into many virtual machines (VMs) or containers. Proxmox VE is a common choice. If the term is new, read what a hypervisor is and how type 1 and type 2 differ.
  • Workloads. These are the things you run: a file share, a media server, an ad blocker, a test domain controller, a Kubernetes cluster.

A home lab is not the same as a home server, but the two overlap. A home server runs services you depend on every day. A home lab is where you experiment. Many people start with a lab and end up with a server that the family uses. The home server setup guide covers that side in detail.

Why people build a home lab

People build home labs for four main reasons.

To learn job skills

Certifications and job interviews ask about Linux, networking, virtualization and cloud. Reading is not enough. You learn faster when you install a system, misconfigure it and then find the fault. A lab gives you that loop at no risk.

To self-host services

Some people want to own their data. They run their own photo backup, password manager, media server or home automation. A lab lets them host these services instead of paying a monthly fee to a cloud provider. You still pay for power and hardware, so do the math for your own case.

To test before production

If you run IT for a small business, a lab is a safe copy of your setup. You can test an update, a firewall rule or a backup restore before you touch the real thing.

Because it is fun

This is a real reason. Many people enjoy building systems. A lab is a hobby with useful side effects.

What does a home lab cost?

A home lab can cost nothing or a few hundred dollars to start. Some people spend much more, but you do not need to.

  • Zero dollars: use the computer you already have. Run VMs inside a desktop app.
  • Low cost: reuse an old desktop or laptop that sits in a closet. Add memory or an SSD if it needs it.
  • A few hundred dollars: buy a used business mini PC or a new low-power mini PC. Many of these sell refurbished.

Prices for hardware change every month. I do not quote them here. Check current listings before you buy.

Do not forget the running cost. A machine that runs all day uses power all day. A small, low-power machine often costs less to run over a year than a big, cheap used server. Measure your own draw with a plug-in power meter.

Three ways to start a home lab setup

You do not need to pick the perfect path. Pick the one that matches what you have today. You can move later.

Path 1: nested on your laptop or desktop

You install a desktop hypervisor such as Oracle VirtualBox or VMware Workstation. Then you create VMs inside it. You can even install Proxmox VE inside a VM to learn it. This is called nested virtualization. This needs an x86 (Intel or AMD) computer. On an Apple Silicon Mac, Proxmox runs only under slow x86 emulation, so use a spare PC instead.

This path is free and fast. The limits are memory and uptime. Your VMs stop when you close the laptop. A laptop with 8 GB of memory gets tight quickly. 16 GB or more is more comfortable for two or three VMs.

To compare desktop tools, read VMware vs VirtualBox vs Proxmox for a desktop lab.

Path 2: an old PC as a dedicated host

You take an old desktop or laptop and wipe it. Then you install a type 1 hypervisor, such as Proxmox VE, directly on the hardware. The machine now runs all the time and you manage it from a web browser on another device.

This path costs little. Old desktops often have room for more drives and more memory. The trade-offs are noise, size and power use. Check that the CPU supports hardware virtualization (Intel VT-x or AMD-V) and that it is turned on in the firmware settings.

Path 3: a mini PC

You buy a small, low-power PC and install Proxmox VE on it. Mini PCs are quiet, small and cheap to run. Many people now start here.

The limits are expansion and network ports. Most mini PCs take one or two drives and have one or two network ports. Check the memory limit before you buy. Some models have soldered memory that you cannot upgrade.

Compare the three starting paths

PathStart costRuns 24/7?Best forMain limit
Nested on your laptopZeroNoLearning the basics, short testsMemory, and the VMs stop when the laptop sleeps
Old PC as a hostZero to lowYesA first real host, more drivesNoise, size, power use
Mini PCLow to a few hundred dollarsYesA quiet, always-on labFew drive bays, few network ports

What software runs a home lab?

Most home labs use a type 1 hypervisor on the host. A type 1 hypervisor runs directly on the hardware, not on top of Windows or macOS.

Proxmox VE is a popular choice for home labs. As of October 2026, it is free to use with an optional subscription. Verify on the Proxmox site. It runs both VMs and containers, and you manage it from a web page. Read what Proxmox VE is and why home labs run it for the full picture. The official documentation is at pve.proxmox.com.

Other options exist:

  • VMware ESXi. Long the default in business. Licensing changed after Broadcom bought VMware. Check the current terms on the VMware site. Then see Proxmox vs VMware in 2026 before you choose it.
  • Microsoft Hyper-V. Built into Windows Server and some editions of Windows. Good if you want to learn a Microsoft stack. See the Hyper-V docs.
  • XCP-ng. An open-source hypervisor based on Xen. It has a smaller home lab community than Proxmox.
  • A plain Linux server with Docker. No hypervisor at all. See the Docker docs. Good if you only want to run containers.

Containers and VMs solve different problems. If you are not sure which you need, read containers vs virtual machines.

Your first week with a home lab

Here is a simple plan. Do one step per evening.

  1. Pick your path from the three above.
  2. Install the hypervisor. For Proxmox VE, write the installer image to a USB stick and boot from it.
  3. Give the host a fixed IP address on your home network. Write it down.
  4. Log in to the web interface from another computer.
  5. Create one Linux VM. Ubuntu Server or Debian is a good first choice.
  6. Create one container and run a small service in it, such as an ad blocker for your network.
  7. Set up a backup job for both. Then restore one to prove the backup works.

Step 7 is the one most people skip. Do not skip it. A backup you have never restored is only a hope.

Common mistakes

  • Buying too much too soon. A rack of used servers looks great. It is also loud, hot and costly to run. Start small. Grow when you hit a real limit.
  • Running the lab on the family network with no plan. One bad DHCP or DNS setting can break the internet for the whole house. Test network changes when nobody depends on the connection.
  • Exposing services to the internet. Do not expose admin pages to the internet. Use Tailscale, or a WireGuard server (which needs one forwarded UDP port).
  • No backups. Your lab will fail. Disks die and updates go wrong. Keep backups on a different disk, ideally a different machine.
  • Not writing things down. Keep a simple text file of IP addresses, passwords (in a password manager) and what each VM does. In three months you will not remember.
  • Ignoring the memory limit. Memory runs out before CPU in most labs. Check how much your host can take before you buy it.

FAQ

Is a home lab worth it?

For most people who want to learn IT or self-host, yes. You learn by doing, and a lab gives you a place to do it with no risk to real systems. If you only want one service, such as a media server, a single home server may be enough.

How much RAM do I need for a home lab?

Memory is usually the first limit you hit. 16 GB is a comfortable start for a few small VMs and containers. 32 GB or more gives you room for a test cluster or heavier services. Containers use far less memory than full VMs.

What is the difference between a home lab and a home server?

A home server runs services that you and your family depend on every day. A home lab is a place to experiment and break things. Many people run both on one machine, but it is safer to keep critical services away from your test VMs.

Can I run a home lab on a laptop?

Yes. You can run VMs inside a desktop hypervisor, or install Proxmox VE on an old laptop. A laptop has a built-in battery, which acts like a small backup power supply. But a battery held at full charge for months can swell, so check it. The limits are memory, storage and network ports.

Is Proxmox good for beginners?

Yes, with some patience. The installer is simple and the web interface covers most tasks. You will need basic Linux skills for some jobs. The official docs and forum are large and active.

Do I need a server rack?

No. Most home labs sit on a shelf or a desk. A rack makes sense when you have several machines, a network switch and a backup power supply to organize.

Related guides