Run virtual machines smoothly on elementary OS with GNOME Boxes
GNOME Boxes gives elementary OS users a straightforward way to run another operating system in a window. It uses the QEMU and KVM virtualisation stack underneath, while presenting the complicated parts through a clean graphical interface. You can test an Ubuntu release, explore Fedora, run a small Windows installation, or open a disposable environment for software experiments.
A virtual machine (VM) behaves like a separate computer with its own virtual disk, memory and operating system. It does not replace elementary OS, and removing the VM does not normally affect the host system. This makes Boxes useful for trying applications, checking website layouts, learning Linux administration and opening files in an isolated environment.
The smoothest experience depends on hardware virtualisation being available and enabled. Modern Intel and AMD processors usually support it, although firmware settings can disable the feature. Before downloading a large ISO, check the available memory, storage space and network connection, particularly if your NBN connection has a monthly data limit or slower evening performance.
What GNOME Boxes does
Boxes is a virtual machine manager designed for simple desktop use. Its main window displays existing machines, and creating one normally involves selecting an ISO image, choosing resources and starting the installation. The guest operating system then runs inside a window alongside your elementary OS applications.
The program relies on QEMU for hardware emulation and KVM for processor-assisted virtualisation. KVM is important because it allows the host CPU to execute much of the guest workload directly. Without it, a VM may still start through software emulation, but performance can be poor and the machine may appear unresponsive.
Boxes is deliberately less complex than tools such as VirtualBox or virt-manager. It hides many advanced settings, which is helpful when you want to install a desktop distribution quickly. Advanced users may eventually prefer virt-manager for custom networking, storage pools, PCI passthrough or detailed firmware settings, but Boxes is an excellent first virtualisation tool.
A VM consumes real resources. A guest with 4 GB of RAM on a computer with 8 GB leaves little room for elementary OS and its applications. Likewise, a virtual disk is usually stored as a growing image file, so a guest that starts at a few gigabytes can gradually use much more space.
Check elementary OS and hardware first
Open System Settings and check the About panel to identify your elementary OS release and available memory. Keep at least 20–30 GB of free disk space for a modest Linux guest, with additional room for updates and personal files. A Windows guest generally needs more storage, and Microsoft’s current requirements should be checked before installation.
Virtualisation is usually enabled in UEFI firmware under a setting named Intel VT-x, Intel Virtualization Technology, AMD-V or SVM Mode. To inspect whether KVM is available, open Terminal and run:
egrep -c '(vmx|svm)' /proc/cpuinfo
A result greater than zero indicates that the processor exposes a virtualisation flag. This does not guarantee that firmware has enabled every required feature, but it is a useful first check. You can also inspect the KVM device after installing the relevant packages:
ls -l /dev/kvm
If /dev/kvm is missing, restart the computer, enter UEFI setup and look for the processor virtualisation option. Firmware menus vary by manufacturer, so the setting might be under Advanced, Security or CPU Configuration. On many laptops sold in Australia, including models commonly used in Sydney, Melbourne and Brisbane offices, it is enabled by default.
Download guest operating systems from their official websites. Verify the checksum when the publisher provides one, particularly for a server image or a distribution you intend to use for sensitive work. An Australian user on a slower regional NBN service may prefer downloading overnight, while a faster fibre connection makes several large ISO images easier to manage.
Install Boxes and create a guest
The simplest graphical route is to open AppCenter and search for GNOME Boxes, if a package is available for your elementary OS release. You can also install it from Terminal. On the Ubuntu-based releases of elementary OS, the following command installs the application and its usual virtualisation components:
sudo apt update
sudo apt install gnome-boxes qemu-kvm libvirt-daemon-system libvirt-clients
The package manager may install additional dependencies. Read the proposed package list, enter your password and allow the process to finish. If the installer reports that a package is unavailable, use the Flatpak version through AppCenter or Flathub instead. Flatpak can be useful when the distribution repository carries an older build.
After installation, sign out and back in if Boxes cannot connect to the virtualisation service. You can also add your account to the libvirt group:
sudo usermod -aG libvirt "$USER"
A new group membership normally takes effect after logging out and in again. Avoid using sudo gnome-boxes; running the graphical application as root can create confusing ownership and permission problems in your home directory.
Launch Boxes from the Applications menu and select the button to create a new virtual machine. Choose an operating system image from the recommended list, browse to an ISO already stored on your computer, or enter a download address where supported. The selected ISO must match the architecture of your host; current elementary OS computers are generally x86-64, while ARM devices may require different images and have more limited guest support.
Before starting the installation, expand the customisation controls. Set memory and disk size according to the guest’s requirements. A lightweight Linux desktop can often work with 2–4 GB of RAM, while a modern Windows desktop is more comfortable with at least 4–8 GB and substantially more storage. Leave enough resources for the host system, especially if you plan to keep a browser, music player and office applications open in elementary OS.
| Use case | Suggested memory | Suggested disk | Practical note |
|---|---|---|---|
| Lightweight Linux test | 2 GB | 15–25 GB | Good for trying a desktop or command-line tools |
| General Linux desktop | 4 GB | 30–40 GB | Comfortable for updates and everyday testing |
| Windows evaluation | 6–8 GB | 64 GB or more | Check Microsoft’s hardware and licence requirements |
| Server or development lab | 2–8 GB | 20–80 GB | Size depends on containers, databases and test data |
Click Create and follow the guest installer. The VM may boot from the ISO automatically. If it returns to the installer every time, shut down the guest, open its properties and remove the ISO from the virtual optical drive, or change the boot order. Keep the ISO if you want to reinstall later, but do not leave it attached accidentally.
Use the virtual machine safely
Boxes supports the usual VM controls for pausing, shutting down and forcing a power-off. Prefer the guest operating system’s normal shutdown command, just as you would on physical hardware. Pausing is useful when you need to free CPU time temporarily, although it still reserves some memory and can leave an old session suspended for a long period.
The guest and host are separate, but they are not automatically a security boundary for every situation. Keep both systems patched, install software from trusted sources and avoid opening untrusted files with shared folders or clipboard integration enabled. A VM is helpful for examining unfamiliar software, yet a carefully designed malware analysis environment requires snapshots, restricted networking and more specialised controls.
Networking normally uses NAT, allowing the guest to access the internet through elementary OS without appearing as a separate device on your home network. This is convenient for updates and web testing. Bridged networking gives the guest its own presence on the local network, but it needs more configuration and can behave differently across Wi-Fi and Ethernet connections.
Shared folders and drag-and-drop features vary by guest operating system and Boxes version. If a feature does not work, use a temporary cloud upload, a USB device passed through to the VM, or a network transfer method such as SSH. Do not share your entire home directory. Sharing a dedicated folder limits accidental exposure of documents, browser profiles and SSH keys.
Windows requires extra care. A downloaded ISO may install, but activation and ongoing use depend on Microsoft’s licence terms. Australian Consumer Law provides consumer protections for products and services, but it does not remove the need to obtain a valid operating system licence. Keep proof of purchase and use an evaluation edition only within its stated conditions.
Manage performance, storage and snapshots
A sluggish VM is usually caused by insufficient memory, disabled KVM acceleration, slow storage or an overworked host. Close demanding elementary OS applications, confirm that /dev/kvm exists and reduce the guest’s allocated RAM if the host begins swapping. Solid-state storage makes a noticeable difference, while a nearly full disk can slow both systems.
Virtual disk images commonly grow as data is written. Monitor the host’s free space rather than relying only on the size shown inside the guest. A Linux guest may report plenty of free space while its image file occupies most of the elementary OS partition. Delete unused machines through Boxes and remove their associated disk images when you are certain they are no longer needed.
Snapshots, where available, save a point-in-time state before a risky change. Create one before testing a new driver, system upgrade or development stack, then revert if the experiment fails. A snapshot is not a complete backup: it can depend on the original disk image, consume significant storage and become useless if the host drive fails.
For important guest data, use an external backup or a separate storage service. Australian users should also consider where sensitive information is stored. A VM containing client records, tax documents or health information still needs sensible access controls, encryption and retention practices. The Privacy Act 1988 and sector-specific obligations may apply to organisations handling personal information, even when that information sits inside a virtual machine.
Power use matters as well. A laptop running elementary OS, a browser and a VM will consume more battery and may generate additional heat. On a warm afternoon in Perth or Adelaide, sustained virtualisation can make fans run continuously. Connect the charger for long installations, use a balanced power profile and shut down idle guests rather than leaving them running all day.
Troubleshoot common problems
If Boxes opens but cannot create a machine, first check that the libvirt service is active:
systemctl status libvirtd
On systems using socket activation, the service may appear inactive until requested, which is not always an error. The more useful test is whether Boxes can connect and whether /dev/kvm exists. If permissions are the problem, confirm group membership with:
groups
Then log out and back in after adding the libvirt group. If the guest starts but is extremely slow, look for a disabled virtualisation setting in UEFI. Some corporate computers also restrict firmware changes, in which case an administrator may need to enable the feature.
A black screen can result from an unsuitable display mode, a damaged ISO or a guest that has not finished booting. Re-download the ISO and compare its checksum where available. For Linux guests, try a basic graphics option during installation. For Windows guests, allow extra time for the first boot and provide the storage or network drivers requested by the installer if necessary.
When a guest has no internet connection, check the virtual network setting and test the host connection first. NAT is the best starting point. VPN software, corporate firewalls and captive portals at hotels or cafés can interfere with virtual networking. On an NBN connection shared by several people, heavy guest downloads can also affect video calls and other household traffic.
Use the guest’s own update tools after installation. For a Debian- or Ubuntu-based guest, that might mean sudo apt update followed by upgrades; for Fedora, use its graphical updater or dnf. Keep the host updated through elementary OS and restart when kernel or QEMU packages require it. A tidy arrangement of named VMs, current ISO files and periodic backups prevents most maintenance problems.
With KVM enabled, adequate memory and a properly sized virtual disk, GNOME Boxes turns elementary OS into a practical testing workstation. Start with a lightweight Linux guest, use NAT networking, keep shared folders narrow and treat snapshots as convenience tools rather than backups. The practical rule is simple: allocate only what the guest needs, keep spare resources for elementary OS, and shut down or delete each VM when its experiment is finished.
