Virtualization

Proxmox VE Beginner Guide on Dedicated Hardware

Beginner-friendly Proxmox VE overview: ISO install, first VM, networking bridges, storage, and why nested Proxmox on tiny VPS is usually the wrong lab.

By Alex Rivera · Infrastructure EngineerPublished 20 November 2025Updated 8 April 202610 min read

Author

Alex Rivera

Infrastructure Engineer

Alex designs and hardens EU VPS fleets in Frankfurt and Amsterdam. He spends most days on Docker, KVM networking, NVMe layouts, and keeping Ubuntu 24.04 boxes boringly reliable for production workloads.

What Proxmox is for

Proxmox VE is a Debian-based hypervisor platform with KVM VMs, LXC containers, clustering, and a polished web UI. It is how many EU operators run private clouds on dedicated boxes.

OrbitHost dedicated fleets are the realistic place to put Proxmox. A nested experiment on a Nano VPS teaches the UI but not real storage/network behavior.

Install from ISO

Download the official Proxmox VE ISO, write it to USB, and install on bare metal. Choose your management IP carefully — you will reach the UI at `https://IP:8006`.

During install, pick a hostname/FQDN you control if you later want proper certificates.

# after install, from a workstation:
# browse to https://YOUR_PROXMOX_IP:8006
# default realm: PAM / Linux PAM standard authentication
# upload ISOs under local storage → ISO Images

First network mental model

`vmbr0` is typically a Linux bridge tied to your physical NIC. VMs attach virtual NICs to that bridge to appear on the LAN or WAN as configured.

On a colocated dedicated server with one public IP, you often use routed or bridged setups depending on provider networking — read the dedicated network docs before bridging wildly.

Create your first Ubuntu VM

Upload an Ubuntu 24.04 cloud or live server ISO. Create a VM with virtio SCSI, virtio NIC, and enough CPU/RAM for the guest role. Start the VM and finish the guest OS install from the console.

# example qm commands on Proxmox shell (IDs vary)
qm create 100 --name ubuntu-app --memory 4096 --cores 2 --net0 virtio,bridge=vmbr0
qm set 100 --scsi0 local-lvm:32 --scsihw virtio-scsi-pci
qm set 100 --cdrom local:iso/ubuntu-24.04-live-server-amd64.iso
qm start 100

Storage basics

local-lvm is common on single-disk installs. For labs, keep ISOs/templates on `local` and VM disks on LVM-thin or ZFS. Snapshot before risky upgrades inside important VMs.

Separate ISO storage from VM disks mentally
Do not treat snapshots as offsite backups
Monitor disk wear on consumer NVMe in labs
Document VMID → role mapping

Firewall and updates

Restrict port 8006. Keep Proxmox updated with `apt` on the host. Guest updates are separate — patch hypervisors and guests on different schedules if you need uptime.

apt update && apt full-upgrade -y
pveversion -v
# enable firewall at datacenter/host/vm levels thoughtfully

How this relates to OrbitHost VPS

If you only need one Ubuntu guest for Docker/FiveM, buy a KVM VPS and skip the hypervisor layer. Proxmox pays off when you run many VMs or teach virtualization.

See `/dedicated` when you are ready for a real host, and `/vps-for-proxmox` only when you understand nested virt limits.

Related products

FAQ

Can I install Proxmox on a cheap VPS?

Only if nested virtualization is enabled and you accept poor performance. Most learning and homelab-style hypervisor work belongs on dedicated hardware.