All subjects · Information Technology · WIT13 2 hour written exam on data, enabling technologies and systems development
Virtualisation: virtual machines and containers
Edexcel IAL Information Technology · WIT13 2 hour written exam on data, enabling technologies and systems development
Virtualisation lets one physical computer behave like many separate ones. It underpins cloud computing. You need to know what it is, why it is used, and the two main ways of achieving it: virtual machines and containerisation (spec 13.1.1 and 13.1.2).
What virtualisation is
Virtualisation is the use of software to create a virtual (simulated) version of a computing resource, such as a server, storage device, network or operating system, so that one set of physical hardware can be shared by several isolated environments.
Why it is used:
- Better use of hardware: many lightly used servers can be consolidated onto a few hosts, cutting hardware, energy, cooling and space costs.
- Isolation: a crash or infection in one virtual environment does not affect others.
- Flexibility and scaling: new servers can be created in minutes from a template; resources can be reallocated.
- Testing: developers can test software on different operating systems on one machine.
- Backup and recovery: a whole virtual machine can be saved as files, copied and restored, or moved to another host.
- Legacy software: old applications can run on an old operating system inside a VM.
Drawbacks: the host is a single point of failure for all its guests unless replicated; some performance overhead; licensing complexity; staff need specialist skills.
Virtual machines
A virtual machine (VM) emulates a complete computer: virtual CPU, memory, disk and network card, with its own full guest operating system.
A hypervisor creates and runs VMs and shares the physical hardware between them:
- Type 1 (bare metal) runs directly on the hardware (used in data centres).
- Type 2 (hosted) runs as an application on a normal operating system (used on desktops for testing).
Setting up: create the virtual platform, install an operating system, then install applications or restore a backup.
Containerisation
A container packages an application with its libraries and settings into a container image. A container engine (Docker is a well-known example; Linux Containers is another) runs containers on a shared host operating system kernel.
Compared with VMs, containers:
- are much smaller (megabytes rather than gigabytes) and start in seconds, because there is no guest operating system to boot;
- allow many more instances per host;
- run identically on any machine with the engine, so 'it works on my machine' problems disappear;
- give weaker isolation than VMs, because all containers share one kernel, and all must use the host's type of operating system.
VMs and containers compared
| Feature | Virtual machine | Container |
|---|---|---|
| Includes a full operating system | Yes, its own guest OS | No, shares the host kernel |
| Managed by | Hypervisor | Container engine |
| Size and start-up | Gigabytes; minutes | Megabytes; seconds |
| Isolation | Strong | Weaker |
| Different OS from host | Possible | Not possible |
| Best for | Running different operating systems, strong separation, legacy systems | Deploying and scaling many copies of applications and microservices |
Worked example
A company has 24 physical servers, each running at 12% average utilisation. It wants to consolidate them as VMs onto hosts run at no more than 75% utilisation. How many hosts are needed (assume each host matches one old server)?
- Total workload = 24 x 0.12 = 2.88 servers' worth
- Hosts = 2.88 / 0.75 = 3.84
- Round up: 4 hosts
Answer: 4 hosts instead of 24
Check yourself
- What creates and manages virtual machines?
- A container image
- A compiler
- A router
- A hypervisor
Show answer
A hypervisor. The hypervisor shares the hardware between VMs.
- Why do containers start much faster than virtual machines?
- They use faster hard disks
- They share the host's operating system kernel, so no guest OS has to boot
- They do not use memory
- They are written in machine code
Show answer
They share the host's operating system kernel, so no guest OS has to boot. No guest OS to load.
- A bank wants the strongest separation between two systems on the same hardware. Which is more suitable?
- Containers
- One shared operating system with two user accounts
- One container running the two systems together
- Virtual machines
Show answer
Virtual machines. VMs have their own OS and stronger isolation.
- Thirty servers each run at 10% utilisation. They are consolidated onto identical hosts run at up to 60%. How many hosts are needed?
Show answer
5. 30 x 0.1 = 3; 3 / 0.6 = 5 hosts.
- A business must keep using software that only runs on an old operating system. How does virtualisation help?
- Containers can run any operating system on any kernel
- Virtualisation updates the software automatically
- The old OS can run as a guest VM on modern hardware
- It converts the software to a web app
Show answer
The old OS can run as a guest VM on modern hardware. A VM can host a different OS from the host.
- Which is a drawback of consolidating many servers onto one host?
- If the host fails, all its virtual servers fail too
- It always increases electricity use
- Each VM needs its own physical network cable
- VMs cannot be backed up
Show answer
If the host fails, all its virtual servers fail too. Single point of failure unless replicated.
- Explain one reason why an organisation might virtualise its servers.
Show answer
Several underused physical servers can be combined onto one host, so the organisation buys and powers less hardware, which reduces costs.. Consolidation, so lower costs.
Sources
- Pearson Edexcel International Advanced Level in Information Technology specification (first teaching 2018), Issue 2, February 2021
- Pearson Edexcel IAL Information Technology: scheme of work for Unit 3
Last updated 8 November 2026. Spotted a mistake? Tell us.