
Hypervisors and server virtualisation: what that layer does and which type to choose
A hypervisor is the software that divides one physical server into several virtual machines, each with its own operating system. Almost every server estate in a small or mid-sized organisation now runs on one, yet it is the layer people think about least. This is what a hypervisor does, which type belongs where, and the four design questions in server virtualisation that make the difference.
A hypervisor divides one physical server into virtual machines. Servers need a type 1, which runs directly on the hardware; a type 2 is for a laptop or a test environment.
How many fit on a host depends more on memory and storage than on the number of cores. And one host is one failure: if you cannot accept downtime, you need a second.
The hypervisor is the most valuable target in your estate, because whoever controls it controls every machine on it. Keep management separate and the backup outside it.
What a hypervisor does
A physical server has processors, memory, disks and network cards. The hypervisor takes these over and gives each virtual machine its own share: a number of virtual processors, an amount of memory, a virtual disk and a virtual network card. The operating system inside does not notice and runs as if it had a server of its own.
The key consequence: a virtual machine is a set of files. You can copy it, capture it in a snapshot before an update, move it to another host and restore it from a backup without reinstalling anything. That is why server virtualisation has become the norm, even in small environments.
The hypervisor also decides whose turn it is. With ten machines on one server, it shares out processing time and memory, and keeps them apart: a machine that hangs or gets infected cannot simply reach the others.
Type 1 and type 2: on the hardware or as an application
There are two kinds, and they belong in different places.
- Type 1, also called bare metal, runs directly on the hardware with no ordinary operating system underneath. This is what belongs on servers: VMware ESXi, Microsoft Hyper-V and KVM, the Linux hypervisor on which Proxmox VE and Nutanix AHV, among others, are built.
- Type 2 is an application on Windows, macOS or Linux, such as Oracle VirtualBox, VMware Workstation or Parallels Desktop. Useful for a developer, a test environment or an old application on a laptop, but not for production: whatever the underlying operating system does (updates, restarts, a virus scanner) affects every machine on it.
In practice the line blurs a little. Hyper-V is switched on within Windows and KVM sits in the Linux kernel, so they look like applications, but they work as type 1. For the decision it makes no difference: a server gets a type 1, a workstation possibly a type 2.
Which operating system then belongs in the virtual machines is a separate question, covered in our article on Windows or Linux for your servers.
What server virtualisation delivers, and what it does not solve
What it delivers: fewer physical servers for the same work, one application per virtual machine without buying a server for each, a new server in minutes from a template, a snapshot as a safety net before an update, and hardware replaced without rebuilding the software: you move the machines to the new host.
What it does not solve:
- Host failure. Ten servers on one machine means one failed power supply stops ten servers at once. Virtualisation concentrates risk unless you spread it.
- Backup. A snapshot sits on the same storage as the machine itself. If that storage fails, or an attacker with admin rights deletes everything, the snapshot goes too.
- Old software. An outdated operating system in a virtual machine is still outdated. You can shield it better, but it remains a risk you manage rather than solve.
- Licences. Software inside the virtual machines is licensed separately, and some licences, such as Windows Server, count the physical cores of the host rather than the virtual machine.
How many virtual machines fit on one host
This is the calculation that most often goes wrong, because it usually starts with the number of cores while that is rarely the limit.
- Processors can be allocated more generously than there are cores, because not every machine computes at once. But do not give a machine more virtual processors than it needs: the hypervisor has to schedule them together, and too many make a machine slower rather than faster.
- Memory should not be overallocated in production. When it runs out, the hypervisor starts swapping to disk, and every machine on the host slows down at once.
- Storage is often the first real limit. Not capacity, but how quickly the disks respond when all machines read and write at the same time, during the nightly backup or on a Monday morning.
So measure first what the existing servers actually use, over a few weeks and including the busy moments, rather than working from what they were given when they were bought. And leave room for growth and for the moment a host is in maintenance.
One host or several
The question is not how many servers you have, but how long everything may be down if the host fails.
- One host with a good backup is reasonable for a small organisation that can absorb a few hours of downtime and knows how long a restore really takes. Test it, because a recovery time that has never been measured is a guess.
- Two or more hosts with shared storage make high availability possible: if a host fails, its machines start on another. And you can update a host while the machines keep running next to it. The shared storage is a separate storage system or software that pools the hosts’ disks.
- A second host at another location, with replication, protects against losing the whole room. That is a continuity question rather than a server question; only start on it once the first two steps are in place.
With more than one host, the rule is that the whole estate must run with one host fewer. Otherwise you have paid for a second host without getting the reason for it.
Virtual machines or containers
A container is lighter than a virtual machine: it shares the operating system kernel with other containers and holds only the application and what it needs. It starts in seconds and takes up little space.
Containers suit software built for them, usually in-house applications or modern web services. Virtual machines suit everything else: standard software that expects a full Windows server, a finance package, a domain controller, a vendor application supported only on a specific operating system.
It is rarely a choice between the two. In most environments containers run inside virtual machines, and the hypervisor remains the layer underneath.
Managing and securing the hypervisor
Whoever controls the hypervisor controls every machine on it: they can shut them down, copy them or encrypt them in one go. That is why ransomware attackers increasingly go after this layer. Five measures that make the difference:
- Management on its own network. The hypervisor’s management interface is not reachable from the office network or the internet, only from a protected management workstation.
- Dedicated admin accounts with multi-factor authentication. Not the same accounts as in the virtual machines’ domain; whoever takes over the domain must not automatically get the hypervisor as well.
- Updates in a fixed order. The hosts need security updates too. With more than one host, move the machines first, update the host and repeat host by host.
- A backup outside the hypervisor, with at least one copy that cannot be altered. How to set that up is in our article on the 3-2-1 backup rule.
- Supported versions. A hypervisor without updates from the manufacturer is an open door beneath all your servers. Put the end of support in your planning.
Where our work stops
What we do. Measuring what the current servers use, designing the virtualisation estate (how many hosts, which storage, which network for management), supplying servers and switches, setting up the hypervisor, converting existing servers into virtual machines and managing it all afterwards, including updates and the backup alongside. We deliver worldwide and have our own local engineers on site in every country.
What we do not do. We do not make hypervisors: the software, its support and the licence terms come from the manufacturer. We do not promise availability the design cannot carry; one host remains one failure, even when we manage it. And we are not an electrical contractor: the power circuits and cooling of the room where the servers stand are work for an installer.
Questions we get about this
The five that come up most often.
What is a hypervisor?
Software that divides one physical server into several virtual machines, each with its own operating system. The hypervisor gives each machine a share of the processors, memory, storage and network, and keeps the machines apart. Because a virtual machine consists of files, it can be copied, moved and restored.
What is the difference between a type 1 and a type 2 hypervisor?
A type 1 runs directly on the hardware and is meant for servers, such as VMware ESXi, Microsoft Hyper-V and KVM. A type 2 is an application on an ordinary operating system, such as VirtualBox or Parallels Desktop, and is meant for a workstation or a test environment. For production, choose a type 1.
Which hypervisor is best for a small business?
That depends less on the product than on who manages it and what is already there. An estate that mainly runs Windows is often well served by Hyper-V; with Linux skills in house or at the support partner, Proxmox is a strong choice; VMware is common in existing environments. Also check that your backup software supports the hypervisor.
What is the difference between virtualisation and containers?
A virtual machine contains a full operating system; a container shares the operating system kernel with other containers and holds only the application. Containers are lighter and suit software built for them. Standard software and Windows applications usually run in virtual machines, and containers often run inside those.
Do you also supply the hypervisor licences and vendor support?
We can buy the licences for you and supply the servers, but the licence terms and the support on the software come from the manufacturer, who also decides what changes at renewal. We design, build and manage the environment, and bring in the manufacturer when the problem lies in their software.
Further reading
What server virtualisation connects to.
The brands above, one page each
What the brand makes, which lines we supply and what we do around it.
Shall we measure what your servers really use?
Let us watch processor, memory and storage on your current servers for a few weeks. Then you know how many hosts you need, and whether one is enough.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.