Beginner’s Guide to Installing Proxmox VE

Proxmox VE installs from its own ISO and replaces whatever is on the disk — it is a Debian-based hypervisor, not something you add to an existing system. This guide covers the requirements that actually matter, the install, and the repository step that every first-time installer hits within about five minutes of first boot.

Requirements

The official minimums and recommendations differ more than usual here, because the minimums are explicitly for evaluation only:

Two of these decide whether your install is usable:

Virtualization extensions. Without VT-x or AMD-V, Proxmox installs and runs, but you cannot start a KVM virtual machine. LXC containers still work, since they share the host kernel. If you only plan to run containers you can live without it; if you expect VMs, check first and enable it in the firmware.

ZFS RAM. The 1 GB-per-TB figure is the one people skip. Choosing ZFS on an 8 TB pool in a 8 GB machine leaves very little for guests. On small hosts, ext4 on LVM is a more comfortable default.

Check virtualization support from a running Linux system before you commit:

lscpu | grep -E 'Virtualization|vmx|svm'

Step 1: Download and verify the ISO

Download the Proxmox VE installer ISO from the official site, then verify it. This is not ceremony — a truncated download produces installer failures that look like hardware faults:

sha256sum proxmox-ve_*.iso

Compare the output against the checksum published on the download page. If they differ, download again.

Step 2: Write the installer to USB

Identify the target device carefully. dd will overwrite whatever you point it at, with no confirmation:

lsblk

sudo dd if=proxmox-ve_*.iso of=/dev/sdX bs=4M status=progress oflag=sync

Use the whole device (/dev/sdb), not a partition (/dev/sdb1). Confirm the size in lsblk matches the USB stick you think you are writing to before pressing enter.

Step 3: Install

Boot from the USB and work through the installer. The decisions worth pausing on:

• Target disk and filesystem. The installer erases the selected disk entirely. ZFS gives you snapshots and checksums at the RAM cost above; ext4 is lighter.
• Network. Set a static IP. A hypervisor whose address moves is a hypervisor you cannot reliably reach, and the management URL depends on it.
• Email. Used for system notifications. A real address you read is better than a placeholder.

When it finishes and reboots, remove the USB. The console prints the management URL, in the form https://<your-ip>:8006.

Step 4: Fix the repositories — the step everyone hits

Log in at https://<your-ip>:8006 (user root, realm Linux PAM). You will get a certificate warning, which is expected: the certificate is self-signed.

Now try an update. It fails, because a fresh install has the enterprise repository enabled, and that repository requires a paid subscription:

apt update

The fix is to disable the enterprise repository and enable the no-subscription one. On Proxmox VE 9 the format changed, and most guides still describe the old one.

Current versions use deb822 .sources files. To disable the enterprise repository, add Enabled: no to /etc/apt/sources.list.d/pve-enterprise.sources:

Types: deb
URIs: https://enterprise.proxmox.com/debian/pve
Suites: trixie
Components: pve-enterprise
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
Enabled: no

And the no-subscription repository, in /etc/apt/sources.list.d/pve-no-subscription.sources:

Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg

Match Suites: to your Debian base — trixie on Proxmox VE 9. On older installs using the legacy .list format, you comment out the line in pve-enterprise.list instead and add the no-subscription deb line. Both formats work; the .sources files are what a current install ships with.

Proxmox VE 8 and newer also expose this in the web UI under Datacenter → Node → Repositories, which is the safer route if you would rather not edit files.

Then:

apt update && apt dist-upgrade

To be clear about what this changes: no-subscription receives the same packages with less testing than the enterprise repository. It is the normal choice for a homelab and the wrong choice for production.

Verify

pveversion

This prints the running pve-manager version and kernel, for example pve-manager/9.1.7 (running kernel: 6.17.2-1-pve). If apt update is clean and pveversion reports a version, the install is healthy.

Common failures

Sources

• Proxmox VE Administration Guide (system requirements, installation)
• Proxmox VE docs — Package Repositories (enterprise and no-subscription repository definitions)
• Proxmox VE docs — Linux Container

Related reading