Proxmox

Buying the right GPU for your homelab is one decision. Getting Proxmox to actually hand that GPU to a VM or container is a separate one, and it’s where a lot of people get stuck, because Proxmox actually supports two completely different ways to do it, and picking the wrong one for the job means either a fight with IOMMU groups you didn’t need to have, or a container that can’t do what you needed a full GPU for. Here’s what each path actually requires, and how to pick between them. ...

RAM is one of the easiest specs to either badly underbuy or badly overbuy in a homelab, because the honest answer to “how much do I need” is “it depends on what you’re actually running,” and most buying guides dodge that and just tell you to get 32GB or 64GB and move on. That’s not wrong exactly, but it skips the reasoning that lets you size correctly for your own setup instead of someone else’s. Here’s how to actually work it out, plus the ECC question that comes up right behind it. ...

Proxmox makes joining a second node to a cluster look almost too easy, one command on the joining node and you’re done, centralized management across both boxes in the web UI. What that quick setup doesn’t make obvious is how much more you need to build on top of it before a cluster gives you the thing most people actually want from one: automatic failover when a node dies. This is the gap that catches people, they cluster two or three nodes, assume they now have redundancy, and find out during an actual outage that a VM doesn’t restart anywhere because nothing was wired up to make that happen. Here’s what clustering actually gets you, what it costs, and an honest read on whether it’s worth doing in a home setup versus running solid standalone nodes. ...

“Do I need a GPU for this” comes up constantly in homelab planning, usually attached to one of two very different goals: hardware-accelerated transcoding for Plex or Jellyfin, or running local AI workloads like Ollama or Stable Diffusion. Those two goals point at completely different hardware, and buying for one when you actually need the other is one of the more common expensive mistakes in this hobby. Here’s how to figure out which category you’re actually in before you spend anything. ...

Proxmox sets up a single bridge during install, vmbr0, hands every VM and container a virtual NIC on it, and most homelabs never touch networking again after that. That’s fine right up until you want to keep your NAS traffic off the same broadcast domain as a VM you don’t fully trust, or you add a second NIC and aren’t sure whether to bond it or split it out, or you’re staring at a VLAN dropdown in the VM hardware tab with no idea what happens if you fill it in wrong. None of this is complicated once you see the shape of it, but Proxmox’s networking config is also one of the few places where a bad change locks you out of the box that’s hosting the config, so it’s worth understanding before you’re mid-edit over SSH. ...

Proxmox hands you two completely different ways to run a workload, LXC containers and full VMs, and the “New CT” and “Create VM” buttons sit right next to each other in the UI like the choice barely matters. It matters. Pick the wrong one for a given workload and you’ll either waste resources you didn’t need to waste, or hit a wall six months in when something a container fundamentally can’t do turns out to be exactly what you needed. Here’s how to actually decide, workload by workload, instead of defaulting to whichever one you set up first. ...

Ask “what should I run Proxmox on” in any homelab community and you’ll get two camps talking past each other, one pushing a mini PC (an Intel NUC-style box, a Beelink, a Minisforum), the other pushing a custom build in a real case with expansion slots. Both are right, for different homelabs. The question isn’t which is objectively better, it’s which set of tradeoffs actually matches what you’re going to do with the box. ...

Proxmox will let you install onto ZFS during setup with a few checkboxes and move on with your life, and that’s exactly how a lot of people end up with a storage layout they didn’t actually choose. ZFS is the best storage option built into Proxmox for most homelab setups, but it comes with tradeoffs that are easy to ignore during install and expensive to fix once you’ve got VMs and containers living on top of it. Here’s what the pool layout choices actually mean, what ZFS does to your RAM, and how to pick a shape you won’t be re-doing in six months. ...

Backups are the thing every homelab guide tells you to do and almost nobody actually verifies works until the day they need it. Proxmox makes this easier than most platforms because it ships a real backup product, Proxmox Backup Server (PBS), instead of leaving you to bolt one on yourself. Here’s how to actually set it up, what it buys you over the built-in vzdump backups, and the one step most people skip that makes the whole thing worthless if you never do it. ...

Updated Aug 12, 2026: expanded with licensing detail, backup tooling, migration notes, and a decision table. Every homelab thread eventually turns into a hypervisor argument. Here’s the practical version, based on what actually matters when it’s your own gear and your own time on the line. The short answer If you’re starting fresh in 2026, run Proxmox VE. It’s free, actively developed, has a real community, and does everything most home labs need - VMs, LXC containers, clustering, ZFS, and a web UI that doesn’t feel like an afterthought. The rest of this post is for the “but why” crowd. ...