Virtual Machine Technical Supportvirtualbox150

This guide deals primarily with issues related to the VirtualBox hypervisor. Other hypervisors may be used to run our Virtual Machines, such as VMware, KVM, hyper-V, Parallels, but we do not provide technical support for those.
This guide is not intended to provide detailed steps for every item on every operating system. It is meant as a general guide, and you will have to google to find the procedure for your particular operating system and computer model.
Remember this terminology: The host is your computer on which you are running VirtualBox. A guest is a Virtual Machine running on your host that you imported into VirtualBox.
Contents of this support page:

  1. Prepare Computer for VirtualBox
  2. VirtualBox Installation
  3. VirtualBox Virtual Machine Import
  4. Using VirtualBox Virtual Machines
  5. VirtualBox Trouble-Shooting

Prepare Computer for VirtualBox

Here are some common issues to check that can cause VirtualBox and the Virtual Machine to fail entirely or have poor performance:

  • Enable Processor Virtualization: Ensure Virtualization is enabled on your Computer. See the Virtualization Error (VT-d/VT-x or AMD-V) in the Trouble-Shooting section below for instructions.
  • Disable OneDrive, DropBox Sync, iCloud, etc If you are using a data synchronization service, make sure it does not (or at least not frequently) synchronize the folder in which you have VirtualBox import and run the Virtual Machines. This can cause a dramatic fall-off of performance for you entire system as these services try to synchronize these massive files.
  • Sufficient Disk Space: Virtual Machines require a significant amount of Disk space (10 GB or more each). Ensure you have sufficient space on your computer

VirtualBox Installation

Please complete BOTH of these steps to install VirtualBox:

  1. Download and install the latest VirtualBox for your host OS from
  2. Download the VirtualBox Extension Pack from
    Open Preferences… -> Extensions and click the little Add New Package button, then browse to the Extension Pack you just downloaded and follow the instructions
    IMPORTANT: ALL of the SCS Virtual Machines require the Extension Pack which provides critical tools and drivers for the Virtual Machines.

WARNING: It is important to update VirtualBox each term. Older version of VirtualBox are not tested with our newer Virtual Machines. Older Virtual Machines generally+ work fine with newer version of VirtualBox.

VirtualBox Virtual Machine Import

To import one of the SCS Virtual Machines as a guest into VirtualBox (which you already installed using the VirtualBox Installation steps above), follow these steps:

  1. Download the Virtual Machine for your course from our Course Virtual Machines page. This will download the .ova file which – if you are curious – is a compressed tarball of the Virtual Machine exported from VirtualBox
  2. In VirtualBox go to File -> Import Appliance (or press CTRL-I)
  3. In the Appliance Import Window that opens, click the folder icon to browse for the .ova file you just downloaded, then click Next
  4. Do NOT change any of the Appliance Settings, these have already been optimized for most systems
    Click Import
    NOTE: Importing an Appliance can take 5-10 minutes depending on the speed of your computer and the size of the Virtual Machine
  5. When the import is complete, you will see the new Virtual Machine guest in VirtualBox’s guest list.

Using VirtualBox Virtual Machines

Starting a Virtual Machine

To start-up a Virtual Machine guest, simply click on the desired one and click the Start button (or double-click the Virtual Machine). Some of our larger Virtual Machines can take up to a minute to boot up the linux operating system and show you the login screen. It the boot-up is a lot slower, or if the performance when logged into the Virtual Machine Desktop or Shell is poor, then consult the Trouble-Shooting section below.

Using a Virtual Machine

How you use a Virtual Machine will depend on your course, so consult your TAs. Some useful things to know:

  • Run a command with sudo (root) privileges: Open a terminal and type any command with sudo in front to run that command as root.
    Example: sudo apt-get install vim – will install the vim text editor package on an ubuntu linux Virtual Machine
  • Find the IP address of your Host-Only Network connection: Open a terminal and type ifconfig | more – The | more (pronounced “pipe more”) will “pipe” the output of the ifconfig command to the more command which will show the results one page at a time, so it doesn’t scroll by before you see it all.
    If you have a Host-Only Network IP address you will see an IP of (or something similar). Check the Trouble-Shooting section below for more information about the Host-Only Network.

Shutting down a Virtual Machine

When you are done using a Virtual Machine, you need to shut it down properly. This can be done in three ways:

  1. Press the the shut down button found on the desktop, task bar, or task menu of the guest operating system
  2. Open a terminal and type the command: sudo shutdown -h now
  3. In the guest window click Machine (menu) -> ACPI Shutdown – This will simulate the power button being pressed

WARNING: If you shutdown a guest operating system any other way, such as by just pressing the “X” button on the guest window or File (menu) -> Close, this is the same as pulling the power cord out of your desktop computer. This can result in hard drive errors depending on what the guest operating system was doing when you killed it.
NOTE: Some of our VMs can take as much as a minute to shut down depending on what the system was doing, please be patient.

VirtualBox Trouble-Shooting

Once VirtualBox is installed AND the Extension Pack is installed, most of our Virtual Machines should work with no further configuration. However, here are some common errors that may still be experienced. In particular the first two problems below (Extension Pack Missing and Virtualization Error) MUST be resolved in order for SCS Virtual Machines to work!

Other Common Issues Encountered with SCS Virtual Machines: