KVM or OpenVZ: which to choose

In 2026 KVM is almost always the right pick: it costs a dollar or two more per month than OpenVZ, but everything runs on it, from Docker to Windows. OpenVZ makes sense in one narrow case, explained below, and at the end you will find the commands to check your own server in a minute.

Updated 28.10.2026 · Find a VPS for your needs →

The short answer: take KVM. On KVM you have your own system kernel, and the server behaves like an ordinary computer: Docker, Windows and any Linux version install fine, and your own firewall and swap work. OpenVZ is a container that shares a kernel with the neighbours on the same physical machine. It is cheaper and lighter, but some familiar programs will not start in it, and you usually find that out after you have paid.

OpenVZ only makes sense if the task is simple, runs on Linux without Docker, and the price difference actually matters to you. Below I look at how big that difference is in practice and what exactly breaks in a container.

How much cheaper OpenVZ really is

Less than you might think. I compared plans with the same amount of memory at the same host: I took the cheapest KVM plan and the cheapest OpenVZ plan and looked at the difference. That gave between 15 and 29 hosts depending on the memory size, using the accsly catalog data of 27 October 2026. The catalog stores prices in roubles, so the dollar amounts are rounded.

With 2 GB of memory, KVM at the median costs well under a dollar more per month, about 16%. With 4 GB the gap is larger, about $2 or 30%. Over a year that comes to somewhere between $8 and $25. And at a third of the hosts that sell both types, KVM of the same size costs the same or even less, so the first step is simply to compare plans within one host.

Choosing OpenVZ also narrows the field a lot. Of the 26,640 plans in the catalog, 501 run on OpenVZ, which is 1.9%, and they are sold by 84 hosts out of 2,175. KVM accounts for 93.5% of all plans (I counted in those where the host did not state the virtualization, because these days the default is almost always KVM). The rest are VMware, Hyper-V, Xen and LXC containers, and for you as a user the first three behave just like KVM.

So the saving on OpenVZ is roughly the price of a coffee a month, and you pay for it with restrictions. For work you would hate to lose, I would not make that trade.

What will not work in an OpenVZ container

Anything that needs its own system kernel. In a container there is one kernel for the whole physical machine, and only the host can change its settings. In practice it looks like this.

Docker often does not install or runs with errors. Many hosts state in their terms that they do not support Docker on OpenVZ. On OpenVZ 7 it sometimes starts if the host has enabled the required features for the container, but you need to confirm that before paying. If your project is built on Docker or you plan to run n8n, GitLab Runner or Kubernetes, look only at KVM or the VPS for Docker selection.

Windows will not run at all. The container uses the host's Linux kernel, so a different operating system is impossible inside it. The catalog has not a single OpenVZ plan with Windows, while among KVM plans Windows is available on about half. Selection: Windows VPS.

The kernel is old and cannot be upgraded. OpenVZ 7 runs kernel 3.10, and the outdated OpenVZ 6 runs 2.6.32. Current distributions are designed for newer kernels, so the host may not have a template for the Ubuntu version you need. Anything added to the kernel later will not work either: for example, the BBR algorithm, which speeds up file delivery over long distances, needs kernel 4.9 or newer.

You cannot load your own kernel modules. This includes, for example, in-kernel WireGuard for a private network between an office and a server. It can be replaced with a version that works without the module, but only if the host has enabled the TUN network device for the container. How to build such a network on a regular KVM server is covered in the article a corporate network on a VPS.

You cannot add swap. The swapon command does not work in a container, so when memory runs out, the process is simply killed. On KVM you can create a 1–2 GB swap file in a minute and get through a load spike.

Memory is counted differently. OpenVZ plans often say something like "1 GB guaranteed, up to 2 GB", and the upper figure is only available while it is free on the host. Plan around the lower one.

When OpenVZ is still a reasonable choice

When the task is small, runs on Linux and does not need Docker. Say you need a server for a simple Python bot, a static site, uptime monitoring of other sites or tests you would not mind losing. A container will cope with that, and over a year you will save roughly $10–12.

Another advantage of a container is that it has almost no overhead. The system boots in seconds, and none of the plan's memory goes to the virtualization itself. On 512 MB plans this is noticeable: on KVM the kernel and system services take about 100–150 MB of it, in a container less.

If this option suits you, the plans are collected in the OpenVZ VPS selection. LXC, a container built along similar lines, is rarer, at about 0.6% of plans, and its limitations are almost the same: LXC VPS.

Is KVM always more honest?

Not always. KVM by itself does not guarantee that the processor is not shared with a dozen neighbours: on inexpensive plans the cores are still shared. The difference is that overselling is easier to spot on KVM, because the system shows how much time the neighbours took away from your machine. I show how to check this below. If the processor will be busy all the time, look for plans with dedicated cores, and for fast single-threaded work, high-frequency CPU VPS.

