Somewhere between "my NAS needs more RAM" and "I just spent four hours reading about hypervisors," most homelab owners run into the same word over and over: Proxmox. It shows up in every self-hosting subreddit, every YouTube build video, every forum thread about ditching VMware. But nobody stops to explain what it actually is before telling you to install it.

That's the gap this article fills. Before you download an ISO or wipe a drive, it helps to know what you're looking at, what problem it solves, and whether it's actually the right tool for your situation. If you've already decided and just want the install steps, we've got a full walkthrough for that. This one is about the "what" and "why" that usually gets skipped.

What You Will Learn

  • What Proxmox VE actually is, in plain terms
  • The technology it's built on, and why that matters to you
  • Who it's for, and a few cases where it isn't the right pick
  • What you need before you try it
  • How to get your first real look at it without committing a whole machine
  • A few commands worth knowing on day one
  • The mistakes and error messages that trip up almost everyone at the start

What Is Proxmox VE?

Proxmox VE (short for Virtual Environment) is a free, open-source platform for running virtual machines and containers on your own hardware. You install it directly on a physical computer — an old desktop, a rack server, a mini PC, whatever you've got — and it turns that machine into a small data center. From there, you create virtual machines running Windows, Ubuntu, pfSense, or almost anything else, all managed from a web browser.

It's built on top of Debian Linux, and it's currently on the 9.x release line (9.2 as of mid-2026), using a rolling-release model where updates land continuously rather than in big yearly jumps. Under the hood it combines two different virtualization technologies:

  • KVM (Kernel-based Virtual Machine) — full virtualization. Each VM gets its own virtual hardware and runs a complete, independent operating system. This is what you use for Windows, or any OS that needs to be fully isolated from the host.
  • LXC (Linux Containers) — lightweight, OS-level virtualization. Containers share the host's Linux kernel instead of emulating hardware, so they start in a couple of seconds and use a fraction of the RAM. You'd use this to run a single Linux service, like a Pi-hole or a small web app.

Both live side by side in the same web interface, which is really the whole pitch: one login, one dashboard, and you can spin up either kind of guest depending on what the job needs.

Proxmox VE is licensed under the AGPLv3, and the software itself is completely free — there's no paywall, no feature you're locked out of for not paying. What Proxmox sells is support and a curated "enterprise" update repository that's tested more conservatively before packages land. Everyone else uses the no-subscription repository, which gets the same updates a little sooner and with less pre-release testing. Homelabbers overwhelmingly run the free repo, and it's stable enough that most people never think about it again after the first setup.

Why Would You Use It?

The honest answer: because running one service per physical machine is a waste of hardware, and juggling a pile of single-purpose boxes gets old fast. A hypervisor lets you carve one machine into many, so your Plex server, your Pi-hole, your Home Assistant instance, and your test VM for "that thing I want to try" can all live on the same box without stepping on each other.

Proxmox specifically tends to come up for a few reasons:

  • It's free and unrestricted. No trial period, no feature gate, no core-count license like you'd run into with some commercial hypervisors.
  • It's approachable. The web GUI covers most day-to-day tasks — you don't need to live in the command line, though it's there if you want it.
  • It scales with you. Start with one box in a closet. Add a second later and cluster them together for live migration and shared storage. Nothing about the single-node setup gets thrown away when you grow.
  • It's the free landing spot for a lot of ex-VMware users. After Broadcom's licensing changes, a lot of admins who used to run ESXi at home (or even at work) started looking at Proxmox as the no-cost option that still feels like a "real" enterprise hypervisor.

It's not the right fit for everyone, though. If you only ever need one Linux box doing one job, a hypervisor is overhead you don't need — just run the service directly. And if your work already lives entirely in a public cloud, Proxmox doesn't replace that; it's for hardware you own and control yourself.

Prerequisites

