How to Install Proxmox VE

Proxmox VE installs directly on a physical server from a bootable USB drive, then provides a browser-based interface for creating virtual machines and Linux containers. For most homelabs, the essential path is to verify hardware support, install the ISO to a dedicated disk, assign a static management address, and complete the first updates.

What Proxmox VE Is

Proxmox Virtual Environment, commonly called Proxmox VE or PVE, is an open-source virtualization platform built on Debian. It combines KVM for full virtual machines, LXC for lightweight Linux containers, software-defined networking, storage management, backups, clustering, and a web administration interface in one system.

Unlike an application installed on top of a normal desktop, Proxmox VE is typically the server’s operating system. Installing it erases the selected target disk, so move any files you need before beginning.

Prerequisites

• A 64-bit Intel or AMD computer with hardware virtualization enabled in UEFI or BIOS
• At least 4 GB of RAM for a small lab, with more memory for guest workloads and ZFS
• A dedicated SSD or hard drive for Proxmox VE and enough storage for virtual disks
• A wired Ethernet connection and access to the router or DHCP lease table
• A USB flash drive large enough for the installer image
• Another computer from which to download the ISO and open the management interface
• A planned static management address such as 192.168.1.x, plus the correct gateway and DNS settings

Download the current Proxmox VE ISO from the official project website. Verify its checksum against the published value, then write it to the USB drive with an imaging utility. This operation overwrites the USB drive; copying the ISO onto the drive as an ordinary file is not sufficient.

Install Proxmox VE

Connect the target server to wired networking, insert the installer USB, and boot from it using the system’s one-time boot menu. Choose the graphical installation option unless the hardware requires another installer mode, then accept the license terms.

Select the destination disk carefully. The options dialog lets you adjust the filesystem and disk layout. The default ext4 or XFS layout is straightforward for a single disk. ZFS adds checksumming, snapshots, and optional redundancy, but it needs suitable memory and benefits from direct access to the drives. ZFS redundancy is not a substitute for backups.

Set the country, time zone, and keyboard layout. Next, create a strong administrator password and provide an email address for system notifications. Store the password securely; the installer configures the administrative root account for initial access.

Choose the physical network interface that will carry management traffic. Enter a fully qualified host name using a name reserved for your own network, then configure an unused static address in your LAN’s subnet. Use a placeholder such as 192.168.1.x when documenting the setup, and enter your router’s actual gateway and a reachable DNS resolver during installation.

Review the summary, start the installation, and reboot when prompted. Remove the USB drive so the machine boots from its installed disk.

First-Boot Configuration

The local console displays the management URL after boot. From another computer on the same network, open https://192.168.1.x:8006. A browser warning is expected initially because Proxmox VE uses a self-signed certificate. Confirm that you reached the intended server before proceeding.

Sign in as root using the Linux PAM realm and the password created during setup. Verify the node’s DNS, time, storage, and network settings. Apply available package updates before deploying guests. If you do not have a paid subscription, configure the repository appropriate for non-subscription use according to the official documentation; do not disable authentication or add untrusted package sources merely to remove repository errors.

Upload an operating-system ISO to ISO-capable storage, or download an approved image through the interface. You can then create a VM or LXC container and assign CPU, memory, storage, and networking. Reserve enough resources for the Proxmox host itself.

Common Pitfalls

• Losing access after installation: A static address outside the LAN subnet, a duplicate address, or an incorrect bridge port can make the web interface unreachable. Confirm the subnet, gateway, and reserved address before installing.
• Installing onto the wrong disk: Disk model names can look similar, and the installer erases the selected device. Disconnect unnecessary drives or identify every disk by size and serial number first.
• Treating snapshots or RAID as backups: Neither protects against every deletion, corruption event, or site failure. Send scheduled backups to separate storage and test restores.

What’s Next

Once networking and updates are stable, create a small test guest, configure automated backups, and document recovery access. After that foundation is proven, explore VLANs, storage pools, monitoring, and clustering as your homelab grows.