Install Proxmox VE

Proxmox VE combines KVM virtualization and LXC containers with a web interface. On a HolyCloud dedicated server, installation usually replaces the existing system — plan backups and IPMI access.

Prerequisites

• 64-bit dedicated server with virtualization enabled (VT-x/AMD-V in BIOS via IPMI)
• Minimum 32 GB disk, 16 GB+ RAM recommended for several VMs
• IPMI/KVM access to mount ISO
• Public IP, gateway, and DNS noted
• Backup of all data

Download Proxmox VE ISO

Get the latest stable ISO from proxmox.com:

# from your workstation or a temporary server
wget https://enterprise.proxmox.com/iso/proxmox-ve_8.x-x.iso

Verify the checksum published on the site.

Installation via IPMI (KVM + virtual ISO)

1. Connect to server IPMI/BMC (see « Access IPMI / BMC » guide).
2. Virtual Media: mount Proxmox ISO.
3. Boot from virtual CD-ROM (F11/F12 at startup per brand).
4. Graphical wizard:

- Target disk: hardware RAID or mdadm (optional ZFS on expert install)

- Hostname: pve01.votredomaine.tld

- Static IP, netmask, gateway, DNS

- Strong root password

- Administrator email (alerts)

1. Reboot: remove virtual ISO.

First web access

Default interface:

https://IP_PUBLIQUE:8006/

Login: root + password set at install (realm pam).

Self-signed certificate: accept the exception or import Let's Encrypt later.

Post-install update

SSH login:

ssh root@IP_PUBLIQUE
pveversion -v
apt update && apt full-upgrade -y

Enterprise subscription (optional): pve-enterprise repo; without subscription, use documented no-subscription repos (at your own risk for production).

Create a first VM (summary)

1. Upload an ISO to local → ISO Images (or shared storage).
2. Create VM: ID, name, ISO, disk, CPU, RAM, vmbr0 network.
3. Start the VM and open the console.

Default bridge vmbr0 tied to the main physical interface.

Storage and backups

pvesm status

Configure vzdump for scheduled snapshots to NFS, S3-compatible, or second disk.

Minimum security

• Change SSH port or limit by firewall if exposed
• Create non-root admin user for API if needed
• Update regularly (apt upgrade)
• Isolate port 8006 (VPN or IP allowlist)

# example: UFW rule (adapt)
ufw allow from VOTRE_IP to any port 8006 proto tcp
ufw allow 22/tcp
ufw enable

Troubleshooting

| Problem | Hint |

|----------|-------|

| No VT-x | Enable in BIOS via IPMI |

| VM network no Internet | Check gateway on vmbr0, switch MAC |

| Cluster | 3 nodes recommended — out of scope for simple dedicated |

Need help?

HolyCloud can confirm VT-d/IOMMU compatibility for PCI passthrough on your hardware reference.