What to take for your task

A site on WordPress, Drupal or Laravel with a database: KVM. The site benefits from swap for traffic spikes and from a current PHP version, and it makes no sense to put up with an old kernel to save a dollar a month. Selection: VPS for a website.

Anything on Docker, including n8n, GitLab and Kubernetes: KVM only, there is no alternative. Windows and software built for it: also only KVM or Hyper-V.

A Telegram bot in Python or Node.js without Docker, monitoring, a test environment: OpenVZ will do, if it is noticeably cheaper at the same host. If the difference is only a dollar or so a month, I would still take KVM: when you move to Docker or a new system version, you will not have to change servers.

How both types work and a table of differences are in the article VPS vs VDS; here we move on to practice.

How to find out what your server runs on

Hosts do not always state the virtualization in the plan, and sometimes they state it wrongly. You can check it in a minute by connecting to the server over SSH. The simplest command is available on any modern Linux:

systemd-detect-virt

It prints a single word. kvm means KVM, openvz an OpenVZ or Virtuozzo container, lxc an LXC container, vmware and microsoft VMware and Hyper-V, xen Xen. If the output is none, you got a physical machine without virtualization. hostnamectl shows the same thing in its Virtualization line.

If there is no systemd or you want to confirm the answer, there are three indirect signs:

ls /proc/user_beancounters /proc/vz 2>/dev/null   # these files exist only in OpenVZ
uname -r                                          # kernel version
lscpu | grep -i hypervisor                        # on KVM: Hypervisor vendor: KVM

If the first command printed anything, you are in an OpenVZ container. A kernel version like 2.6.32-042stab… means OpenVZ 6, and one with vz7 in the name means OpenVZ 7. There is also the virt-what utility, installed with apt install virt-what and run as root; it recognises more of the rare cases.

How to tell that neighbours are crowding your server

On KVM, look at steal, the time the hypervisor gave to other machines while yours was asking for the processor:

vmstat 1 10

You need the st column on the right. If it shows 0–2, everything is fine. If under load it stays above 5–10, the neighbours are taking a noticeable share of the processor, and the server will run slower than the plan promises. The same figure appears in top as st in the %Cpu line.

In OpenVZ steal is usually not visible, but there is a counter of hit limits instead:

cat /proc/user_beancounters

Look at the last column, failcnt. A non-zero value in the privvmpages or physpages row means the container ran short of memory and some requests were refused. If the numbers keep growing, the plan is too small for your task, even if free shows free memory.

Run these checks in the first days after payment, while the refund period is still valid. Plans that offer one are in the money-back VPS and free trial selections.

FAQ

Which is better for a website, KVM or OpenVZ?

For a site with a database, KVM is better: you can add swap, install a current system version and any software. A simple PHP site will run on OpenVZ too, but the saving at one host is usually somewhere between half a dollar and two dollars a month.

Does Docker work on OpenVZ?

Often not. Docker does not work on OpenVZ 6, and on OpenVZ 7 it only starts if the host has enabled it for the container. If your project uses Docker, take KVM.

How much cheaper is OpenVZ than KVM?

At the same host with the same memory, KVM at the median costs well under a dollar more per month with 2 GB and about $2 more with 4 GB, according to the accsly catalog on 27 October 2026. At a third of these hosts, KVM costs the same or less.

How can I find out which virtualization my VPS uses?

Run systemd-detect-virt on the server. It prints kvm, openvz, lxc, vmware, microsoft or xen. Another sign of OpenVZ is the presence of the /proc/user_beancounters file.

Can I switch from OpenVZ to KVM without reinstalling?

No, they are different technologies, and a container cannot be turned into a virtual machine. You will have to order a new KVM server and move your files, databases and settings to it.

How is LXC different from OpenVZ?

For the user, hardly at all: both are containers that share the host kernel, with no Windows and no custom kernel modules. LXC is common at hosts running Proxmox, and the kernel there is usually newer than on OpenVZ 7.

Plans on this topic

VPS for Kubernetes and k3sXen VPSVMware VPSHyper-V VPSBest VPS hosting 2026