You don't need much to take a first look, but a real install has a few actual requirements:

  • A 64-bit CPU (Intel 64 or AMD64) with virtualization support — Intel VT-x or AMD-V. Almost anything from the last decade has this, but it's sometimes disabled in the BIOS by default.
  • At least 2 GB of RAM for the host itself, plus however much you plan to hand out to VMs. 8 GB is a comfortable starting point for a homelab box running a few small guests.
  • A drive to install onto — Proxmox will use the whole disk by default, so don't point it at anything with data you care about.
  • One network port, wired. Proxmox doesn't officially support Wi-Fi for the management interface, and you'll have a much easier time with a cable.
  • A USB drive (8 GB or larger) to write the installer ISO to, and a way to reach the machine's boot menu.

None of this needs to be new or expensive. A lot of home Proxmox nodes started life as a discarded office PC or an eBay-bought mini PC with a low-power Celeron in it.

Step-by-Step Tutorial

This isn't the full install walkthrough — we've written a separate, dedicated guide for that with every screen covered. What's useful here is a quick, low-commitment way to actually see Proxmox VE running before you decide to dedicate hardware to it.

  1. Check virtualization is enabled. Reboot the machine you're testing on, enter the BIOS/UEFI setup, and look for a setting called Intel VT-x, AMD-V, or sometimes just "Virtualization Technology." Turn it on if it isn't already.
  2. Download the installer ISO. Grab it from the official Proxmox download page. The file is a few gigabytes, so plan for that on a slower connection.
  3. Verify the checksum. The download page lists a SHA256 sum next to the file. On Linux or macOS, run sha256sum proxmox-ve_9.x.iso and compare it against the published value. It's a habit worth having for any OS installer, not just this one.
  4. Write it to a USB drive. Tools like Rufus (Windows) or Etcher (Windows/macOS/Linux) both work. Rufus in particular needs "DD mode" for this ISO — the default "ISO mode" writes a disk that won't boot correctly.
  5. Boot from the USB drive. You'll land in the Proxmox installer. You don't have to complete the install just to look around — the first few screens (welcome, EULA, target disk) will show you the general shape of the process even if you back out afterward.
  6. If you want to go further without touching real hardware, you can run the installer inside a VM in VirtualBox or VMware Workstation with nested virtualization enabled. It's slower and a little fiddly to set up, but it's a genuinely safe way to click through a full install and log into the web interface with zero risk to your actual PC.
  7. Log into the web interface. Once installed (for real or in a test VM), point a browser at https://<the-ip-address>:8006. You'll hit a certificate warning — that's expected, covered below — and then a login screen. The default user is root with whatever password you set during install.

That's genuinely enough to get a feel for the interface: the Datacenter view on the left, the node underneath it, and buttons for Create VM and Create CT sitting right at the top. Everything past this point is either "install it for real," which the dedicated guide covers step by step, or "start creating VMs," which is its own topic entirely.

Commands Explained

You can run Proxmox entirely from the browser, but a few commands are worth knowing from day one, usually run over SSH once you've enabled it:

pveversion

Prints the installed Proxmox VE version and the kernel it's running. It's the first thing to check when you're troubleshooting or reporting a bug, since behavior can differ meaningfully between point releases.

pvesh get /nodes

