Before touching Proxmox VE, you need to master the Linux CLI, basic networking concepts, and an understanding of server hardware. In this episode you will also prepare the minimal hardware, burn the installer ISO, perform a bare-metal installation, and configure the repositories.

Welcome to the Learn Proxmox VE series! This series will take you from mastering Proxmox Virtual Environment — an open-source, Debian-based virtualization platform that combines KVM full virtualization, LXC containers, distributed storage, backup, and firewall in one system — from conceptual foundations all the way to production readiness. There are 21 episodes in total, organized into six phases.
But before touching the Proxmox installation, there are a few core skills and hardware requirements you must have. Why are these prerequisites important? Because Proxmox is a level-1 hypervisor that runs directly on top of the hardware. The decisions you make during installation — storage layout, network configuration, even the ISO version — will affect your entire infrastructure in the episodes that follow.
Episode 0 is your roadmap: we will make sure your core skills are in place, prepare the hardware and USB installer, perform a bare-metal installation of Proxmox VE 8.x, and then configure the repositories after installation. Once this episode is done, the whole series can be followed comfortably.
Proxmox is built on Debian Linux, so you need to be comfortable with the terminal: navigating directories, editing files with nano or vi, understanding permissions, and running commands with sudo or as root. Day-to-day operations like managing repositories, checking logs, and tweaking configuration all happen through the CLI.
grep -E "vmx|svm" /proc/cpuinfoThe output must show the vmx flag for Intel or the svm flag for AMD. If it's empty, hardware virtualization is probably not enabled in the BIOS, and Proxmox won't be able to run VMs properly.
Proxmox is a machine that is always connected to the network. You need to understand IP addresses, subnet masks, gateways, and DNS, because all of these are asked during the installation process. Also understand the concept of VLAN for network isolation, which we will use in phase 4, as well as how to read network configuration on Linux with ip a.
Proxmox manages CPU, RAM, and storage directly. You need to know about virtualization extensions (Intel VT-x and AMD-V), the importance of ECC RAM for servers running critical data, and the differences between storage types: HDD for cheap capacity, SSD for performance, and NVMe for the lowest latency.
To follow this series comfortably, prepare hardware with the following specifications:
You will also need a second PC or laptop to access the Proxmox web UI through a browser, or use SSH from another machine on the same network.
Download the latest Proxmox VE ISO from the official Proxmox website, then burn it to a USB drive of at least 4 GB. On Linux, the dd command is the most reliable way:
dd bs=4M if=proxmox-ve_8.2-1.iso of=/dev/sdX status=progress oflag=syncReplace /dev/sdX with your USB device — be careful, because dd will wipe the entire contents of the target drive. oflag=sync ensures the write buffer is flushed before the command finishes.
Plug in the USB installer, enter the BIOS, set the boot order to USB, then follow the installation wizard. Choose the first option, accept the EULA, and select the country, timezone, and keyboard layout. The most important part is selecting the target disk and the storage layout: for a single disk, the default ext4 or LVM-thin choice makes a lot of sense. In the networking section, fill in the hostname, IP address, netmask, gateway, and DNS according to your network.
The installation runs for a few minutes, then the system reboots. Remove the USB when prompted, and Proxmox will boot from the disk.
After booting, the terminal displays the management access address. Open a browser and navigate to that address:
https://<IP-PROXMOX>:8006Log in with user root and the password you set during installation. The browser will show a self-signed certificate warning — ignore it for now, because episode 15 will replace it with a valid certificate.
Proxmox enables the pve-enterprise repository by default, which requires a subscription. Since we are using the free version, this repository must be disabled so that apt update doesn't error out. Edit the repository configuration file:
nano /etc/apt/sources.list.d/pve-enterprise.listComment out the line containing enterprise.proxmox.com by adding a # at the start, then save.
Add the free pve-no-subscription repository so Proxmox receives updates from the public servers:
echo "deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription" >> /etc/apt/sources.listAfter that, run the system update and upgrade:
apt update && apt full-upgrade -yThis entire series assumes this free repository is active. The apt update command will be used over and over, so get used to it now.
Before moving on to episode 1, make sure the Proxmox services are running correctly:
pveversion
systemctl status pveproxypveversion shows the Proxmox version and the running kernel, while pveproxy is the service that serves the web UI on port 8006. If both are active, your environment is ready.
One important habit to adopt right now: always access Proxmox through the web UI at https://<IP>:8006 and confirm every operation via the Task Log. We will explore the web UI in more depth in episode 2.
In episode 0 you set the foundation for the whole series: verifying your Linux CLI, networking, and hardware knowledge, burning the installer ISO, performing a bare-metal Proxmox VE installation, and configuring the free repositories after installation.
The key takeaways:
vmx or svm.dd and set the boot order in the BIOS before installation.pve-no-subscription.https://<IP>:8006 with the root user.pveversion and systemctl status pveproxy.In the next episode, episode 1, we will cover the history, architecture, and why to choose Proxmox VE — from the platform's birth at Proxmox Server Solutions GmbH in 2008, the Debian + KVM + LXC foundation, to its comparison with VMware vSphere and Microsoft Hyper-V. Make sure your environment is ready, because the Learn Proxmox VE journey has only just begun!