Run Other Operating Systems Safely with VirtualBox on elementary OS
Virtual machines give elementary OS users a convenient way to explore another operating system without replacing the system already installed on a laptop or desktop. VirtualBox creates a self-contained computer inside a window, allowing you to test Linux distributions, older releases, development builds, and some Windows software environments while keeping your everyday files separate.
This is useful for checking an application before installing it on your main system, learning another desktop interface, or creating a temporary environment for a tutorial. A virtual machine is also less disruptive than dual booting: there is no repartitioning, boot-menu maintenance, or need to restart the computer each time you change systems.
Performance depends on the hardware available to the host. A modern computer with virtualisation support, 8 GB or more of memory, and plenty of SSD space will provide a much smoother experience than an older machine. On an NBN connection in Brisbane, Melbourne, or Perth, downloading several ISO images may still consume a substantial amount of data, so it is sensible to remove images and unused virtual machines when testing is finished.
Check the Computer Before Installation
VirtualBox runs on elementary OS because the distribution uses an Ubuntu-compatible base and Linux kernel. Before installing it, check the host computer’s memory, storage, and processor virtualisation settings. Open System Settings and review the available storage, then run this command in Terminal:
free -h
df -h
lscpu | grep -i virtualization
The first command shows memory, the second shows free disk space, and the third looks for AMD-V or Intel VT-x support. If the final command produces no useful result, virtualisation may be disabled in UEFI firmware, or the processor may be too old to support it. Firmware menus vary by manufacturer; settings are commonly called Intel Virtualization Technology, VT-x, SVM, or AMD-V.
A virtual machine needs memory and processor time taken from elementary OS while it is running. For a lightweight Linux guest, 2 GB of RAM and two virtual CPUs may be adequate. A current desktop Linux distribution is more comfortable with 4 GB and two or four virtual CPUs. A Windows guest generally needs more memory and storage, and its licence requirements remain separate from VirtualBox.
Leave enough resources for the host desktop. On a computer with 8 GB of RAM, allocating 4 GB to a guest can make elementary OS feel sluggish, especially with a browser, music player, and several documents open. SSD storage also matters: a dynamically expanding virtual disk saves space initially, but the file can eventually grow to its configured maximum.
Install VirtualBox from the Ubuntu Repositories
The simplest installation method uses the packages provided through the repositories configured for elementary OS. First refresh the package information and install the main application:
sudo apt update
sudo apt install virtualbox
Enter your account password when requested. Linux does not display characters while a password is being typed, which is normal. After installation, open the Applications menu and search for VirtualBox, or launch it with:
virtualbox
The repository version is usually the best starting point because it integrates with the distribution’s package management and receives updates through the normal system update process. It may not be the newest VirtualBox release, but compatibility and uncomplicated maintenance are often more valuable than having every new feature immediately.
You can confirm the installed version with:
VBoxManage --version
If the package manager reports that no installation candidate is available, check that the standard Ubuntu-compatible repositories are enabled and that elementary OS can reach them. A failed apt update should be fixed before attempting the installation again. Common causes include an interrupted update, an incorrect repository entry, or a temporary network or mirror problem.
VirtualBox includes kernel modules that allow the application to communicate with the Linux host. If a kernel update occurs, those modules may be rebuilt automatically. Restarting elementary OS after the first installation and after major kernel updates can help ensure that the correct modules are loaded.
Add the VirtualBox Extension Pack Carefully
The main VirtualBox package supplies the virtual machine manager, virtual storage controllers, networking, display support, and USB functionality. Oracle’s Extension Pack adds features such as USB 2.0 and USB 3.0 support, virtual disk encryption, remote display capabilities, and network boot improvements. It is optional for many basic testing tasks.
The Extension Pack must match the installed VirtualBox version. Downloading an unrelated file from a search result can create version conflicts or expose the computer to malware. Use the official VirtualBox download page, select the Extension Pack matching the version shown by VBoxManage --version, and open the downloaded file with VirtualBox. It can also be installed from Tools, then Extension Pack Manager, depending on the application version.
Read the licence before accepting it. Oracle distributes the Extension Pack under a separate licence from the open-source VirtualBox base package. Its permitted use depends on the circumstances, particularly for commercial, organisational, or larger-scale deployment. Australian users should also consider how the software is being used at work or in a training business rather than assuming that personal use rules apply everywhere.
The Extension Pack is not required to boot an Ubuntu, Fedora, Debian, or elementary OS guest. If your purpose is simply testing an ISO, leave it out until a specific feature requires it. This keeps the setup smaller and avoids an additional licensing component.
Create a Virtual Machine from an ISO
Download the guest operating system’s ISO image from its official website and save it in a clearly named folder, such as ~/Downloads/iso. Verify its checksum when the project publishes one. A SHA-256 check helps detect a damaged download or an altered file:
sha256sum ~/Downloads/iso/example-linux.iso
Compare the displayed value with the checksum listed by the operating system project. Some Australian users rely on local university or community mirrors to improve download speeds, but the checksum should still come from the project’s official release information.
Open VirtualBox and select New. Give the machine a descriptive name, choose the guest operating system type and version, and select the downloaded ISO when prompted. Automatic installation options may appear for common systems. These can save time, but manual installation is preferable when you want to choose partitions, user accounts, locale, or keyboard layout yourself.
Allocate memory conservatively, then create a virtual hard disk. A dynamically allocated disk is suitable for most experiments. Choose VDI unless you have a specific reason to use another format, set a practical maximum size, and store the file on a drive with sufficient free space. A 25 GB disk may suit a lightweight Linux test, while a full desktop guest or development environment may need 40 GB or more.
Before starting, open Settings and review System, Display, Storage, and Network. Enable two virtual CPUs if the host has enough processor capacity, give the guest 64 MB or 128 MB of video memory, and enable 3D acceleration only when the guest supports it reliably. For a first test, the default NAT network mode is usually safest because the guest can access the internet through the host without appearing as a separate device on the local network.
Install and Operate the Guest System
Start the virtual machine and follow the guest operating system’s installer. The guest sees virtual hardware rather than the physical disk in the computer, so selecting the virtual disk for installation will not normally alter the elementary OS installation. Read each installer screen carefully, particularly if you attach any real drives or change storage settings.
Use an Australian keyboard layout when appropriate, especially on laptops with symbols that differ between US and Australian keyboards. Set the time zone to an Australian city such as Sydney, Melbourne, Brisbane, Adelaide, Darwin, or Perth when the guest asks for a location. Correct regional settings affect dates, currency, keyboard behaviour, and scheduled tasks.
Once the guest reaches its desktop, install its updates and test the applications that motivated the experiment. The VirtualBox window provides controls for pausing, restarting, shutting down, and sending keyboard shortcuts to the guest. The Input menu can help release the mouse pointer or adjust how the host and guest share the keyboard.
A saved state suspends the guest much like closing a laptop lid, while Power Off is equivalent to abruptly cutting electricity. Use the guest’s own shutdown command whenever possible. Sudden power-off can damage its virtual filesystem just as a power cut can damage a physical installation. This matters in homes where a desktop may be switched off at the wall each evening to manage electricity use.
Improve Integration and Keep Tests Safe
For a better desktop experience, install Guest Additions inside the guest operating system. These drivers can provide improved display resizing, a smoother mouse, shared clipboard support, and shared folders. The installation process differs between Linux and Windows guests, and some Linux distributions package their own version. Install the additions only when needed, since mismatched versions can cause display or kernel-module problems.
Shared folders are convenient for moving test files between elementary OS and the guest, but they reduce isolation. Do not share your home directory by default. Create a dedicated folder containing only the files required for the experiment, and avoid giving an untrusted guest write access to important host data. Clipboard sharing deserves similar caution, particularly when testing unknown software or scripts.
Take a snapshot before making a risky change. A snapshot records the virtual machine’s state so you can return to it later, although it is not a complete backup. Snapshots consume storage and may reduce disk performance when kept in a long chain. Delete old snapshots after confirming that the test is no longer needed.
Networking deserves attention when testing servers, malware samples, or unfamiliar services. NAT is a sensible default. Bridged networking places the guest directly on the same network as the host and may expose services to other devices, including routers, smart televisions, and work computers. Host-only networking is useful when the guest must communicate with the host but should not have ordinary internet access.
Keep the guest updated, but remember that a virtual machine is not a security boundary with an absolute guarantee. VirtualBox, elementary OS, and the guest all need security updates. If the guest will store personal or business information, check backup arrangements and licensing obligations. Australian Consumer Law can protect consumers in many software-related purchases, but it does not replace the licence terms or security responsibilities that apply to software used in a business.
When testing is complete, shut down the guest and remove it through VirtualBox’s manager, choosing whether to delete its associated virtual disk. Also remove unused ISO files and snapshots. This can recover many gigabytes, which is useful on compact laptops or systems with expensive storage upgrades. A clean-up routine is especially worthwhile after trying several distributions for a community guide or comparing desktop environments.
VirtualBox turns elementary OS into a practical laboratory for operating systems, configuration experiments, and application compatibility checks. The safest workflow is simple: verify hardware support, install the repository package, use official ISO images, allocate resources carefully, keep networking conservative, and treat snapshots as recovery points rather than backups. The key thing to remember is that a virtual machine is disposable testing space, while the elementary OS installation and the files outside it still deserve the same care as any real computer.
