How to Install Proxmox on Bare Metal
A Step-by-Step Guide
Installing Proxmox Virtual Environment (Proxmox VE) directly on server hardware unlocks top-tier performance, live management via the web UI, and powerful features like ZFS, clustering, and backups. Follow this beginner-friendly walkthrough to go from ISO to first login—fast.
Why Choose Proxmox VE?
- All-in-one: KVM for full VMs + LXC containers in one UI.
- Open-source with optional enterprise repo; huge community.
- Web-based management: Create, snapshot, and back up VMs from the browser.
- ZFS support: Software RAID, checksums, snapshots, and replication.
- Scales up: Cluster multiple nodes and enable High Availability.
Requirements (Hardware & Software)
Minimum Hardware
- 64-bit CPU (Intel VT-x/AMD-V recommended)
- RAM: 2 GB minimum (8 GB+ recommended for multiple VMs)
- Storage: 32 GB+ (SSD/NVMe recommended)
- Network: 1× Ethernet (2+ if using VLANs/bonding)
Download
Get the latest Proxmox VE ISO from the official site, then create a bootable USB with
Rufus (Windows), BalenaEtcher (cross-platform), or dd
(Linux/macOS).
Prep: BIOS/UEFI & Bootable USB
1) Enable Virtualization in BIOS/UEFI
- Turn on Intel VT-x/VT-d or AMD-V/IOMMU.
- Set Boot Mode to UEFI (preferred) and enable AHCI/NVMe for storage.
- Disable fast boot/CSM if the installer doesn’t appear.
2) Create a Bootable USB
Linux/macOS example (replace /dev/sdX
with your USB device):
sudo dd if=proxmox-ve.iso of=/dev/sdX bs=4M status=progress conv=fsync
Install Proxmox VE (Wizard)
- Boot from USB and choose Install Proxmox VE.
- License + Target Disk: Accept, then pick the disk (or choose ZFS, see below).
- Locale: Set country, time zone, keyboard.
- Admin: Create the
root
password and enter an email for alerts. - Network: Assign a static IP, gateway, and DNS.
- Install → Wait for completion → Reboot and remove USB.
https://your-ip:8006
) on the console.
First Login & Post-Install Steps
- Open a browser and go to:
https://<your-server-ip>:8006
(You may need to proceed past a self-signed certificate warning.) - Login as
root
with the password you set. - Update the node:
apt update && apt full-upgrade -y
- (Optional) Switch to the no-subscription repo if you don’t have an enterprise subscription:
# In the web UI: Node > Repositories > Disable "Enterprise" and enable "No-Subscription" # Or via CLI (varies by version); use the UI if you're new.
- Add storage (local-LVM, ZFS pool, NFS, or SMB) and start creating VMs/containers.
Networking Tips (Static IP, VLANs)
- Use a static management IP on your Proxmox host.
- Create a Linux Bridge (e.g.,
vmbr0
) to attach VM NICs to your LAN or trunk. - For VLANs, tag the bridge port on your switch and set VLAN IDs on VM NICs.
- Bond multiple NICs (LACP) for redundancy/throughput if your switch supports it.
Storage Choices: ext4 vs ZFS
ext4 (LVM-thin)
- Pros: Simple, fast, low RAM usage.
- Best for: Single-disk installs, small labs.
ZFS
- Pros: RAID (mirror/RAIDZ), checksums, snapshots, send/receive replication.
- Considerations: Likes RAM (~1 GB per TB of raw storage is a common rule-of-thumb).
- Best for: Data integrity, multi-disk pools, easy snapshots and rollback.
Troubleshooting
- Installer can’t find disks: Set SATA/NVMe mode to AHCI; update BIOS.
- No network after install: Check bridge config (
vmbr0
) and switch port VLANs. - Can’t reach web UI: Verify IP/gateway/DNS; ensure nothing blocks port
8006
. - Package repository errors: Confirm that only one Proxmox repo is enabled and it matches your Proxmox/Debian version.
FAQ
Is Proxmox free to use?
Yes. Core features are free and open-source. A paid subscription provides enterprise repository access and support.
Can I install on a USB or SD card?
It’s possible but not recommended for production. Use SSD/NVMe for reliability and speed.
Do I need ECC RAM?
No, but it’s recommended for ZFS to reduce the risk of undetected memory errors.
Can I add a GPU later for passthrough?
Yes. Enable IOMMU in BIOS, configure kernel params, and map the device to a VM; results vary by hardware.
Conclusion
That’s it! Your Proxmox VE host is live and ready for VMs and containers. Next, consider adding backups, experimenting with ZFS snapshots, and—when you’re ready—joining multiple nodes into a cluster.