Installation via virtual machine image is deprecated as of Avalon 6.5. If you're looking for automated installation, please see our documentation on installing Avalon with Docker.

This documentation is for Release 6.x.
For older releases:

These instructions will walk you through the process of downloading, booting, and configuring a CentOS 7.x virtual machine image containing Docker containers of Avalon, Fedora, Red5 and Opencast Matterhorn, with additional instructions on loaded sample audio and video content.

1. Getting a Virtualization Product

The Avalon VM is distributed as an Open Virtualization Appliance which should be compatible with these Virtual machine products:

Other virtualization products may be used but they will require manually converting the OVA file into something useful.

2. Getting the Avalon Virtual Machine Image

The Avalon VM file is located at and is roughly 2GB.  Due to the size, it may take some time to download.

3. Importing the Avalon VM Image

The OVA file currently contains release 6.4.2

Each virtualization product has different methods for using a VM appliance.  The tested methods are below.  If you use a product which is not listed, please contact us with usage instructions and we will add them here.


Users on Apple hardware may get the following error screen when starting the VM:

If you receive this dialog, click the Change Network Settings button followed by the OK in the following dialog to resolve the issue.

VMware Player

Libvirt's Virtual Machine Manager

Virtual Machine Manager is an open source GUI front end to QEMU, KVM and other Linux-based virtualization products.  It comes with Fedora Linux and other distributions.  It doesn't directly support OVA files so manual conversion is required.

Generic VM Product

A generic VM product may be set up using these settings:

Notes for ALL Virtualization Products

Disk Usage

The disk image in the OVA package is dynamically-allocated with a maximum size of 500G.  While the disk image may only use a few gigabytes when it is first used, it will grow as more data is placed into the VM.  Most VMs behave unpredictably when the host system doesn't have enough disk space to satisfy guest OS requests.  Monitor the disk usage closely.

4. Using the Avalon VM

Once the VM has rebooted and the login screen has appeared, the Avalon system is ready to use. 

  1. Login using username avalon, password avalon.
  2. Open the built-in Chrome browser and point it to http://localhost.
  3. Click on Login
  4. Click on Register new identity
  5. Sign up using the default email to get admin access

After you have signed in, Avalon VM can be used like any other Avalon installation. The Avalon Collections Guide contains information for using Avalon.  You can create new collections and add items. Additional features can be configured using feature specific documentation.

5. Installing Sample Content (Optional)

The sample content can be ingested through a batch ingest process

  1. Create a new collection, for example, DEMO
  2. wget
  3. tar zxvf DemoFixturesBatch.tar.gz
  4. mv ExampleBatchIngest/* /home/avalon/avalon-docker/masterfiles/dropbox/DEMO/

As the samples are ingested, you will see new items being added to the collection. Be patient as the media transcoding may take a while.

6. Building your own OVA file

If you want to build your own OVA file follow the instructions on

Troubleshooting the Avalon VM

Because the OVA uses Docker and Docker-Compose, you can find instructions on how to navigate the stack on the avalon-docker github page

Reconfiguring the Avalon VM

Resetting the root password

Known Issues

Known Issues - a list of bugs, workarounds, and cautions.

In addition, there are some issues for us to consider in future releases of this VM image:

(info) information(question) oddity, potential todo item(plus) todo item(minus) issue w/o workaround(warning) issue with workaround