Step 1: Verify Hardware Compatibility and System Requirements
Before beginning the installation, confirm your bare-metal server meets the core requirements. Proxmox VE (Virtual Environment) is a Debian-based hypervisor, so x86_64 (64-bit) architecture is mandatory. Intel VT-x or AMD-V CPU virtualization extensions must be enabled in the BIOS/UEFI. Minimum RAM is 2 GB, though 8 GB or more is recommended for production workloads. Storage should be a modern SSD or NVMe drive for the OS; a separate disk or RAID array for VM storage is highly advisable. Verify that your network interface card (NIC) is supported—most Intel, Realtek, and Broadcom adapters work out of the box. Disable Secure Boot in your motherboard firmware, as it can interfere with the Proxmox boot process and kernel modules. Also, ensure you have a dedicated IP address, subnet mask, gateway, and DNS server details if you plan to use a static IP configuration, which is standard for server deployments.
Step 2: Download the Proxmox VE ISO Image
Navigate to the official Proxmox website: https://www.proxmox.com/en/downloads. Select the “Proxmox VE” product. Download the latest stable ISO installer (e.g., proxmox-ve_8.0-1.iso). Verify the SHA256 checksum provided on the download page against your local file using a checksum utility (e.g., sha256sum on Linux or Get-FileHash on PowerShell). This ensures the image has not been tampered with. The ISO is roughly 1 GB and includes a complete Debian base system with the Proxmox kernel and management tools. Do not use the “Proxmox Backup Server” or “Proxmox Mail Gateway” ISOs—those are separate products.
Step 3: Prepare the Installation Media
Write the ISO to a bootable USB drive (at least 2 GB in size). On Windows, use Rufus (select “DD Image” mode for best results) or balenaEtcher. On Linux, use the dd command: sudo dd if=proxmox-ve_8.0-1.iso of=/dev/sdX bs=4M status=progress && sync (replace /dev/sdX with your USB device—be extremely careful not to target your system disk). Alternatively, mount the ISO via IPMI or iDRAC virtual media if you are remotely deploying to a server. Avoid writing the ISO using “ISO9660” mode; the “DD” mode preserves the hybrid boot structure, ensuring UEFI and legacy BIOS compatibility.
Step 4: Boot from the Installation Media
Insert the USB drive into the target server and power it on. Access the boot menu (typically F11, F12, or Esc during POST) and select the USB device. For UEFI systems, ensure you choose the UEFI-boot entry if available. The Proxmox bootloader will present a graphical menu with options: “Install Proxmox VE,” “Install Proxmox VE (Debug Mode),” and “Install Proxmox VE (Serial Console).” Select the first option. If the server lacks a graphical display or is headless, choose the serial console option and configure your serial port parameters accordingly.
Step 5: Configure the Installation Parameters
The installer will load the Debian environment. A welcome screen appears; click “Agree” to the End User License Agreement. Next, select the target disk for the Proxmox OS installation. You can choose to use an entire disk (which wipes all data) or set up advanced LVM or ZFS configurations. For most bare-metal deployments, ZFS (RAID0 or RAID1) is recommended for its data integrity, snapshots, and compression features. Select “ZFS (RAID-0)” for a single disk, or “ZFS (RAID-1)” if you have two identical disks for mirroring. LVM-thin is another strong option, offering efficient snapshot management. Be cautious: any existing data on the selected disk will be permanently erased.
Step 6: Set the Hostname, IP Address, and Network
You will be prompted to enter a fully qualified domain name (FQDN) for the server (e.g., pve01.example.com). This hostname is critical for clustering and certificate generation. Next, configure networking. For production, select “Static” IP configuration. Enter your planned IP address (e.g., 192.168.1.100), netmask in CIDR notation (e.g., /24 for 255.255.255.0), gateway (e.g., 192.168.1.1), and DNS server (e.g., 8.8.8.8). If using DHCP (not recommended for servers), the installer will assign a dynamic IP. After network setup, the installer will configure the localhosts file and generate SSH keys.
Step 7: Set the Root Password and Email
You must set a strong root password for the server. This password is used for SSH access and Proxmox web interface login. Ensure it is at least 12 characters with mixed case, numbers, and symbols. Then, enter an email address for system notifications (e.g., root alerts, backup reports). This email is used by the Proxmox mail subsystem (Postfix). You can change it later via the web interface or /etc/aliases.
Step 8: Allow the Installation to Complete
The installer will partition the disk, install the base Debian system, install the Proxmox kernel and tools, and configure the bootloader. This process typically takes 5 to 15 minutes depending on disk speed and hardware. During the installation, you may see a prompt regarding “Configure postfix.” If you have a mail relay, select “Internet Site” and enter your mail server details. Otherwise, select “Local only” for standalone operation. The installer will finalize by installing GRUB to the boot disk. Upon completion, click “Reboot.” Remove the USB installation media when prompted.
Step 9: Perform the First Boot and Initial Access
After reboot, the server will display a console login prompt. Log in with the username root and the password you set. Verify the network interface is up by checking IP address with ip a. If the IP is incorrect, edit /etc/network/interfaces and run ifreload -a. From any computer on the same network (or with routing access), open a web browser and go to https://:8006. Accept the self-signed SSL certificate warning (this is normal). You will be greeted by the Proxmox login screen.
Step 10: Apply Initial Post-Installation Configuration
Log in to the web GUI using root and the password. The first step is to update the package repository. Navigate to Datacenter > pve > Updates > Refresh. Alternatively, run apt update && apt dist-upgrade -y via SSH. Proxmox does not include the non-free or enterprise repositories by default. For a subscription-free setup, edit /etc/apt/sources.list to add the “no-subscription” repository: deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription. Remove or comment out the enterprise repo line. After updating, reboot if a new kernel was installed.
Step 11: Configure Storage and Networking
In the web interface, go to Datacenter > Storage > Add to configure directories for ISO images, VM templates, backups, and containers. If you have a separate storage disk or RAID array, add it as a ZFS pool or LVM volume. For ZFS, use zpool create command in the shell or use the GUI’s “ZFS” plugin. For networking, consider bridging additional physical NICs to the default vmbr0 bridge for VM connectivity. Add VLAN interfaces if required. Configure firewall rules under Datacenter > Firewall to allow essential ports (22, 8006, 5900-5999 for VNC, 111 for NFS). Finally, verify your time sync: ensure ntp or chrony is enabled and pointing to reliable NTP servers.
Step 12: Enable the Proxmox Enterprise Repository (Optional)
If you have a valid Proxmox subscription, enable the enterprise repository by running: pveceph install (for Ceph) or editing the apt sources files accordingly. The enterprise repo provides highly tested updates and security patches. Without a subscription, the “no-subscription” repo is fully functional for testing and development, but note that it is not intended for production use per Proxmox’s licensing policy, though many run it successfully.
Step 13: Secure Your Deployment
Change the default root password regularly. Create a separate non-root user with sudo privileges for daily management. Disable root SSH login by editing /etc/ssh/sshd_config (set PermitRootLogin prohibit-password if you use key-based authentication). Enable two-factor authentication for the web interface via TOTP (available under Datacenter > Permissions > Two-Factor Auth). Regularly check for updates via the GUI’s update manager. Set up automated backups using Proxmox’s built-in vzdump functionality, targeting a separate NFS or SMB share. For critical environments, configure a Proxmox cluster and enable high availability (HA) for VMs using the Datacenter > Cluster wizard.
Step 14: Perform a Post-Installation Validation
Test VM creation by uploading an ISO image (e.g., an Ubuntu Server LTS ISO) to the local storage you configured. Create a guest virtual machine with at least 1 CPU core, 1 GB RAM, and a 10 GB virtual disk. Start the VM and verify network connectivity via console. Test live migration if you have a second Proxmox node (requires cluster setup). Run pveversion -v to verify all packages are up to date. Monitor system logs with journalctl -f to catch any hardware errors or misconfigurations. Finally, review the Proxmox admin guide for advanced tuning, such as CPU pinning, hugepages, or PCI passthrough for GPU workloads.