Cutter 16
$176.70 total · Save 5%
- vCPU
- 6 × dedicated
- RAM
- 16 GB
- Storage
- 320 GB NVMe SSD
- Transfer
- 15 TB
- IPv4 / IPv6
- 1 / /64 routed
Operating system
Proxmox VE turns one instance into a hypervisor running its own KVM guests and LXC containers, with a web UI and built-in backup. It works here because we enable nested virtualisation — many providers do not, which is why Proxmox fails on their platforms.
Proxmox VE is a hypervisor you run on a virtual server. Because OnionVPS uses true KVM virtualisation, the instance presents full hardware virtualisation to Proxmox, so it can host its own KVM guests and LXC containers. A container-based VPS shares the host kernel and cannot provide the nested virtualisation Proxmox needs. Know that Proxmox boots with a 4096 MB RAM minimum, but 16 GB is comfortable, and the hypervisor consumes a good chunk of that before any guest starts. Many providers disable nested virtualisation, so this works here and fails elsewhere.
People run Proxmox VE here to consolidate a home lab onto one IP, spin up nested test environments, and run reseller platforms with separate VMs or containers per tenant. The built-in backup and replication help, as does the web UI, but the heavy baseline resource use means you trade performance headroom for consolidation.
Plan for the operating system to cost you RAM before any guest runs. With a 4096 MB minimum, boot barely fits and leaves little for workloads. At 16 GB, you have roughly 12 GB for guests. Buy extra disk to accommodate ZFS and backups; start smaller than you think and scale up with extra RAM and NVMe.
$176.70 total · Save 5%
$336.30 total · Save 5%
$262.20 total · Save 5%
Proxmox VE boots in 4096 MB and is comfortable with 16 GB. Add whatever your application needs on top of that — the operating system baseline is a floor, not a budget.
Yes, on true KVM virtualisation, which is what every OnionVPS instance runs. It is available as a ready template and can also be installed from your own ISO.
Tied to the Debian base
Nested KVM guests run under Proxmox inside your virtual server, so there is an extra virtualisation layer compared to direct KVM. That adds overhead, but for home-lab consolidation or testing, the convenience of a web-managed hypervisor outweighs the cost. Use LXC containers for lower-overhead workloads where possible.
Yes, if your existing Proxmox host supports live migration or you can create a backup that includes your VM images. OnionVPS provides full root access and nested virtualisation, so the hypervisor sees the same environment it expects. Just upload your backup or use the Proxmox migration tool with suitable network planning.