{"id":25156,"date":"2026-11-01T09:13:43","date_gmt":"2026-11-01T09:13:43","guid":{"rendered":"https:\/\/atalnetworks.com\/?p=25156"},"modified":"2026-11-01T09:13:43","modified_gmt":"2026-11-01T09:13:43","slug":"proxmox-bare-metal-setup-guide","status":"publish","type":"post","link":"https:\/\/atalnetworks.com\/de\/proxmox-bare-metal-setup-guide\/","title":{"rendered":"Running Proxmox VE on Bare Metal: Complete Setup Guide"},"content":{"rendered":"

Running Proxmox VE on bare metal lets you use a physical server to host virtual machines and Linux containers. You install Proxmox directly on the hardware, then manage compute, storage, networking, and backups through its web interface.<\/span><\/p>\n

A successful installation involves more than reaching the login screen. The host needs reliable management access, suitable storage, working guest networks, and backups that you can restore.<\/span><\/p>\n

This guide covers a single x86-64 server, from installation planning to your first working guest and restore test. It uses the Proxmox VE 9 release family as its reference. Check the installed version before applying version-specific instructions.<\/span><\/p>\n

What Does Proxmox on Bare Metal Mean?<\/b><\/h2>\n

A bare-metal installation places Proxmox VE directly on a physical server. The installer supplies the host operating system and virtualization software.<\/span><\/p>\n

You can then create two main types of guests:<\/span><\/p>\n\n\n\n\n\n
Guest type<\/b><\/td>\nHow it works<\/b><\/td>\nCommon use<\/b><\/td>\n<\/tr>\n
Virtual machine<\/span><\/td>\nRuns its own operating system and kernel<\/span><\/td>\nWindows servers, Linux servers, separate application environments<\/span><\/td>\n<\/tr>\n
Linux container<\/span><\/td>\nShares the host kernel while keeping its own user environment<\/span><\/td>\nSupported Linux services with lower resource overhead<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The physical host supplies the resources. Every guest uses some of its CPU time, memory, storage capacity, and network bandwidth.<\/span><\/p>\n

Keep the host focused on virtualization and management. Place application workloads inside guests so that application changes are easier to control and recover.<\/span><\/p>\n

Before You Start: Check Hardware and Recovery Access<\/b><\/h2>\n

Proxmox installation erases the selected target disks. Copy any required data elsewhere and confirm which drives the installer will use.<\/span><\/p>\n

For a remote dedicated server, open the provider\u2019s console before changing the operating system or network. A working IPMI, iDRAC, iLO, or equivalent console gives you a recovery path when normal network access fails.<\/span><\/p>\n

Plan Resources Around Your Guests<\/b><\/h3>\n

Installation requirements are only a starting point. Size the server for the workloads it will run.<\/span><\/p>\n\n\n\n\n\n\n\n\n\n
Component<\/b><\/td>\nWhat to check<\/b><\/td>\n<\/tr>\n
CPU<\/span><\/td>\nSupported x86-64 processor with Intel VT-x or AMD-V enabled<\/span><\/td>\n<\/tr>\n
Memory<\/span><\/td>\nCapacity for the host, storage services, and active guests<\/span><\/td>\n<\/tr>\n
Lagerung<\/span><\/td>\nUsable capacity, redundancy, write endurance, and workload performance<\/span><\/td>\n<\/tr>\n
Network<\/span><\/td>\nSupported adapters, assigned addresses, VLANs, and provider restrictions<\/span><\/td>\n<\/tr>\n
Console<\/span><\/td>\nRemote keyboard, display, power control, and installation-media access<\/span><\/td>\n<\/tr>\n
Backup destination<\/span><\/td>\nStorage outside the physical host<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Do not allocate all physical memory to guests. The host and storage services also need memory.<\/span><\/p>\n

For example, a server with 64 GB of RAM cannot safely be planned as eight guests each requiring a full 8 GB at all times. That leaves no room for host services or changes in workload demand.<\/span><\/p>\n

CPU allocation also needs judgment. Assigning more virtual CPUs does not create more physical processing capacity.<\/span><\/p>\n

Record Your Network Details<\/b><\/h3>\n

Collect these values before booting the installer:<\/span><\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n
Setting<\/b><\/td>\nInformation required<\/b><\/td>\n<\/tr>\n
Hostname<\/span><\/td>\nA stable name such as <\/span>pve01.example.com<\/span><\/td>\n<\/tr>\n
Management IP<\/span><\/td>\nAssigned address and prefix length<\/span><\/td>\n<\/tr>\n
Gateway<\/span><\/td>\nExact gateway supplied by the network administrator or provider<\/span><\/td>\n<\/tr>\n
DNS<\/span><\/td>\nResolver addresses<\/span><\/td>\n<\/tr>\n
Physical interface<\/span><\/td>\nThe adapter connected to the intended network<\/span><\/td>\n<\/tr>\n
VLAN<\/span><\/td>\nRequired tag, if applicable<\/span><\/td>\n<\/tr>\n
Guest addresses<\/span><\/td>\nPublic addresses, routed subnet, or private addressing plan<\/span><\/td>\n<\/tr>\n
MAC policy<\/span><\/td>\nWhether guest MAC addresses require approval<\/span><\/td>\n<\/tr>\n
Recovery access<\/span><\/td>\nConsole and rescue-system instructions<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

A provider may route addresses differently from a home or office network. Never assume that a public address can be attached directly to a VM.<\/span><\/p>\n

Choose Your Storage Layout<\/b><\/h2>\n

Choose storage before installation because changing the root layout later can require migration or reinstallation.<\/span><\/p>\n

ZFS or LVM-Thin?<\/b><\/h3>\n

ZFS and LVM-thin serve different storage designs.<\/span><\/p>\n\n\n\n\n\n\n
Choice<\/b><\/td>\nSuitable situation<\/b><\/td>\nPlanning requirement<\/b><\/td>\n<\/tr>\n
ZFS mirror<\/span><\/td>\nTwo or more suitable disks with direct disk access<\/span><\/td>\nMemory budget, disk health monitoring, usable capacity<\/span><\/td>\n<\/tr>\n
LVM-thin<\/span><\/td>\nThin-provisioned guest storage on a suitable underlying disk arrangement<\/span><\/td>\nPool capacity and metadata monitoring<\/span><\/td>\n<\/tr>\n
Separate guest storage<\/span><\/td>\nWorkloads need capacity or performance beyond the boot disks<\/span><\/td>\nAdditional devices and a clear storage plan<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The installer can create different storage arrangements depending on the selected filesystem. Check the resulting storage configuration instead of assuming every installation contains <\/span>local-lvm<\/span>.<\/span><\/p>\n

With ZFS, allow the software to manage the individual disks. Proxmox documentation cautions against placing ZFS over a hardware RAID controller with its own cache management. An appropriate HBA or supported direct-disk arrangement is the better starting point.<\/span><\/p>\n

Redundancy Is Different From Backup<\/b><\/h3>\n

A mirror can help keep data available after a disk failure. It does not protect against every form of data loss.<\/span><\/p>\n\n\n\n\n\n\n
Protection<\/b><\/td>\nHelps with<\/b><\/td>\nDoes not replace<\/b><\/td>\n<\/tr>\n
Disk mirror<\/span><\/td>\nFailure of a disk within the mirror\u2019s fault tolerance<\/span><\/td>\nOff-host backup<\/span><\/td>\n<\/tr>\n
Snapshot<\/span><\/td>\nReturning supported storage to an earlier state<\/span><\/td>\nIndependent recovery copy<\/span><\/td>\n<\/tr>\n
Backup<\/span><\/td>\nRestoring retained data and guest configuration<\/span><\/td>\nApplication recovery testing<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Plan all three according to the workload. Keep enough free space for normal operation, snapshots, backups, and growth.<\/span><\/p>\n

Step 1: Download and Check the Installation Image<\/b><\/h2>\n

Download the installation image from the official Proxmox website. Select the image for the hardware you will use.<\/span><\/p>\n

The official download page listed Proxmox VE 9.2-1 during research on November 1, 2026. Use the current supported release appropriate to your environment and record the version you install.\u00a0<\/span><\/p>\n

Check the downloaded file against the published SHA-256 checksum.<\/span><\/p>\n

On Linux:<\/span><\/p>\n

sha256sum \/path\/to\/proxmox-ve.iso<\/span><\/p>\n

On Windows PowerShell:<\/span><\/p>\n

Get-FileHash .\\proxmox-ve.iso -Algorithm SHA256<\/span><\/p>\n

Compare the complete result with the official value.<\/span><\/p>\n

For a local server, write the image to a USB drive using an image-writing tool. Confirm the destination device because writing the image replaces its existing contents.<\/span><\/p>\n

For a remote server, mount the ISO through virtual media or the provider\u2019s supported installation system.<\/span><\/p>\n

Step 2: Boot and Install Proxmox VE<\/b><\/h2>\n

Restart the server and select the installation media from the boot menu.<\/span><\/p>\n

Use the graphical installer when it works correctly. The terminal installer provides another route when graphical display support causes problems.<\/span><\/p>\n

The official documentation recommends installation from the supplied ISO. Installation over an existing Debian system is an advanced option that requires separate storage, package, and network planning.\u00a0<\/span><\/p>\n

Select the Target Disks<\/b><\/h3>\n

Check disk capacity and identity carefully.<\/span><\/p>\n

If you planned a ZFS mirror, select the intended disks and mirror arrangement. If you selected another storage design, confirm that it matches your plan.<\/span><\/p>\n

Do not proceed until you know which disks will be formatted.<\/span><\/p>\n

Set Location and Administrator Details<\/b><\/h3>\n

Enter the location, time zone, and keyboard settings.<\/span><\/p>\n

Set a strong administrator password and an email address monitored by the operations team. Notification delivery still needs to be checked after installation.<\/span><\/p>\n

Configure the Management Network<\/b><\/h3>\n

Enter the hostname, management address, prefix, gateway, and DNS server.<\/span><\/p>\n

Use the interface connected to the correct network. On a server with several adapters, interface names alone may not make the cabling obvious. Check the provider\u2019s port information or console tools.<\/span><\/p>\n

Review the final installation screen. Confirm both storage and network settings before starting.<\/span><\/p>\n

When installation finishes, disconnect the ISO or USB media and boot from the installed system.<\/span><\/p>\n

Step 3: Check First Login and Host Health<\/b><\/h2>\n

From an approved management network, open:<\/span><\/p>\n

https:\/\/YOUR_MANAGEMENT_IP:8006<\/span><\/p>\n

For the initial login, select the Linux PAM authentication option and use the root credentials created during installation.<\/span><\/p>\n

A new installation normally presents a certificate that your browser does not already trust. Confirm that you are connecting to the intended server through a trusted path before accepting it. Configure an appropriate trusted certificate for routine administration.<\/span><\/p>\n

Open the host shell and inspect the system:<\/span><\/p>\n

pveversion -v<\/span><\/p>\n

hostname -f<\/span><\/p>\n

ip -br addr<\/span><\/p>\n

ip route<\/span><\/p>\n

timedatectl<\/span><\/p>\n

pvesm status<\/span><\/p>\n

Check that:<\/span><\/p>\n