VirtualBox is a general-purpose full virtualizer for hardware. Targeted at server, desktop and embedded use, it is now the only professional quality virtualization solution. It is also Open Source Software. The powerful virtualization product for enterprise as well as home use.
VirtualBox provides are useful for several scenarios: Running multiple operating systems simultaneously. VirtualBox allows you to run more than one operating system at a time.
This way, you can run software written for one operating system on another (for example, Windows software on Linux or a Mac) without having to reboot to use it.
Since you can conﬁgure what kinds of “virtual” hardware should be presented to each such operating system, you can install an old operating system such as DOS or OS/2 even if your real computer’s hardware is no longer supported by that operating system.
Software vendors can use virtual machines to ship entire software conﬁgurations. For example, installing a complete mail server solution on a real machine can be a tedious task.
With VirtualBox, such a complex setup (then often called an “appliance”) can be packed into a virtual machine. Installing and running a mail server becomes as easy as importing such an appliance into VirtualBox.
In order to run VirtualBox on your machine, you need:
- Reasonably powerful x86 hardware. Any recent Intel or AMD processor should do.
- Memory. Depending on what guest operating systems you want to run, you will need at least 512 MB of RAM (but probably more, and the more the better). Basically, you will need whatever your host operating system needs to run comfortably. Plus the amount that the guest operating system needs. So, if you want to run Windows 8.1 on Windows 7, you probably won’t enjoy the experience much with less than 2 GB of RAM. Check the minimum RAM requirements of the guest operating system, they often will refuse to install if it is given less. Sometimes it malfunctions instead. So you’ll need that for the guest alone, plus the memory your operating system normally needs.
- Hard disk space. While VirtualBox itself is very lean (a typical installation will only need about 30 MB of hard disk space), the virtual machines will require fairly huge files on disk to represent their own hard disk storage. So, to install Windows 8, for example, you will need a file that will easily grow to several 10 GB in size.
- A supported host operating system. Presently, we support Windows, many Linux distributions, Mac OS X, Solaris and OpenSolaris. Check the user manual of the VirtualBox version you are using which versions are supported.
- A supported guest operating system. Besides the user manual (see below), up-to-date information is available at “Status: Guest OSes“.
- VMSVGA: fixed VM screen artifacts after restoring from saved state
- Storage: Fixed audio endianness for certain CUE sheet CD/DVD images.
- VBoxHeadless: Running VM will save its state on host shutdown
- VBoxManage: Fix OS detection for Ubuntu 20.10 ISO with unattended install
- Linux Additions: Fixed mouse pointer offsetting issue for VMSVGA graphics adapter in multi-monitor VM setup (6.1.24 regression)
Changes in VirtualBox 6.1.24 (2021-07-21):
- Storage: Fixed starting a VM if a device is attached to a VirtIO SCSI port higher than 30 (bug )
- Storage: Improvement to DVD medium change signaling
- Serial: Fixed a the guest missing interrupts under certain circumstances (6.0 regression)
- Audio: Multiple fixes and enhancements
- Network: Fixed connectivity issue with virtio-net after resuming VM with disconnected link
- Network: Fixed UDP GSO fragmentation issue with missing 8 bytes of payload at the end of the first fragment
- API: Fixed VM configuration for recent Windows Server versions
- Extension Pack: Fixed issues with USB webcam pass-through on Linux
- Host and guest driver: Fix small memory leak
- Linux host and guest: Support kernel version 5.13
- Linux host and guest: Introduce support for SUSE SLES/SLED 15 SP3 kernels
- Linux host: Installer will not attempt to build kernel modules if system already has them installed and modules versions match current version
- Windows host: Fix DLL signature validation to work better with an invalid certificate
- Guest Additions: Fixed crash on using shared clipboard
- Linux Guest Additions: Introduce support for Ubuntu specific kernels
- Solaris guest: Increased default memory and disk sizes
- EFI: Support network booting with the E1000 network controller emulation
- EFI: Stability improvements
Changes in VirtualBox 6.1.22 (2021-04-29):
- VMM: Improved performance of 64-bit Windows and Solaris guests when Hyper-V is used on recent Windows 10 hosts
- VMM: Fixed frequent crashes of 64-bit Windows Vista and Server 2003 guests when Hyper-V is used
- GUI: Fixed regression where user was not able to save unset default shortcuts
- Storage: Fixed regression in LsiLogic SAS controller emulation caused VM crash
- Linux Guest Additions: Fixed issue when it was not possible to run executables from mounted share
Changes in VirtualBox 6.1.20 (2021-04-20):
- VMM: Fixed extremely poor VM performance depending on the timing of various actions (regression in 6.1.0)
- VMM: Fixed guest OS hanging under certain circumstances when Hyper-V is present
- VMM: Fixed Guru Meditation error when using a nested hypervisor under certain circumstances
- VMM: Fixed a SMAP related host panic affecting Solaris 11.4 systems with Intel Haswell CPUs or later
- OCI: Add cloud-init support for export to OCI and for OCI instance creation
- GUI: Fixed “Delete all files” leaving behind Logs/VBoxUI.log
- Audio: Multiple fixes and enhancements
- Audio: Fixed detection of duplex audio devices on macOS (5.0 regression;)
- Network: Fixed link status reporting for “not attached” adapters
- Network: Fixed connectivity issues with e1000 in OS/2 guests (6.1.18 regression; bug #20148)
- Network: Fixed VxWorks e1000 driver compatibility issue (bug #20182)
- Network: Fixed GUI checks for port forwarding rules rejecting IPv6 with “Nat Network” (bug #14847)
- DHCP: Don’t crash in the presence of fixed address assignments (bug #20128)
- Serial: Fixed possible VM hang when using the a serial port in disconnected mode (bug #19854)
- Webcam: Fixed interoperability with v4l2loopback and fixed a crash under certain circumstances (bug #20176)
- NVMe: Fixed sporadic Windows VM hang or reboot on high CPU load
- VBoxManage: Allow changing network adapter attachment of a saved VM with “modifyvm”
- vboximg-mount: Fix for argument processing to honor the ‘–root’ option (6.0 regression; bug #20073)
- Linux host and guest: Support kernel versions 5.11 (bug #20198) and 5.12
- Linux host: Maximum MTU size increased to 16110 for host-only adapters on Linux kernels 4.10+ (bug #19122)
- Linux Guest Additions: Fix vboxvideo module compilation for kernel version 5.10.x
- Linux Guest Additions: Fixed kernel module build for RHEL 8.4 beta and CentOS Stream (bug #20289)
Homepage – https://www.virtualbox.org
Currently, Oracle VM VirtualBox runs on the following host operating systems:
Windows hosts (64-bit):
- Windows 7
- Windows 8
- Windows 8.1
- Windows 10 RTM (1507) build 10240
- Windows 10 November Update (1511) build 10586
- Windows 10 Anniversary Update (1607) build 14393
- Windows 10 Creators Update (1703) build 15063
- Windows 10 Fall Creators Update (1709) build 16299
- Windows 10 April 2018 Update (1803) build 17134
- Windows 10 October 2018 Update (1809) build 17763
- Windows Server 2008 R2
- Windows Server 2012
- Windows Server 2012 R2
- Windows Server 2016
- Windows Server 2019
Mac OS X hosts (64-bit):
- 10.12 (Sierra)
- 10.13 (High Sierra)
- 10.14 (Mojave)
Intel hardware is required. See also Chapter 14, Known Limitations.
Linux hosts (64-bit). Includes the following:
- Ubuntu 16.04 LTS, 18.04 LTS and 18.10
- Debian GNU/Linux 9 (“Stretch”)
- Oracle Linux 6 and 7
- Redhat Enterprise Linux 6 and 7
- Fedora 28 and 29
- Gentoo Linux
- SUSE Linux Enterprise server 12 and 15
- openSUSE Leap 42.3 and 15.0
Size: 103 MB