A virtual machine (VM) is software that emulates a full physical computer, running its own operating system and applications while sitting entirely inside a real host machine. You can run a Linux system inside a Windows laptop, or spin up a dozen separate Windows servers on a single rack-mounted box in a data centre. Each VM believes it has exclusive access to its own CPU, memory, storage, and network card. It doesn't. It's sharing hardware with everything else on the host.
This idea sounds abstract until you realise how much of the modern internet runs on it. When a company rents a server from Amazon Web Services or Microsoft Azure, what it receives isn't a physical box. It's a VM.
The role of the hypervisor
The piece of software that makes virtualisation possible is called a hypervisor. Its job is to sit between the physical hardware and the virtual machines, managing which VM gets access to which resources and when.
There are two main types. A Type 1 hypervisor runs directly on the hardware with no host operating system beneath it. VMware ESXi and Microsoft Hyper-V in bare-metal mode are examples. A Type 2 hypervisor runs on top of a conventional operating system the way any other application would. VirtualBox and VMware Workstation work this way. Type 1 is faster because there's one fewer layer. Type 2 is easier to set up on a personal laptop.
The hypervisor allocates slices of CPU time, blocks of RAM, and chunks of disk space to each VM. When a VM sends an instruction that touches real hardware, the hypervisor intercepts it, translates it, and executes it safely. No VM can reach beyond its allocated resources and touch another VM's data. That isolation is what makes VMs so useful for security.
What's actually inside a virtual machine
Each VM is defined by a small set of files stored on the host. One file describes the machine's configuration: how many virtual CPUs it has, how much RAM is allocated, which network adapters are attached. Another file, often very large, is the virtual hard disk. It's a single file on the host that the VM sees as a whole drive.
When you power on a VM, the hypervisor reads those files and starts the boot process just as a physical machine would. The guest operating system loads, drivers initialise, and within seconds you have a fully functional computer in a window on your screen. Shut it down and all that state sits dormant in those same files, ready to restart in seconds.
This portability matters. A VM image can be copied to a USB drive, uploaded to cloud storage, or moved to a different physical server. The whole machine travels with it.
Snapshots and why they change how software is tested
One of the most practical features of virtual machines is the snapshot. A snapshot captures the exact state of a VM at a moment in time: the contents of RAM, the state of every file on the virtual disk, every running process. You can take a snapshot before installing risky software or running an update, and if something breaks, roll back to that point in seconds.
Software developers use this constantly. Test an application, roll back, change something, test again. No reinstalling. No waiting for a fresh machine to provision. It compresses hours of work into minutes.
Security researchers use snapshots to study malware safely. They infect a VM, watch what the malware does, then roll the whole environment back to clean without touching the host system. Understanding concepts like zero-day exploits becomes a lot more practical when you can observe them in a sandboxed VM rather than on a machine you actually use.
VMs versus containers
Virtual machines are sometimes compared to containers, and the comparison is worth understanding. Both create isolated environments for software. The difference is in what they include.
A VM carries a full operating system inside it, every kernel, every driver, every system library. A container shares the host's kernel and packages only the application and its dependencies. Containers start in milliseconds; VMs take seconds to minutes. Containers are lighter and more efficient. VMs offer stronger isolation because a compromised container can, in some attack scenarios, affect the host kernel, while a compromised VM typically can't escape past the hypervisor.
As covered in MediaChannel's guide to software containers, both technologies solve similar problems with different trade-offs. Many production environments use both: containers for fast, lightweight application packaging, and VMs as the underlying isolated environment those containers run in.
How cloud computing uses virtual machines at scale
When you spin up a compute instance on a cloud platform, you're provisioning a VM. The cloud provider runs a fleet of physical servers, each one hosting dozens or hundreds of VMs simultaneously. The hypervisor handles the resource allocation, billing is calculated per second of compute time used, and the physical machine underneath is entirely invisible to you.
This model lets cloud providers make extraordinary use of hardware. A physical server sitting at 10 per cent utilisation is wasteful. Pack it with VMs, each running different workloads for different customers, and utilisation climbs sharply. That efficiency is what makes cloud services affordable. The operating system kernel each VM runs is entirely separate from every other VM on the same box, maintaining the security boundary customers depend on.
Live migration is one of the more remarkable things cloud-scale virtualisation enables. A running VM can be moved from one physical server to another with no downtime. The hypervisor copies the VM's memory pages to the destination machine while the VM keeps running, then pauses it for milliseconds to sync the final state, and resumes it on the new host. The application inside never knows anything happened.
Who actually uses virtual machines
Developers use VMs to test software on different operating systems without maintaining separate machines. System administrators use them to consolidate many server workloads onto fewer physical boxes. Security professionals use them to safely analyse malicious files. Educators use them to give students isolated environments where mistakes can't cause real damage.
At home, the most common use is running a second operating system. An Australian user on a Mac might run a Windows VM to access software that isn't available on macOS. VirtualBox from Oracle is free and works on Windows, macOS, and Linux, making it the most accessible entry point for anyone curious about virtualisation.
VMs have been around since the 1960s, when IBM built them into mainframes so different departments could share expensive hardware without interfering with each other. The core idea hasn't changed. What's changed is that the hardware is now fast enough to make a VM feel indistinguishable from a real machine.
The virtual machine is one of the most consequential abstractions in computing. It turned physical hardware into something that can be divided, copied, moved, and replaced without touching a single physical component.