Proxmox VE vs VMware ESXi: Complete Install Guide (Bare Metal, Step-by-Step)

This long-form guide covers two enterprise hypervisors side by side: Proxmox VE (open-source, KVM + LXC) and VMware ESXi (commercial, vSphere hypervisor). You will install both from bare metal, verify each web interface, create your first VM, and understand when to choose which platform.

Part A — Proxmox VE installation (bare metal)

A1. Requirements

• 64-bit CPU with VT-x/AMD-V enabled in BIOS
• 8 GB RAM minimum (16 GB+ for lab with multiple VMs)
• 32 GB+ boot disk (120 GB SSD recommended)
• Static IP for management interface
• Proxmox VE 9.x ISO from proxmox.com/downloads

A2. Create bootable USB

# On Linux workstation — flash ISO to USB
lsblk
sudo dd if=proxmox-ve_9.0-1.iso of=/dev/sdX bs=4M status=progress conv=fsync
# Or use Ventoy / Rufus / balenaEtcher on Windows

A3. Boot and start graphical installer

1. Insert USB, boot server, press F11/F12 for boot menu.
2. Select Install Proxmox VE (Graphical).
3. Accept EULA → select target disk (ext4 or ZFS).
4. Set country, timezone, keyboard.
5. Set root password and email for alerts.
6. Configure management network: hostname pve1.lab.local, IP 192.168.1.50/24, gateway, DNS.
7. Review summary → Install → reboot.

Installer console output (typical):

Starting Proxmox VE installer...
Formatting /dev/nvme0n1p2 ext4...
Installing base system packages...
Installing Proxmox VE packages (pve-manager, qemu, lxc)...
Configuring network vmbr0 on eno1...
Installation completed — rebooting.

A4. First login to Proxmox web UI

# From browser
https://192.168.1.50:8006
# Login: root / your-install-password
# Realm: Linux PAM standard authentication

# From SSH — verify version
ssh root@192.168.1.50
pveversion -v
systemctl status pveproxy pvedaemon pve-cluster

Expected pveversion output:

pve-manager/9.0.3/bc4f547a (running kernel: 6.8.12-1-pve)
qemu-server: 9.0.3
pve-qemu-kvm: 9.0.2-1

A5. Post-install Proxmox configuration

# Update repositories and upgrade
apt update && apt full-upgrade -y

# Disable enterprise repo if no subscription (lab only)
# Use pve-no-subscription repo per Proxmox wiki

# Download Ubuntu cloud-init template for CT/VM
pveam update
pveam available | grep ubuntu
pveam download local ubuntu-22.04-standard_22.04-1_amd64.tar.zst

# Check node status
pvesh get /nodes/pve1/status

A6. Create first VM in Proxmox

1. Datacenter → pve1 → Create VM.
2. General: VM ID 100, name ubuntu-web.
3. OS: ISO image (upload Ubuntu ISO to local storage first).
4. System: default BIOS, Q35 machine type.
5. Disks: 32 GB on local-lvm.
6. CPU: 2 cores, RAM: 2048 MB.
7. Network: vmbr0, virtio model.
8. Finish → Start VM → Open console.

# CLI create + start VM
qm create 100 --name ubuntu-web --memory 2048 --cores 2 \
  --net0 virtio,bridge=vmbr0 --scsi0 local-lvm:32
qm set 100 --cdrom local:iso/ubuntu-22.04.iso
qm start 100
qm list

Part B — VMware ESXi installation (bare metal)

B1. Requirements and licensing

• Server on VMware HCL (Hardware Compatibility List)
• ESXi 8.x ISO from Broadcom/VMware portal (free tier or vSphere license)
• 8 GB RAM minimum, 32 GB boot USB/SD or local disk
• Management IP on dedicated VLAN recommended

B2. Boot ESXi installer

1. Flash ESXi ISO to USB, boot server.
2. Select ESXi-8.x Standard Installer.
3. Enter (Continue) through welcome → Accept EULA.
4. Select install disk (local SSD — all data will be erased).
5. Select keyboard layout.
6. Set root password (complexity required).
7. Confirm install → Reboot.

ESXi installer log on screen (DCUI):

VMware ESXi 8.0.2 Installation
Reading installation image...
Creating VMFS datastore 'datastore1' on Local NVMe...
Installing hypervisor binaries...
Installation successful. Please reboot.

B3. Configure ESXi management network (DCUI)

1. After reboot, press F2 on Direct Console UI.
2. Login as root.
3. Configure Management Network → IPv4 → Static.
4. IP: 192.168.1.60, Mask: 255.255.255.0, Gateway: 192.168.1.1
5. DNS: 8.8.8.8, Hostname: esxi1.lab.local
6. Test management network → working.

# From SSH (after enabling SSH in DCUI → Troubleshooting)
ssh root@192.168.1.60
vmware -v
esxcli system version get
esxcli network ip interface ipv4 get

Expected output:

VMware ESXi 8.0.2 build-22380479
   Product: VMware ESXi
   Version: 8.0.2
   Build: Releasebuild-22380479
   Update: 2

B4. Access ESXi Host Client (web UI)

# Browser
https://192.168.1.60/ui
# Login: root / password
# Create datastore, upload ISO, create VM from GUI

B5. Create first VM on ESXi

1. Host Client → Virtual Machines → Create VM.
2. Name: ubuntu-web-esxi, Compatibility: ESXi 8.x.
3. Guest OS: Linux → Ubuntu 64-bit.
4. Datastore: datastore1, 32 GB thin disk.
5. 2 vCPU, 2 GB RAM, VMXNET3 network.
6. Mount Ubuntu ISO from datastore browser.
7. Power on → Open console → install OS.

# Useful ESXi CLI commands
esxcli vm process list
vim-cmd vmsvc/getallvms
esxcli storage filesystem list
esxcli system maintenanceMode set --enable true   # before major changes
esxcli system maintenanceMode set --enable false

Part C — Proxmox vs VMware: comparison

Part D — When to choose which

Choose Proxmox VE when you want open-source KVM, LXC containers, integrated backups, ZFS/Ceph, and no per-socket licensing. Ideal for homelab, hosting providers, and Linux-first teams.

Choose VMware ESXi when your organization already runs vSphere, needs official enterprise support, vMotion with vCenter, or compliance mandates for VMware-only stacks.

Part E — Side-by-side verification checklist

# === Proxmox (192.168.1.50) ===
pveversion
pvesm status
qm list
pct list
journalctl -u pveproxy --since today | tail -20

# === ESXi (192.168.1.60) ===
vmware -v
esxcli hardware platform get
esxcli vm process list
grep -i error /var/log/vmkernel.log | tail -10
grep -i error /var/log/hostd.log | tail -10

Part F — Common issues

Proxmox

• Cannot access :8006 — check systemctl status pveproxy, firewall, and certificate.
• No subscription nag — expected without license; use no-subscription repo for lab.
• VM won't start — enable VT-x in BIOS; check journalctl -u qmeventd.

VMware ESXi

• Installer doesn't see NIC — inject VIB driver or use supported HCL hardware.
• License warning — assign license in Host Client → Manage → Licensing.
• Datastore full — esxcli storage vmfs extent list and expand or add disk.

You now know how to install and verify both Proxmox VE and VMware ESXi from scratch. For production, add backup (PBS or vzdump / Veeam), monitoring, and cluster planning before migrating workloads.