Set up Windows Virtual Machine for VirtualBox - TUXEDO Computers

  ATTENTION: To use our store you have to activate JavaScript and deactivate script blockers!  
Thank you for your understanding!

Set up Windows Virtual Machine for VirtualBox

If you rely on Windows for work or personal use, you can run it in a virtual machine—isolated and privacy-friendly. This guide shows you how to import our preconfigured Windows VM into VirtualBox, using Windows 11 as an example.

Download

After logging into your customer account, you’ll find the prepared virtual machine in the Downloads section—provided that you ordered your device with this option. Due to licensing restrictions, access is only available in this case.

Extracting the Archive

Open your file manager, navigate to the Downloads folder, and extract the file Windows11.tar.xz by right-clicking it and selecting Extract » *Extract here*.

After extraction, you may delete the archive. Then cut the extracted folder using Ctrl + X.

Preparing the Folder Structure

Navigate to your Home folder. If the VirtualBox VMs directory does not exist, create it manually. Paste the previously cut VM folder using Ctrl + V.

Importing the Virtual Machine

Launch VirtualBox using the Tux-key. In the program window, click Add in the upper right corner.

Browse to the VirtualBox VMs folder, select the VM folder (e.g., Windows 11), and open the .vbox file inside.

The VM is now ready to use and can be started by clicking Start. As is common with Windows, you’ll need to go through the setup assistant before the system is fully operational.

Tips and Notes

Workaround for Error: VERR_NO_LOW_MEMORY

In recent versions of VirtualBox, the following error may occur when starting the VM: Out of memory condition when allocating memory with low physical backing (VERR_NO_LOW_MEMORY).

This issue is caused by a known bug that has not yet been resolved. As a temporary workaround, execute the following command before starting the VM:

echo "3" | sudo tee /proc/sys/vm/drop_caches

The VM should then start normally. Please note that this workaround only lasts until the next reboot. A permanent fix requires an update from Oracle—so make sure to keep VirtualBox up to date.