More in the guide

  • Docker on a VPS: getting startedDocker lets you run a bot, a website, a database and monitoring on one server without them getting in each other's way, and moving to another VPS comes down to copying a couple of files and the data. Installation takes five minutes; the real trouble starts later: database ports exposed to the internet, logs growing to tens of gigabytes and data that vanished along with a container. Here is how to avoid all of that from the start.
  • How to move a website from shared hosting to a VPSThe move itself takes a couple of hours; the mistakes usually happen around it: a forgotten cron job, .htaccess rules that nginx does not read, an AAAA record with the old address, or mail that disappeared along with the IP change. Below is the order of steps with commands and checks for a PHP and MySQL site.
  • Server control panels: ISPmanager, FASTPANEL, aaPanelA panel turns a VPS into the kind of dashboard you know from shared hosting: sites, databases, mail and certificates are set up with a few clicks instead of editing config files. The three panels most often installed on Russian and budget international servers are ISPmanager, FASTPANEL and aaPanel. They differ in price, memory requirements and how much of the server they take over.
  • Windows VPS for 1CA rented server for 1C saves you from the office PC under a desk that nobody updates or backs up. But 1C on a VPS has its own quirks: the software licence is tied to the parameters of the virtual machine, users need both 1C and Windows licences, and core speed matters more than core count. Here is how to put together a 1C server for a small company.
  • Windows VPS: licensing, RDP and secure sign-inA Windows server costs more than Linux not only because of memory: the price includes a licence, and how it is arranged decides whether you are compliant and how many people can connect. An exposed RDP port is also the most common way such servers get hacked. Here are both topics.
  • When to move from shared hosting to a VPSA VPS does not make a site faster by itself: it gives you resources and freedom, and with them the job of running a server. Here is how to tell that hosting has become too small, when the problem can be solved without moving, and how to migrate a site so visitors notice nothing.
  • VPS backups: strategies and toolsOn a VPS, backups are your job, even if the plan says "backups included". We go through what exactly to back up, why a host snapshot is not enough, how to set up restic or BorgBackup in half an hour, and how to make sure you can actually restore from a backup.
  • First 10 steps after buying a VPS: securityBots start guessing passwords on a new server within minutes of it getting a public IP. Below are ten steps that close the most common holes in about an hour: commands for Ubuntu and Debian, the differences for AlmaLinux and Rocky Linux, and the checks that keep you from locking yourself out of your own server.
  • How to choose a country for your serverPut the server where your visitors are. For an audience across Europe, Germany, the Netherlands and Finland are convenient; for North America, the US East Coast. If you serve EU users, keeping the data in the EU makes GDPR simpler. Price hardly decides it: at the same host a server in Frankfurt, Amsterdam or New York usually costs the same, and only Asia and Australia are noticeably more expensive.
  • Hourly billing: when it pays offHourly billing pays off if you need the server for less than three weeks a month: for a test, a build, a one-off heavy job. At most hosts an hour costs exactly the monthly price divided by 730 hours, so over a full month you hardly overpay. The overpayment hides elsewhere: hourly plans are dearer on average, and for a server that runs all year, monthly billing or a year paid in advance usually comes out cheaper.
  • How much RAM and how many cores a website needsMost websites are fine with 2 GB of memory and one or two cores; a shop with thousands of products needs 4 GB and two cores. Memory matters more than cores: when it runs out, the site slows down or crashes, while an extra core without memory adds almost nothing. Below I show how to work out the memory for your site and how to see what it actually uses.
  • NVMe or SSD: does it matter for a websiteFor a small site the difference between NVMe and SSD is barely noticeable, because pages are served from memory rather than from disk. It shows up in shops and sites with a large database. At the same host NVMe costs only about $0.50–1 a month more, and sometimes less, so what usually decides it is not the disk type but its size and how the host has limited it.
  • What is a VPS, in plain EnglishA VPS is a slice of a powerful physical server that you rent and that behaves like a separate computer, with its own operating system, its own IP address and full control. Below is how it differs from shared hosting, who needs one, what it costs and what to check right after you buy it.
  • VPS for a Telegram bot: what the bot needs and how to pick a planA bot with a menu and a few commands runs fine on the cheapest server, while a bot with broadcasts, files and a database hits completely different limits. Here is what a bot really consumes, which Telegram limits shape the choice of server and how to avoid overpaying.
  • How to test VPS ping and speed before you payThe numbers in a plan do not tell you the latency to your users or how fast the disk really is. Most of this can be measured before you pay, the rest in the first hour after launch. Here are the tools and how to read the results.
  • Corporate network on a VPS: remote access to the officeA rented server can become the hub of a company's private network: remote employees and branch offices connect through it to the ERP, file server, CRM and Git. Here are the common layouts, protocols, server requirements and security basics.
  • How to choose a VPS: the 7 specs that matterTwo plans with the same "2 cores, 4 GB, 50 GB" can differ several times in speed and twice in price a year later. Here is what stands behind each line of a VPS plan and what to check before you pay.
  • VPS vs VDS: is there a difference and what actually mattersIn most markets VPS and VDS mean the same thing: a virtual server. The difference that really affects your work is hidden not in the name but in the virtualization type and whether resources are guaranteed.