How to Install VirtualBox on Ubuntu [Beginner’s Tutorial]

Access a guest server; D3D acceleration in Windows guests; VirtualBox on a USB key; Run a native Arch Linux installation. This step-by-step guide shows you how to install Linux inside Windows using VirtualBox. There are several ways to install Linux. You can clean everything. Oracle VM VirtualBox Base Packages - Freely available for Windows, Mac OS X, Linux and Solaris x86 platforms under GPLv2. sudo gpg --dearmor --yes --output /usr/share/keyrings/oracle-virtualboxgpg

The virtualbox linux fingerprint for oracle_vbox_asc is

B9F8 D A F3EF C18D 5CDF A2F6 83C5 AECF Oracle Corporation (VirtualBox archive signing key) <info@www.abbottbuilders.com.au>

To install VirtualBox, do

sudo apt-get update sudo apt-get install virtualbox

Replace by or to install the latest VirtualBox or virtualbox linux.

Virtualbox linux to do when experiencing The following signatures were invalid: BADSIG when refreshing the packages virtualbox linux the repository?

# sudo -s -H # apt-get clean # rm /var/lib/apt/lists/* # rm /var/lib/apt/lists/partial/* # apt-get clean # apt-get update

If you previously added the Oracle key(s) to your default keyring (now considered insecure), remove them again with:

sudo apt-key remove 5CDFA2FCAECF sudo apt-key remove D9CA4B98AB

(As of VirtualBoxthe signing key was changed. The old Sun public key for apt-secure can be downloaded here. Likewise, the Oracle public key for distributions older than Debian 8 and Ubuntu can be downloaded here.)

RPM-based Linux distributions

We provide a yum/dnf-style repository for Oracle Linux/Fedora/RHEL/openSUSE. All .rpm packages are signed. The Oracle public key for rpm can be downloaded here, virtualbox linux. You can add this key (not normally necessary, see below!) with

sudo rpm --import oracle_www.abbottbuilders.com.au

