02
Verify compatibility before installation starts
Proxmox requires Intel VT or AMD-V for x86 KVM. Size memory for the host plus guests, with extra headroom for ZFS or Ceph. Passthrough also depends on firmware, motherboard, and device support; catalogue specifications alone do not prove compatibility.
Selecting the image does not confirm installation. Accepted or Queued only records the workflow; custom ISO mounts are also reviewed. Back up elsewhere because the installer removes data from selected target drives.
Verify compatibility before installation starts| Decision | Verify before relying on it |
|---|
| Image | Exact Proxmox VE release, architecture, boot mode, and checksum |
|---|
| CPU | Virtualization flags and any passthrough requirements |
|---|
| Memory | Host overhead, guest allocation, storage services, and recovery headroom |
|---|
| Disks | Installer targets, controller mode, redundancy, and backup destination |
|---|
03
Choose the storage model before the installer writes disks
Choose LVM, ZFS, or another storage type before installation. Proxmox distinguishes hardware RAID from non-RAID disks for ZFS or Ceph and warns against placing either behind hardware RAID. Confirm controller mode and target disks.
Snapshots, mirrors, and replication do not replace off-host backup. Configure a separate target and test restoration. Tungsto backup or extra-disk options require separate confirmation; selecting Proxmox does not create them.
04
Plan management and guest networking before cutover
Proxmox uses Linux bridges such as vmbr0 as software switches. This does not define Tungsto routing. Obtain addresses, prefixes, gateway, and the permitted guest topology before configuring bridges, NAT, VLANs, or extra addresses.
Restrict management access and arrange recovery before remote network changes. KVM requests return Queued, not an immediate console or progress view. Preserve working settings and verify IPv4 and IPv6 after changes.
05
Operate Proxmox as a self-managed platform
You manage updates, authentication, certificates, firewalls, guests, licenses, monitoring, backups, and recovery. Proxmox VE is open source; its enterprise repository and vendor support need a separate Proxmox subscription, not included unless stated.
One host is not high availability. Clustering, quorum, storage, interconnects, and failure testing need additional systems and design. Tungsto does not promise managed HA, Ceph, or cross-region private networking through the OS image.
Direct answers
Questions before you order
Is Proxmox VE installed as soon as I select it?
No. The selection records the requested image. Accepted, Provisioning, or Queued does not prove installation or delivery. Wait for explicit completion and verify the installed release and access.
Can I use my own Proxmox ISO?
You can request a public HTTPS ISO, but the mount is queued for operator review. Verify publisher, checksum, architecture, boot mode, drivers, and target disks first.
Is a Proxmox subscription included?
Not unless the order explicitly says so. Proxmox VE is open source, but its enterprise repository and vendor support are separate subscription services.
Does one Proxmox server provide high availability?
No. A single host remains one failure domain. HA requires multiple nodes, quorum, suitable networking and storage, independent backups, and tested failure procedures.