Proxmox Virtual Environment (VE) is a professional open-source virtualization platform developed by the Austrian company Proxmox Server Solutions. Starting with version 9 (2025), the platform is built on Debian 13 (Trixie) and offers two types of virtualization: full (KVM) and container-based (LXC) in a single management interface.
Key technologies in Proxmox VE 9
Proxmox brings together every tool needed to manage infrastructure in one web interface:
- KVM (Kernel-based Virtual Machine) — full hardware virtualization, supporting Windows, Linux, FreeBSD.
- LXC (Linux Containers) — lightweight containers with no hypervisor overhead.
- Ceph — a built-in distributed storage system.
- ZFS — a filesystem with deduplication, snapshots, RAID-Z.
- Proxmox Backup Server — an integrated backup system with block-level deduplication.
What is new in Proxmox VE 9
| Feature | PVE 8 | PVE 9 |
|---|---|---|
| Base OS | Debian 12 (Bookworm) | Debian 13 (Trixie) |
| Linux kernel | 6.8 | 6.11+ |
| QEMU | 8.1 | 9.2 |
| ZFS | 2.2 | 2.3 |
| Ceph | Reef (18.x) | Squid (19.x) |
Proxmox vs the competition
| Criterion | Proxmox VE | VMware ESXi | Hyper-V |
|---|---|---|---|
| License | Open Source (AGPLv3) | Commercial | Commercial |
| Price | Free / subscription | High | Bundled with Windows Server |
| KVM/LXC | Both | VMware only | Hyper-V only |
| Web interface | Built in | Separate vCenter | Windows Admin Center |
| Cluster | Up to 32 nodes | Up to 96 nodes (vSphere) | Up to 64 nodes |
Free to use: Proxmox VE is fully functional without a subscription. A paid subscription grants access to the enterprise repositories with updates and official support, but it does not unlock any feature that is otherwise disabled.
Proxmox VE 9 system requirements
- CPU: a 64-bit processor with Intel VT-x or AMD-V support.
- RAM: 2 GB minimum (8+ GB recommended for production).
- Storage: 32 GB minimum for the install.
- Network: 1 Gbit/s Ethernet (a cluster needs at least 2 interfaces).
Common first-boot errors explained
- TASK ERROR: command 'apt-get update' failed: exit code 100 right after installation — the server is pointed at the enterprise repository without an active subscription; switch to the free
pve-no-subscriptionrepository in the sources list. - WARNING: CPU does not support KVM extensions when creating the first VM — virtualization (Intel VT-x / AMD-V) is disabled in the BIOS/UEFI; enable it in the motherboard settings and reboot the host.
- Login failed. Please try again — permission denied (401) in the web interface with correct credentials — the host's system clock has drifted from real time, so the authentication token is treated as expired; check
timedatectl statusand enable NTP sync. - storage 'local-lvm' is not online after an unexpected reboot — the LVM-thin volume did not activate automatically; it is usually fixed with
vgchange -ayfollowed by checkingpvesm status.
Architecture and components
The step-by-step install process is covered in installing Proxmox VE 9 on a server, and creating the first machine is covered in creating a virtual machine in Proxmox VE.
Proxmox VE runs as a bare-metal hypervisor — it installs directly on the hardware and manages all of the server's resources. The web interface is available on port 8006 over HTTPS right after installation.
# Check the status of all VMs and containers
qm list
pct list
# Proxmox version
pveversion -vImportant: do not install Proxmox VE on top of an existing Debian/Ubuntu system without risking package conflicts. Use only the official ISO installer from proxmox.com — it guarantees the correct kernel version and full component compatibility.
Licensing options
| Plan | Price/year (per socket) | What is included |
|---|---|---|
| Community | Free | Every feature, community forum, no-subscription repo |
| Basic | EUR 119 | 3 support tickets/year, enterprise repo |
| Standard | EUR 299 | 10 tickets, 2-business-day SLA |
| Premium | EUR 599 | Unlimited tickets, 4-hour SLA |
When Proxmox is not the best choice
- The company already has a team deeply expert specifically in vSphere/vCenter, and rebuilding processes and retraining staff costs more than paying for VMware licenses — migrating for its own sake rarely pays off.
- Maximum virtual desktop (VDI) density is needed with ready-made brokers like Horizon — the Proxmox ecosystem around VDI is weaker than specialized commercial solutions.
- The infrastructure is entirely on Hyper-V and tied to System Center and Windows-specific Active Directory tooling — moving to a Linux hypervisor means reworking the whole automation chain, not just swapping the virtualization platform.
How to verify the installation succeeded
# The web interface responds over HTTPS
curl -kI https://SERVER_IP:8006/
# Cluster and storage services are up
systemctl status pve-cluster pvedaemon pvestatd
# Storage is present and available
pvesm statusIf the web interface returns HTTP 200 at https://SERVER_IP:8006/, the key services show active (running), and pvesm status reports storage as active, the installation completed correctly and the host is ready for the first VMs and containers.
Proxmox VE 9 is a mature solution used by thousands of hosting providers, IT departments and home labs around the world. Open code, a rich API and an active community make it a strong choice for virtualization without vendor lock-in.