Installing Virtual DICE

Virtual DICE is distributed in the form of a virtual machine image file. All you really have to do is to copy the image to your computer then open it with VirtualBox. First though, check that the computer has what is needed:

Requirements

• The host computer will need about 50GB of free disk space (to start with, and more as you fill its disk with files) and at least 3GB of free memory.
• The computer should be secure and private to you, since you may well want to enter your DICE account details in order to get access to AFS, and your account details should only be entered on a machine which you know has not been interfered with.
• You will need VirtualBox. VirtualBox is available for Linux, Mac, Windows and Solaris hosts and any of these should be capable of running Virtual DICE, given sufficient hardware resources.
• If your computer is a PC, look in the BIOS settings for Virtualization Support and enable Virtualization Technology and VT For Direct I/O.
• It will be an advantage to install one of our VPN services on your computer.

Downloading

The image file is large, so the easiest way to copy it to your computer may be to connect the computer to a wired connection on the Informatics network then copy an image file directly to your computer.
Another option is to copy the image file to a USB stick or pen drive, then copy it from the drive to your computer.
Downloading over a wireless connection may take a while, but is possible.
Before downloading an image file over broadband, check your provider's fair use policies.
Do not try to use iFile as it cannot currently manage files this large.
However you copy the image file, remember that it is very large, it will take a while to copy, and it will probably be too big for your DICE home directory.

AFS: If you have installed AFS on your computer, copy the Virtual DICE image file from:

/afs/inf.ed.ac.uk/group/mp-unit/virtual_dice/images

Copy vdice.ova and vdice.md5sum to your computer. The Informatics filesystem pages explain how to install an AFS client on your computer.
SSH: If your computer has ssh you could copy the image by typing these commands in a terminal window:

sftp ssh.inf.ed.ac.uk:/afs/inf.ed.ac.uk/group/mp-unit/virtual_dice/images/vdice.ova vdice.ova
sftp ssh.inf.ed.ac.uk:/afs/inf.ed.ac.uk/group/mp-unit/virtual_dice/images/vdice.md5sum vdice.md5sum

Web: Download the image from this link.
Copy vdice.ova and vdice.md5sum to your computer.

Checking the download

After downloading the files, use the MD5 checksum to make sure that the file is not corrupt.
If you are using Linux, check the checksum by typing this command in a terminal window:

/usr/bin/md5sum --check vdice.md5sum

A successful check should output something like

vdice.ova: OK

If you are using Windows, Hashcalc can check md5sums, or try the Microsoft File Checksum Integrity Verifier.

On a Mac, open a Terminal and generate a new checksum, then compare it to the one in the vdice.md5sum file. Generate the checksum like this:

md5 vdice.ova

and see the existing checksum like this:

cat vdice.md5sum

Alternatively, a checksum tool can be installed through popular packaging mechanisms Homebrew or MacPorts with a command such as

$ brew install md5sha1sum

or

$ sudo port install md5sha1sum

Installing and booting

Once the .ova file has been checked, just click it to open it in the normal way, or start VirtualBox and import the file using the Import Appliance menu option. Either way a new virtual machine will appear in VirtualBox. Before starting this virtual machine please make sure that the host computer is connected to the network. This will enable the virtual machine to set its clock to the correct date and time as it starts up. (If you ever need to set the clock after booting, see clocks and time in Virtual DICE.)

The .ova image file only needs to be imported once. To boot Virtual DICE on subsequent occasions, start its virtual machine from within VirtualBox.

The first time you attempt to "start" the image in VirtualBox you may get an error about "USB 2.0" problems. The solution to this is to download the VM VirtualBox Extension Pack from the VirtualBox download page, then install it, then try again.