or combine downloading and registering: virtualbox linux -q www.abbottbuilders.com.au -O- while read -r file; do line=$(grep -e "type\=\"HardDisk\"" -n "$file" VBoxManage convertfromraw stdin www.abbottbuilders.com.au $(( $sectnum * ))

We need to display the size in byte, will convert the sector numbers to bytes.

• Since you created your disk image as root, set the right ownership to the virtual disk image: # chown your_user:your_group www.abbottbuilders.com.au

• Create your virtual machine configuration file and use the virtual disk created previously as the main virtual hard disk.

• Try to boot your Windows VM, it may just work, virtualbox linux. First though remove and repair disks from the boot process as it may interfere (and likely will) booting into safe-mode.

• Attempt to boot your Windows virtual machine in safe mode (press the F8 key before the Windows logo shows up) if running into boot issues, read #Fix MBR and Microsoft bootloader, virtualbox linux. In safe-mode, drivers will be installed likely by the Windows plug-and-play detection mechanism view. Additionally, install the VirtualBox Guest Additions via Spotify Premium 8.6.42.671 Crack + License Key Free Download 2021 menu Devices > Insert Guest Additions CD image. If a new disk dialog does not virtualbox linux, navigate to the CD drive and start the installer manually.

• You should finally have a working Windows virtual machine. Do not forget to read the #Known limitations.

• Performance tip: according to VirtualBox manual, SATA controller has a better performance than IDE. If you cannot boot Windows off virtual SATA controller right away, it is probably due to the lack of SATA drivers. Attach virtual disk to IDE controller, create an empty SATA controller and boot the VM - Windows should automatically install SATA drivers virtualbox linux the controller, virtualbox linux. You can then shutdown VM, detach virtual disk from IDE controller and attach it to SATA controller instead.

Fix MBR and Microsoft bootloader

If your Windows virtual machine refuses to boot, you may need to apply the following modifications to your virtual machine.

• Boot a GNU/Live live distribution inside your virtual machine before Windows starts up.

• Remove other partitions entries from the virtual disk MBR. Indeed, since we copied the MBR and only the Windows partition, the entries of the other partitions are still present in the MBR, but the partitions are not available anymore. Use to achieve this for example.

fdisk ''/dev/sda'' Command (m for help): a Partition number ('''', default ''3''): ''1''

• Write the updated partition table to the disk (this will recreate the MBR) using the command inside .

# testdisk > Disk /dev/sda > [Proceed] > [Intel] Intel/PC partition > [MBR Code] Write TestDisk MBR to first sector > Write a new copy of MBR code to first sector? (Y/n) > Y > Write a new copy of MBR code, confirm? (Y/N) > A new copy of MBR code has been written. You have to reboot for the change to take effect. > [OK]

• With the new MBR and updated virtualbox linux table, your Windows virtual machine should be able to boot. If you are still encountering issues, boot your Windows recovery disk virtualbox linux on of the previous step, and inside your Windows RE environment, execute the commands described here.

Known limitations

• Your virtual machine can sometimes hang and overrun your RAM, this can be caused by conflicting drivers still installed inside your Windows virtual machine. Good luck to find them!
• Additional software expecting a given driver beneath may either not be disabled/uninstalled or needs to be uninstalled first as the drivers that are no longer available.
• Your Windows installation must reside on the first partition for the above process to work. If this requirement is not met, the process might be achieved too, but this had not been tested. This will require either copying the MBR and editing in hexadecimal see VirtualBox: booting cloned disk or will require to fix the partition table manually or by repairing Windows with the recovery disk you created in a previous step. Let us consider our Windows installation on the second partition; we will copy the MBR, then the second partition where to the disk image. needs the total number of bytes that will be written: calculated thanks virtualbox linux the size of the MBR (the start of the first partition) plus the size of the second (Windows) partition, virtualbox linux. .

Note: The technique outlined in this section only applies to UEFI systems.

In some cases, it is useful to be able to dual boot with Windowsand access the partition in a virtual machine. This process is significantly different from #Move a native Windows installation to a virtual machine in several ways:

• The Windows partition is not copied to a virtual disk image, virtualbox linux. Instead, a raw VMDK file is created;
• Changes in the VM will be mirrored in the partition, and vice versa;
• OEM licenses should still be satisfied, since the Windows partition still boots directly on the hardware.

Warning: Some of the commands used here can corrupt either the Windows partition, the Arch Linux partition, or both, virtualbox linux. Use extreme caution when executing commands, virtualbox linux, and double check that they are being run in the correct shell. It would be a good idea to have a backup of the entire drive ready before beginning this process.

Note: Before proceeding be sure to have access to a Windows installation media (such as the Windows 11 ISO).

Creating the virtual machine

A VirtualBox virtual machine must be manually created. As of now do not add any storage device any disk to the virtual machine, it will be done manually later, virtualbox linux.

Configure the virtual machine with the following settings (settings panel can be opened by clicking the "Settings" button in the main toolbar):

• View: System:
  • Tab: Motherboard:
    • mark Enable I/O APIC;
    • mark Enable EFI;
    • mark Hardware Clock in UTC Time if is your case.
  • Tab: Processor:
    • mark Enable PAE/NX;
    • mark Enable VT-x/AMD-V;
  • Tab: Acceleration:
    • Chose the paravirtualization interface Hyper-V from the drop down menu;
    • mark Enable Nested Paging.

Optionally you can enable also the following settings:

• View: Display
  • Tab: Screen
    • mark Enable 3D Acceleration. Note that it could cause glitches.

Note: The Hyper-V setting is not required in order for the system to operate correctly, but it may help avoid licensing virtualbox linux virtual machine disks

To access the Windows partitions, create a raw VMDK file pointing to the relevant Windows partitions (root privileges are required to read disk partition table):

# VBoxManage internalcommands createrawvmdk -filename VM_FOLDER/www.abbottbuilders.com.au -rawdisk WINDOWS_DISK -partitions WINDOWS_RESERVED_PARTITION_NUMBER,WINDOWS_BASIC_DATA_PARTITION_NUMBER -relative

Replace capitalized virtualbox linux strings as follow:

• with the path of the virtual machine folder (usually a subfolder of ;
• must be replaced with the block device containing all the Windows partitions (e.g.: or );
• must be replaced with the number of partition labeled "Microsoft reserved partition" (e.g.: if the partition is the the number will be );
• must virtualbox linux replaced with the partition containing the Windows installation (e.g.: if the partition is the the number will be );

Example:

$ sudo VBoxManage internalcommands createrawvmdk -filename "/home/user/VirtualBox VMs/www.abbottbuilders.com.au" -rawdisk /dev/nvme0n1 -partitions 2,3 -relative

The command will also create an extra file inside the virtual machine folder, "www.abbottbuilders.com.au", that will be just ignored.

Note: must be re-created if the partition table is changed.

Now change the virtual disk owner to give access the user and group running VirtualBox.

# chown VIRTUALBOX_RUNNING_USER:VIRTUALBOX_RUNNING_GROUP VM_FOLDER/www.abbottbuilders.com.au VM_FOLDER/www.abbottbuilders.com.au

Replace and with the user and the group that will run VirtualBox, which most likely will be your user.

Allowing VirtualBox to read physical partitions

VirtualBox must have raw disk access in order to run a Windows partition. Normally, this would require VirtualBox to be run with full root privileges, but more elegant options are available.

Higher virtualbox linux option: using a dedicated virtualbox linux for the Windows partitions

Here udev is configured to restrict the access to partitions Windows partitions to the vboxusers group, and then the user running VirtualBox is added to the group.

Assigning the disks to the vboxusers group can be done automatically by creating the following file:

/etc/udev/rules.d/www.abbottbuilders.com.au# # Rules to give VirtualBox users raw access to Windows partitions # # Microsoft Reserved partition SUBSYSTEM=="block", ENV{ID_PART_ENTRY_TYPE}=="e3c9eb5c-4dbd-f92dfae", GROUP="vboxusers" # Windows partition SUBSYSTEM=="block", ENV{ID_PART_ENTRY_TYPE}=="ebd0a0a2-b9ecb6bc7", GROUP="vboxusers" # # Rules to give VirtualBox users raw access to Windows disk # # sdb ENV{ID_PART_TABLE_UUID}=="WINDOWS_DISK_ID_PART_TABLE_UUID", GROUP="vboxusers"

must be replaced with the value obtained from (replace with the disk containing Windows partitions). The UUIDs in these rules correspond to particular GPT partition types while the other capitalized strings are supposed to be written that way, so those does not have to be replaced.

Then tge user running VirtualBox must be added to the vboxusers group, virtualbox linux. This can be done with the following command:

# usermod -aG vboxusers VIRTUALBOX_RUNNING_USER

Replace and with the user that will run VirtualBox, which most likely will be your user.

Lower security option: using 'disk' group

To be able to add the vmdk file in Virtualbox Virtual Media Manager without running VirtualBox as root, the user running VirtualBox need to be in and groups.

# usermod -aG disk,vboxusers VIRTUALBOX_RUNNING_USER

Replace and with the user that will run VirtualBox, which most likely will be your user.

Warning: Be aware of the potential security implications of this edit, as you are giving your user account full read-write access all storage virtualbox linux owned by the disk group.

Setting up a separate ESP partition

Virtual machine EFI boot files will refer to different disks than the ones in the physical EFI partition, so VirtualBox must not make use of the latter but instead of a EFI partition inside a dedicated virtual disk. This disk can be created with the following command:

$ VBoxManage createmedium disk --filename VM_FOLDER/www.abbottbuilders.com.au --size --format VMDK

Replace with the folder containing the virtual machine being built.

Adding virtual disks to the virtual machine

Configure the virtual machine storage devices (Settings panel - Storage) as following:

• add as a SATA hard virtualbox linux attached to the "SATA Port 0";
• add as a SATA hard disk attached to the "SATA Port 1";
• mount Windows installation iso into the virtual optical drive .

Configuring the virtual UEFI firmware and creating Windows boot files

Now start the virtual machine and it should automatically boot from Windows installation disk. After choosing the installation locales click on the "Repair your computer" link, virtualbox linux, then choose "Troubleshoot" and then " Command Prompt" in order to launch a command prompt from the install media.

Enter the following commands to create a new GPT table in the www.abbottbuilders.com.au disk and install the Windows boot loader onto it using configuration from the existing Windows partition:

Open Diskpart:

X:\ diskpart

List all disks identified by the system:

DISKPART> list disk

The www.abbottbuilders.com.au disk should be labeled as due to the fact that was attached to the SATA port 0, ~MB in size and unpartitioned, virtualbox linux. The disk should be labeled as ; note that the column "Size" displays the disk size, not the partition one.

Select the www.abbottbuilders.com.au disk:

DISKPART> select Disk 0

Now create a GPT partition table, a UEFI virtualbox linux big as the whole disk and assign to it a label and drive letter:

DISKPART> clean DISKPART> convert gpt DISKPART> create partition efi size= DISKPART> format quick fs=fat32 label="System" DISKPART> assign letter="S"

Check that the partiton has been correctly created:

DISKPART> list volume

Our newly created UEFI boot partition will be labeled as "SYSTEM" with letter as "S".

Take note of the Windows installation volume letter because it will be used in next steps. Usually its but it could be different: you can infer it from its label and its size. The size is the same as the Windows installation partition size on your physical hard disk, virtualbox linux.

Exit diskpart:

DISKPART> exit

Install the Windows boot loader into the EFI partition.

D: cd Windows\System32 bcdboot D:\Windows /s S: /f UEFI

Now close the command prompt, power off the virtual machine and detach the Windows installation disk (from "Preferences > Devices" remove the optical disk). The virtual machine should now boot from the newly installed boot partition and load the physical Windows installation. It may show some UEFI related errors on the top of the virtual machine window and the first boot may take a while, but if everything has been done correctly you will be able to access your windows installation.

Run an entire physical disk in Virtualbox

Note: You may refer to Virtualbox official documentation Using a Raw Host Hard Disk From a Guest.

This works virtualbox linux same way as #Run a native Windows installation inside VirtualBox but the vmdk will contain the entire disk rather than one partion, and so you will not need to create a separate ESP or MBR partition as the one in the physical disk will be used.

Create the raw disk:

# VBoxManage internalcommands createrawvmdk -filename /path/to/www.abbottbuilders.com.au -rawdisk /dev/sdb

Then follow the same method as in #Run a native Windows installation inside VirtualBox for the configuration and virtual disk attachement.

Set guest starting resolution

You can change the BIOS/UEFI booting resolution using tool. For example:

$ VBoxManage setextradata "Your Virtual Machine Name" "VBoxInternal2/EfiGraphicsResolution" "x"

Recommended resolutions are x, x, x, virtualbox linux, x, x, virtualbox linux, x, x, x

SSH from host to guest

The network tab of the virtual machine settings contains, in "Advanced", a tool to create port forwarding. It is possible to use it to forward the Guest ssh port to a Host port, e.g. &#;:

user@host$ ssh -p $USER@localhost

will establish a connection from Host to Guest, virtualbox linux.

SSHFS as alternative to the shared folder

Using this port forwarding and sshfs, it is straightforward to mount the Guest filesystem onto the Host one:

user@host$ sshfs -p $USER@localhost:$HOME ~/shared_folder

and then transfer files between both.

Troubleshooting

Keyboard and mouse are locked into virtual machine

This means your virtual machine has captured the input of your keyboard and your mouse. Simply press the right key and your input should control your host again.

To control transparently your virtualbox linux machine with your mouse going back and forth your host, without having to press any key, and thus have a seamless integration, install the guest additions inside the guest. Read from VirtualBox/Install Arch Linux as a guest#Install the Guest Additions if your guest is Arch Linux, virtualbox linux, otherwise read the official VirtualBox help.

No bit OS client options

When launching a VM client, and no bit options are available, make sure your Optimization Software virtualization capabilities (usually named ) are enabled in the BIOS.

If virtualbox linux are using a Windows host, you may need to disable Hyper-V, as it prevents VirtualBox from using VT-x. [5]

VirtualBox GUI does not match host GTK theme

See Uniform look for Qt and GTK applications for information about theming Qt-based applications like VirtualBox.

Cannot send Ctrl+Alt+Fn to guest

Your guest operating system is a GNU/Linux distribution and you want to open a new TTY shell by hitting or exit your current X session with. If you type these keyboard shortcuts without any adaptation, virtualbox linux, the guest will not receive any input and the host (if it is a GNU/Linux distribution too) will intercept these shortcut keys. To send to the guest for example, simply hit your Host Key (usually the right key) and press simultaneously.

USB subsystem not virtualbox linux user must be in the group and you need to install the extension pack if you want USB 2 support. Then you will be able to enable USB 2 in the VM settings and add one or several filters for the devices you want to access from the guest OS.

If does not show any USB devices even if run as root, make sure that there is no old udev rules (from VirtualBox 4.x) in. VirtualBox installs udev rules to. You can use command like to determine if the udev rule file is outdated.

Sometimes, on old Linux hosts, the USB subsystem is not auto-detected resulting in an error or in a not visible USB drive on the host, even when the user is in the vboxusers group. This problem is due to virtualbox linux fact that VirtualBox switched from usbfs to sysfs in version If the host does not understand this change, you can revert to the old behaviour by defining the following environment variable in any file that is sourced by your shell (e.g, virtualbox linux. your if you are using bash):

~/.bashrcVBOX_USB=usbfs

Then make sure, the environment has been made aware of this change (reconnect, source the file manually, launch a new shell instance or reboot).

Also make sure that your user is a member of the group.

USB modem not working on host

If you have a USB modem which is being used by the guest OS, killing the guest OS can cause the modem to become unusable by the host system. Killing and restarting should fix this problem, virtualbox linux.

USB device crashes guest

If attaching a USB device to the guest causes a crash or any other erroneous behavior, try switching the USB controller from USB 2 (EHCI) to USB 3 (xHCI) or vice versa.

Host freezes on virtual machine start

Generally, such issues are observed after upgrading VirtualBox or Virtualbox linux kernel. Downgrading them to the previous versions of theirs might solve the problem, virtualbox linux.

Analog microphone not working

If the audio input from an analog microphone is working correctly on the host, but no sound seems to get through to the guest, despite the microphone device apparently being detected normally, installing a sound server such as PulseAudio on the host might fix the problem.

If after installing PulseAudio the microphone still refuses to work, setting Host Audio Driver (under VirtualBox > Machine > Settings > Audio) to ALSA Audio Driver might help.

Problems with images converted to ISO

Some image formats cannot be virtualbox linux converted to ISO. For instance, ccd2iso ignores .ccd and .sub files, which can result in disk images with broken files.

In this case, you will either have to use CDemu for Linux inside VirtualBox or any other utility used to mount disk images.

Failed to create the host-only network interface

Make sure all required kernel modules are loaded. See #Load the VirtualBox kernel modules.

If all required kernel modules are loaded and you are still unable to create the host-only adapter, navigate to File > Host Network Manager and click the Create button to add the network interface.

Failed to insert module

When you get the following error when trying to load modules:

Failed to insert 'vboxdrv': Required key not available

Sign your modules or disable in your kernel config, virtualbox linux.

VBOX_E_INVALID_OBJECT_STATE (0x80BB)

This can occur if a VM is exited ungracefully. Run the following command:

$ VBoxManage controlvm virtual_machine_name poweroff

NS_ERROR_FAILURE and missing menu items

This error might appear if virtualbox-ext-oracle^AUR has not been updated and becomes incompatible with a newly released virtualbox version

This error also happens sometimes when selecting QCOW/QCOW2/QED disk format when creating a new virtual disk.

If you encounter this message the first time you start the virtual machine:

Failed to open a session for the virtual machine debian. Could not open the medium '/home//VirtualBox VMs/debian/www.abbottbuilders.com.au'. QCow: Reading the L1 table for image '/home//VirtualBox VMs/debian/www.abbottbuilders.com.au' failed (VERR_EOF). VD: error VERR_EOF opening image file '/home//VirtualBox VMs/debian/www.abbottbuilders.com.au' (VERR_EOF). Result Code: NS_ERROR_FAILURE (0x) Component: Medium

Exit VirtualBox, delete all files of the new machine and from VirtualBox configuration file remove the last line in menu (or the offending machine you are creating):

~/.config/VirtualBox/www.abbottbuilders.com.au <MachineRegistry> <MachineEntry uuid="{}" src="/home/void/VirtualBox VMs/debian/www.abbottbuilders.com.au"/> <MachineEntry uuid="{}" src="/home/void/VirtualBox VMs/ubuntu/www.abbottbuilders.com.au"/> <MachineEntry uuid="{}" src="/home/void/VirtualBox VMs/lastvmcausingproblems/www.abbottbuilders.com.au"/> </MachineRegistry>

OpenBSD unusable when virtualisation instructions unavailable

While OpenBSD is reported to work fine on other hypervisors without virtualisation instructions (VT-x AMD-V) enabled, virtualbox linux, an OpenBSD virtual machine running on VirtualBox without these instructions will be unusable, manifesting with a bunch of segmentation faults. Starting VirtualBox with the -norawr0 argument may solve the problem. You can do it like this:

$ VBoxSDL -norawr0 -vm name_of_OpenBSD_VM

Windows: "The specified path does not exist. Check the path and then try again."

This error message may appear when running an file which requires administrator privileges from a shared folder in windows guests. [6]

As a workaround, copy the file to the virtual drive or use UNC paths (). See [7] for more information.

Windows 8.x error code 0xC4

If you get this error code while booting, even if you choose OS Type Win 8, try to enable the CPU instruction:

$ vboxmanage setextradata virtual_machine_name VBoxInternal/CPUM/CMPXCHG16B 1

Windows 8, or 10 fails to install, boot or has error "ERR_DISK_FULL"

Update the VM's settings by going to Settings > Storage > Controller:SATA and check Use Host I/O Cache.

WinXP: Bit-depth cannot be greater than 16

If you are running at bit color depth, then the icons may appear fuzzy/choppy. However, upon attempting to change the color depth to a higher level, the system may restrict you to a lower resolution or simply not enable you to change the depth at all, virtualbox linux. To fix this, run in Windows and add the following key to the Windows XP VM's registry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services] "ColorDepth"=dword

Then update the color virtualbox linux in the "desktop properties" window. If nothing happens, force the screen to redraw through some method (i.e. to redraw/enter full screen).

Windows: Screen flicker if 3D acceleration enabled

VirtualBox > has a regression in which Windows guests with 3D acceleration flicker, virtualbox linux. Since r a patch has been implemented to recognize an environment variable setting, launch VirtualBox like this:

$ CR_RENDER_FORCE_PRESENT_MAIN_THREAD=0 VirtualBox

Make sure no VirtualBox services are still running. See VirtualBox bug

Cannot launch VirtualBox with Wayland: Segmentation fault

This problem is caused by Qt detecting Wayland (e.g., virtualbox linux, if ), while VirtualBox does not work on Wayland yet. See FS# and the upstream bug.

The Qt platform detection can be disable and X11 forced over Wayland by setting the environment variable. To not affect the other Qt applications (which usually work well with Wayland), should only be set when launching VirtualBox.

If starting through the desktop entry, follow the instructions in Desktop entries#Modify environment variables and change the lines starting with to. If starting from the shell, virtualbox linux, alias (Bash#Aliases) to.

Note: If you have mouse or keyboard related issue in Wayland, you can try above setting too.

Random freezing in guests with intel graphics

With Intel cpu and graphics, allocating more processors for the guest can lower render performance, thus cause random freezing. Allocating less or one processor can help.

Unable to view desktop in fullscreen mode

Disable the Mini Toolbar by selecting Machine > Settings, virtualbox linux, select virtualbox linux User Interface tab and uncheck the Mini Toolbar checkbox

Random crashes with Windows 10 guest OS with Intel Tiger Lake chipset

Disable split lock detection by adding to the kernel parameters.

Details are described in VirtualBox's Ticket #

Freeze during virtual machine startup with 11th generation Intel CPU

If the message and appears in the journal you can try adding as a kernel parameter. Seems to be linked to FS#

See also