pvesh is a CLI tool that talks to the same internal API the web GUI uses. This particular command lists every node in your cluster (just one, if you're running standalone) along with its status. It's a useful sanity check that the management stack is actually healthy.

qm list

Lists every virtual machine on the node — ID, name, status, memory allocation. qm is the command-line tool for managing VMs specifically; containers have their own equivalent.

pct list

The container version of qm list. pct stands for Proxmox Container Toolkit, and it's what you'd use to start, stop, or inspect LXC containers from the shell.

None of these are required to use Proxmox day to day — the web GUI genuinely covers most of what a beginner needs. But when something's not showing up correctly in the browser, these are usually the fastest way to check what's really going on underneath it.

Common Errors

A handful of messages show up for almost everyone in the first hour, and none of them mean anything is actually broken:

  • "Your connection is not private" / certificate warning in the browser. Proxmox generates its own self-signed SSL certificate during install so the web interface works over HTTPS immediately. Browsers don't trust it by default because it wasn't issued by a recognized certificate authority. You can click through it (Advanced → Proceed) or replace it later with a Let's Encrypt certificate if the node has a real domain name pointed at it.
  • "No valid subscription" pop-up after login. This shows up if you're using the free, no-subscription repository without a paid support plan — which is the normal setup for almost every home user. It's a nag, not an error. It doesn't disable or limit anything.
  • "TASK ERROR: command … failed" during apt update. This usually means the node is still pointed at the enterprise repository, which requires a subscription key to access. Swapping it for the no-subscription repo (a one-line change in /etc/apt/sources.list.d/) fixes it immediately.
  • Web interface won't load at all. Almost always one of two things: you forgot the :8006 port in the URL, or a firewall between you and the box is blocking it. Ping the host first to confirm basic connectivity before chasing anything more complicated.

Troubleshooting

If you're stuck earlier than any of that — the installer won't boot, or the machine won't even see the USB drive — check these in order:

  • Boot mode mismatch. Some older BIOS setups default to Legacy/CSM boot while the USB was written for UEFI, or the other way around. Check the boot menu (usually F11 or F12 on startup) and try switching modes if the drive isn't listed.
  • Bad USB write. If Rufus was left in "ISO mode" instead of "DD mode," the resulting drive often won't boot at all, or hangs partway through. Rewriting with DD mode selected almost always fixes this.
  • Virtualization disabled in BIOS. The installer will run fine either way, but VMs won't start afterward if VT-x/AMD-V is off. This is the single most common "why won't my VM start" report from people who just finished installing.
  • No network after install. Proxmox creates a bridge (usually named vmbr0) during setup and binds it to whatever NIC you selected. If the wrong interface got picked, or you've got multiple NICs and picked the disconnected one, the management IP won't respond. This is fixable from the local console even without network access.

Best Practices

A few habits that save people from redoing work later:

  • Test on spare hardware first if you can. Even an old laptop is enough to get a feel for the interface before you commit a "real" server to it.
  • Stick with the no-subscription repo unless you're paying for support. It's what almost every home user runs, and it's plenty stable for that use case.
  • Don't install onto the only copy of a disk with existing data. The installer will happily wipe whatever's there.
  • Give the host itself a static IP before you build anything on top of it. Losing track of the management IP because your router handed out a new DHCP lease is a genuinely common self-inflicted headache.
  • Read the release notes before major version upgrades (like 8.x to 9.x). They're short, and skipping them is how people end up with a broken cluster mid-upgrade.

Frequently Asked Questions

Is Proxmox VE really free?

Yes. The full software is free and open source under the AGPLv3 license. Paid subscriptions only cover support and access to the more conservatively tested enterprise repository — no features are locked behind payment.

What's the difference between Proxmox VE and Proxmox Backup Server?

Proxmox VE is the hypervisor — it runs your VMs and containers. Proxmox Backup Server is a separate product built specifically for storing and deduplicating backups, often installed on its own machine. You can use Proxmox VE without ever touching Backup Server.

Can I run Proxmox VE on a laptop?

You can, and plenty of people do for testing. Battery behavior and sleep/lid settings can be finicky since Proxmox expects a server that stays powered on, so it's better suited to something that'll run 24/7.

Do I need to know Linux to use it?

Not really, for the basics. The web GUI handles most tasks without needing shell access. Knowing your way around a Linux command line helps once you go past the basics, but it's not a hard requirement to get started.

Does Proxmox VE need an internet connection to run?

No, once installed it runs fine offline. You'll want internet access for updates and for downloading ISO images for your VMs, but the hypervisor itself doesn't phone home to function.

Is Proxmox VE the same as VMware ESXi?

They solve the same basic problem — running multiple VMs on one physical machine — but they're different products from different companies with different licensing models. If you're coming from ESXi specifically, it's worth reading a direct comparison before switching.

Conclusion

Proxmox VE is, at its core, a free way to turn one physical machine into several useful virtual ones, using the same KVM and LXC technologies that plenty of much more expensive platforms are built on. That's really the whole idea — the rest is interface and convenience on top of it.

If any of this sounded like it fits what you're trying to do, the next reasonable step is downloading the ISO and trying the install on whatever spare hardware you've got sitting around. It doesn't need to be your final setup. It just needs to be enough to see whether the workflow clicks for you.