Child pages
  • Running a Virtual Machine on Linux or Windows
Skip to end of metadata
Go to start of metadata

Running a VM on a Linux system

If you are using a Linux workstation within the Luddy School of Informatics, Computing, and Engineering and want to run another operating system, one option is to run it as a Virtual Machine.  When running a Virtual Machine, you must still adhere to some basic security requirements, including:

  • Use only current operating systems that are fully supported and receiving security updates.
  • Configure the system to obtain all security patches automatically
  • Use anti-virus software, where possible
  • You must use Network Address Translation (NAT) networking.

Here is the procedure for setting this up:

  1. Verify Workstation Capability - We recommend that you do not run VMs on linux systems with less than 8GB of memory and you need to make sure that the CPU supports virtualization and that it is enabled in the bios.  Please submit a service request if you are unsure of your workstation capability.
  2. Request VirtualBox or VMware Installation - We will install the VirtualBox virtualization software on your workstation so please submit a service request asking us to install VirtualBox.  In your request, please include the name and IU tag number of the workstation you are using.  Alternatively, you can get a VMware Workstation license at no cost per the KB page What free and discounted software is available?.
  3. Add to Group vboxusers - If you elect to use VirtualBox, we will add you to the vboxusers group so you have all the permissions you need to run VMs.  You may need to log out and back in again before you will appear in this group.  You can verify that this is set up by running the "groups" command at a terminal window and making sure that vboxusers appears in the list.  If it does not, please submit a service request asking us to add you to this group.
  4. Local Disk Space - You are advised not to place your VM disk image in your network mounted home directory.  This will give less than optimal performance and you are likely to run out of space with your limited disk quota.  Instead, we will create a directory for your use on the local disk, typically /home/username.  Please note that this local /home filesystem lives on the local workstation drive.  As a result, it is not backed up in any way so you are responsible for backing up any critical files you have in the VM.  In addition, the /home filesystem is only accessible from this one workstation and not over the network on other systems.
  5. Windows Installation Media and License - If you want to run Windows, you will need the media and a license.  Please submit a service request asking for help.
  6. VirtualBox Configuration - You will first need to change the default Virtual Machine Folder, which is where the VM disk images are stored.  The default is a "VirtualBox VMs" folder in your default, network-mounted home directory on the RHEL Unified workstations.  You should change that to be under the local /home/username folder (eg. /home/username/VirtualBox VMs) by starting virtualbox and going to File > General > Default Machine Folder.
  7. Virtual Machine Disk Image Creation - Once you have VirtualBox installed and configured and you have the Windows media and license, you are ready to create your VM.  Just run virtualbox and click on the New icon and answer the questions to create the virtual disk image.  We recommend using dynamic allocation of the VM space.
  8. OS Installation - Once the VM is created, you now need to install the OS.   If you have downloaded an .iso file you want to boot from, you can specify that by going to Settings > Storage > Optical Drive > Click the Disk pulldown > Choose Virtual Optical Disk File.  Browse to the iso file to attach.  Then, just power on the VM to boot from it.
  9. OS Configuration - Once you have the OS installed, it will be up to you to manage the installation.  You should be able to install the software you need, manage accounts, etc.  If you have trouble with any of this and need help, please submit a service request and we will try to help.
  10. VirtualBox Extension Pack Installation - Please note that while the base VirtualBox package is free for any use the Extension Pack is not.  The Extension Pack provides additional functionality (including USB port access) and is covered by a license that is described in the VirtualBoxLicensing: Frequently Asked Questions.  If your use falls under the Personal Use and Evaluation License (PUEL) defined on that page then you can download and install the Extension.  If your use is NOT covered then it has to be licensed so please submit a service request asking for help purchasing a license.

Microsoft Office Notes

If you want to install additional Microsoft software on your VM, there are many products available via the Microsoft Imagine site where you downloaded the Windows OS.  Unfortunately, one notable exception is that Microsoft Office is not available via Microsoft Imagine.  We can help you get a license to run Microsoft Office (please submit a service request) but wanted to mention 2 alternatives that may meet your needs without having to install Microsoft Office in your VM.

  • IUanyWare - The IUanyWare system allows you to run various version of the Office tools (along with lots of other Windows software) as described in the KB page What is IUanyWare.  This can be used from your browser in Linux as well as in the Windows VM so there is no need to even be running a VM to use this.
  • Box for Office Online - You can use Office tools (Word, Excel, Powerpoint) via a web browser as described in the KB page Box for Office Online.  This is an extremely handy way to create and edit Office files from any web browser and using any operating system.

Running a VM on a Windows system

The process for setting up a VM on a Windows system is similar to the above section in terms of the security considerations and setup.  You can submit a service request to have VirtualBox or VMware Workstation installed on your Luddy-managed Windows workstations.

There are some configuration changes required on recent builds of Windows 10 needed to run VMs on Windows 10.  These are listed here for reference and these changes can be made by Luddy IT staff when VirtualBox or VMware Workstation is installed on your system:

Virtualization Support/Virtualization: Enable Intel Virtualization Technology
Virtualization Support/VT for Direct I/O: Enable VT for Direct I/O

Regedit (reboot required):
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard – EnableVirtulizationBasedSecurity = 0
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\CredentialGuard – Enabled = 0

Run in CMD as Admin:
bcdedit /set hypervisorlaunchtype off

Windows Features:
Uncheck Hyper-V

Settings in Virtual Box:
System/Acceleration -  Paravirtualization Interface: Default
System/Acceleration -  Hardware Virtualization: Enable VT-x/AMD-V Checked
System/Motherboard – Extended Features: Enable EFI (special OSes only) Checked