How to Get Started With Proxmox VE: A Beginner's Guide

What Proxmox VE actually is

Proxmox VE (Virtual Environment) is a free, open-source platform for running virtual machines and containers on your own hardware. It installs directly on a physical machine, the way an operating system would, rather than running on top of one. That makes it a type-1 hypervisor: your PC or server becomes a dedicated host for other machines, not a desktop you also browse the web on.

It is built on Debian Linux and managed through a web dashboard (no command line required for day-to-day use). Proxmox VE 9.0 was announced on August 5, 2025, based on Debian 13 "Trixie" with a 6.14.8-2 kernel. Proxmox VE 9.2 (the current release as of this writing) was released on May 21, 2026. Built on Debian 13.5, it ships with Linux kernel 7.0 as the new stable default, alongside QEMU 11.0, LXC 7.0, and ZFS 2.4. It is the tool most home lab guides recommend once a single host stops being enough.

Turn off the subscription nag (optional)

If you log into a fresh Proxmox install, you will see a "No valid subscription" warning dialog. Proxmox is free, but by default, it points to an enterprise update repository that requires a paid key.

You do not need to buy one to use the software. The difference between the free version and the paid tiers is support access and enterprise-repository update timing, not software functionality. Every home lab install uses the free, no-subscription repository, which receives updates slightly later than the enterprise repo and is explicitly "not recommended on production servers" by the official wiki.

Switch the update source to the no-subscription repository (in the web UI under your node, then Updates > Repositories) so apt stops failing on the enterprise repo. That fixes updates but not the login popup; the popup only goes away with a paid key or a community post-install script that patches the web UI. Functionally, your server works the same either way. For those bringing Proxmox into a business environment, subscription options are priced per CPU socket, per year:

Subscription pricing

Proxmox vs. the alternatives

If you are already running a few containers with Docker Compose, you might wonder why you need a hypervisor at all. The difference is isolation and flexibility: Docker shares one kernel across every container, while Proxmox lets you run full VMs alongside lightweight containers on a single host.

(Note: Proxmox's own "comparison" page is a self-description of its own feature set, not a feature-by-feature matrix against rivals. The comparison data for XCP-ng and Unraid below is drawn from secondary community analysis.)

Broadcom restored a free entry-level ESXi tier in April 2025, but clustering and high availability still require paid vSphere licenses. Hyper-V's free standalone edition is genuinely discontinued, meaning it is effectively no longer a no-cost home-lab option. Proxmox gives you full VMs and LXC containers managed from one dashboard, with clustering included for free.

Hardware you actually need

Proxmox's official minimum requirements for evaluation (not production) are a 64-bit x86 CPU (Intel 64/AMD64) with Intel VT/AMD-V or a 64-bit ARM (ARMv8-A+) processor, 1 GB of RAM for the host (plus extra for your guests), a hard drive, and a single NIC. Treat that as a strict "will it boot" baseline.

For a usable home lab running a handful of services, aim for the recommended production requirements:

System requirements

• CPU: any consumer CPU from the last 6-8 years with virtualization support enabled in BIOS.
• RAM: 8GB minimum, 16-32GB comfortable if you plan to run several VMs at once.
• Storage: an SSD for the boot drive and VM storage.
• Network: a wired gigabit connection.

Many home labs start on repurposed office PCs or mini PCs bought secondhand. For example, popular community guides showcase setups running multiple VMs and containers on an aged Ryzen 5 1600, or robust standalone servers using an Intel NUC with an i7 processor and 64 GB of RAM. A secondary NVMe drive is often recommended as an LVM-thin pool for VM storage, keeping your boot drive completely separate. The official requirements also list 64-bit ARM (ARMv8-A or newer) CPUs, but x86 mini PCs remain the easiest starting point, since that is where nearly all community guides and tested hardware sit.

Installing Proxmox VE and creating your first VM

Your first VM walkthrough

Once you are in the dashboard, setting up a VM takes only a few clicks:

1. Get an OS image: Expand your node on the left, click on your local storage, and select ISO Images. You do not need to download the ISO to your computer first; use the built-in Download from URL button to fetch a Linux image directly to the server.
2. Start the wizard: Click Create VM in the top right corner. Adopt a clear naming and tagging convention for your VMs early on.
3. OS: Select the ISO you just downloaded.
4. System: Leave defaults (or enable Qemu Agent if you plan to install it in the guest).
5. Disks: Set your disk size. Make sure the storage target is your local-lvm (or equivalent thin pool), not the directory where you keep ISOs.
6. CPU & Memory: Allocate cores and RAM.
7. Network: Pick the default vmbr0 bridge.
8. Confirm: Finish the wizard, right-click your new VM, and click Start. Open the Console tab to run through the OS installation.

You can follow a nearly identical wizard (clicking Create CT) to spin up an LXC container using a downloaded template. Use the built-in Notes field for documenting your configuration decisions on each VM. Additionally, delay setting up clustering until you encounter a problem that genuinely requires it; keeping a single-node setup is much easier to manage when you are first learning the system.

VM or LXC container: how to choose

This is the decision new users get wrong most often.

Rule of thumb: reach for an LXC container by default. LXC uses meaningfully less RAM than KVM for idle workloads. According to the official wiki, LXC containers can only run Linux guests, rely on shared-kernel namespace isolation (AppArmor/seccomp) rather than full isolation, and support up to 10 network interfaces and 256 mount points. They also do not support live migration natively (the workaround is nesting them inside a VM). Only spin up a full VM when you specifically need a different operating system, stronger isolation, or software that does not behave well containerized.

Basic networking: bridges and VLANs

When you install Proxmox, it creates a default virtual bridge called vmbr0 tied to your physical network card. Think of this bridge as a virtual network switch. When you create a VM or container, you attach its virtual network interface to vmbr0, and it gets an IP address from your home router just like a physical device would.

For most beginner home labs, one bridge is all you need. If you want to isolate traffic (for example, keeping guest services separate from your trusted network), the simplest approach is to use VLAN tagging. Instead of creating multiple bridges, leave your VMs on vmbr0 and assign a VLAN tag directly to the VM's virtual network interface in the Proxmox UI.

Backups: don't skip this

Proxmox includes a built-in backup tool called vzdump that can back up an entire VM or container to a file, on a schedule, without you writing any scripts. Set it up in Datacenter > Backup as soon as you have your first service running, pointing at a second disk or a network share.

A backup on the same disk as the thing it is backing up is not a backup. Furthermore, a snapshot is not a backup: it lives on the same storage as the VM and is for quick rollback during config changes, not disaster recovery.

Where Proxmox fits in a wider home lab

Once Proxmox is running, it becomes the foundation everything else sits on. Popular first services include an automation server such as n8n, which runs well in a small LXC container. Check the best open source projects for home labs for a fuller list of what to deploy once your hypervisor is up.

FAQs