Multi-node Kubernetes labs
Run a 3-node k3s cluster inside one VPS, control plane plus two workers, each as a nested VM. Practice failover, upgrades, and operator patterns without paying for three machines.
Nested VPS Hosting
VMs inside VMs.
Yes, really.
/dev/kvm exposed inside the guest. KVM-on-KVM, Hyper-V, VirtualBox, Docker-in-Docker, all native.
The independent cloud for builders, since 2008. Nested in 60 seconds.
Starting at $2.48/mo · 50% off · No credit card required
~ ssh root@vps-lon-001
kvm enabled
root@vps-lon-001:~# ls -l /dev/kvm
crw-rw---- 1 root kvm 10, 232 /dev/kvm
root@vps-lon-001:~# grep -c -E 'vmx|svm' /proc/cpuinfo
8
root@vps-lon-001:~# virt-host-validate qemu | head -3
QEMU: Checking for hardware virtualization : PASS
QEMU: Checking if device /dev/kvm exists : PASS
QEMU: Checking for cgroup 'cpu' controller : PASS
root@vps-lon-001:~# _
Nested VPS at a glance
Cloudzy exposes /dev/kvm inside every VPS guest, so you can run KVM-on-KVM, Hyper-V, VirtualBox, or Docker-in-Docker natively. Plans run from $2.48 per month across 12 regions, with sizes from 512 MB to 64 GB DDR5, all on NVMe storage and 40 Gbps uplinks. Servers provision in 60 seconds on AMD EPYC. Cloudzy has operated independently since 2008 and is rated 4.6 / 5 by 708+ reviewers on Trustpilot.
- Starting price
- $2.48 / month
- Provisioning
- 60 seconds
- Hypervisor
- KVM (nested)
- Inner OS
- Any KVM/HV guest
- Money-back
- 14 days
- Founded
- 2008
Why builders pick Cloudzy
A tech-savvy favorite.
The four things buyers actually compare us on, done right.
Nested KVM included
/dev/kvm is exposed in the guest from minute one. Run inner VMs without paid add-ons, special plans, or support tickets.
Risk-free trial
14-day money-back guarantee on every plan. No questions asked. No setup fees. Cancel anytime from the dashboard.
99.95% uptime SLA
Automated monitoring across 12 regions. Last-30-day SLA tracked publicly at status.cloudzy.com, no hiding.
Human support, fast
Live chat replies typically under 5 minutes. Engineers, not script-readers. Median resolution under 1 hour.
What runs nested
Hypervisors all the way down.
No tickets required.
Hardware virtualization passthrough is on by default, no support ticket, no plan upgrade, no extra fee. apt install qemu-kvm libvirt-daemon-system and you're ready. Inner VMs see real virt extensions, not emulation.
vmx / svm flags exposed on every plan
KVM-on-KVM
/dev/kvm exposed
Hyper-V
On Windows VPS
VirtualBox
Headless or GUI
Docker-in-Docker
Privileged DinD
k3s · kind
Inner k8s cluster
QEMU
Any guest arch
Vagrant
libvirt provider
Proxmox-lite
Test installs only
Use cases
What people build
with nested virt.
Malware sandbox & security lab
Detonate samples inside an inner VM, snapshot before, roll back after. Strong isolation from the outer VPS, separate kernel, separate network namespace, separate user-space.
CI runners with privileged Docker
GitLab CI, Drone, Jenkins, Buildkite, most CI systems want privileged container builds. Nested KVM lets you run those runners inside a VPS without pinning the workload to a bare-metal host.
Cross-architecture builds
Use QEMU + nested KVM to emulate ARM, RISC-V, or POWER guests on x86 hardware. Build, test, and ship multi-arch containers from a single Cloudzy VPS.
Training and workshops
Each student gets their own inner VM, with full root and full networking, sharing one outer VPS. Reset between sessions with a snapshot rollback. Cheaper than handing out 20 VPSs.
Test new distros & kernels
Try a new kernel, init system, or distribution without rebuilding the outer VPS. Nested VMs are throwaway by design, fail safe, snapshot, retry.
60s
Provisioning
40 Gbps
Uplink
NVMe-only
Storage
12
Regions
99.95%
Uptime SLA
14 days
Money-back
Global network
12 regions. Four continents.
One click away.
Drop your nested VPS as close to your users as physics allows. Median P50 latency under 10 ms in North America and Europe.
us-utah-1us-dal-1us-lax-1us-nyc-1us-mia-1eu-ams-1eu-lon-1eu-fra-1eu-zrh-1me-dxb-1ap-sgp-1ap-tyo-1
Pricing
Pay for what you use. That's it.
Hourly, monthly, or yearly. No egress fees. No commitments. Currently 50% off all plans.
1 GB DDR5
Light nesting · 1 inner VM
$3.48 /mo
$6.95/mo −50%
Deploy now
14-day money-back
- 1 vCPU @ EPYC
- 25 GB NVMe
- 1 TB · 40 Gbps
- Nested KVM enabled
- Dedicated IPv4 + IPv6
2 GB DDR5
2-3 inner VMs · Lab work
$7.475 /mo
$14.95/mo −50%
Deploy now
14-day money-back
- 1 vCPU @ EPYC
- 60 GB NVMe
- 3 TB · 40 Gbps
- Nested KVM enabled
- Dedicated IPv4 + IPv6
Most popular
4 GB DDR5
k3s clusters · CI runners
$14.47 /mo
$28.95/mo −50%
Deploy now
14-day money-back
- 2 vCPU @ EPYC
- 120 GB NVMe
- 5 TB · 40 Gbps
- Nested KVM enabled
- Dedicated IPv4 + IPv6
8 GB DDR5
Multi-VM labs · Training
$26.475 /mo
$52.95/mo −50%
Deploy now
14-day money-back
- 4 vCPU @ EPYC
- 240 GB NVMe
- 7 TB · 40 Gbps
- Nested KVM enabled
- Dedicated IPv4 + IPv6
FAQ. Nested VPS
Common questions, straight answers.
What is a nested VPS?
A nested VPS is a virtual server with hardware virtualization passed through to the guest OS, so you can run another hypervisor inside it. On Cloudzy, that means KVM-on-KVM, Hyper-V, VirtualBox, or Docker-in-Docker all run cleanly inside the VPS itself. Useful for labs, training, security research, CI runners, and anything that wants its own kernel.
How do I confirm nested virtualization is enabled?
On Linux: cat /proc/cpuinfo | grep -E 'vmx|svm' should show one of those flags, and ls /dev/kvm should exist. From there you can apt install qemu-kvm libvirt-daemon-system and start defining inner VMs. On Windows Server, run Get-VMHost from PowerShell to confirm Hyper-V can attach.
Is there a performance penalty for nested VMs?
Some, yes. Nested virtualization adds a layer of indirection, so the inner VM runs at roughly 80-95% of bare KVM speed depending on the workload, disk-heavy and IPC-heavy work takes the biggest hit. For most lab, dev, and CI use cases the difference is invisible.
Can I run a Kubernetes cluster inside one VPS?
Yes, and it's a popular setup. k3s, microk8s, and kind all run cleanly inside a Cloudzy VPS. For a multi-node cluster pick the 4 GB or 8 GB plan so you have headroom for the kubelet, etcd, and a couple of workloads. For production k8s, deploy multiple VPSs and join them, nesting one cluster inside one VPS is fine for dev.
Does Docker-in-Docker work?
Yes. The simple form is `docker run --privileged dind` to spin up a Docker daemon inside a container. Many CI runners (GitLab CI, Jenkins agents, Drone) use this pattern. KVM is enabled, so containerd, podman, and rootless Docker also work without tricks.
Can I run Hyper-V inside a Cloudzy Windows VPS?
Yes. Pick the Windows VPS plan, enable the Hyper-V role from Server Manager or PowerShell (Install-WindowsFeature -Name Hyper-V), then create inner VMs from the Hyper-V Manager. You'll want at least 4 GB on the outer VPS to leave room for Windows Server + one inner VM.
What's the difference vs running my workload in one big VPS?
Nested VMs give you stronger isolation than containers, separate kernels, separate user-spaces, separate networking, at the cost of some performance and RAM. Pick nesting when you need to test kernel modules, run untrusted code, simulate a multi-machine network, or train people on hypervisor administration.
Are there any hidden fees?
No. Nested virt is included on every Cloudzy plan at no extra charge. Egress, snapshots, IPv4 + IPv6, and root access are all included. The only paid extras are Floating IPs ($2.50/month) and additional snapshots beyond the free quota.
How fast is provisioning?
Once payment is confirmed, your VPS is live in 60 seconds. You'll receive an email with the IP, root password, and SSH connection string within seconds, and /dev/kvm is already exposed inside the guest.
Is there a money-back guarantee?
Yes, 14 days from purchase, no questions asked, full refund. Apply from the panel or email [email protected].
Ready when you are.
Nested in 60 seconds.
Pick a plan, pick a region, click. /dev/kvm waiting on the other end.
No credit card required · 14-day money-back guarantee · Cancel anytime