Index of /hsa/legacy/software/hipe_vm

[ICO]NameLast modifiedSizeDescription

[PARENTDIR]Parent Directory   -  
[   ]HIPE-15.0.1_1.md5 2017-07-04 11:47 52  
[   ]HIPE-15.0.1_1.ova 2017-06-08 14:25 4.7G 
[TXT]VERSION.html 2017-07-04 11:47 319  
[TXT] 2017-06-26 15:50 247  

In addition to the normal Java distribution, HIPE is also available as a pre-configured OVA Virtual Machine (VM) image. The aim is to extend the usable lifetime of the software by further decoupling it from the host operating system and hardware. The HIPE VM installation includes the HIFI, PACS and SPIRE options and the specialized ICC packages intended for calibration scientists.

The guest OS is Debian Linux with the LXDE desktop. The minimum of applications are installed as it assumed that other applications will be run on the host operating system.

Getting Started

System Requirements


Running HIPE

Stopping the VM

Performance Tips

Transferring Data

There are several ways to transfer data between the guest and host:

Known Issues


Configuring Memory

The default configuration of the VM assumes that the host machine has 8 GB of RAM. However, 16 GB are recommended for processing Herschel data.

The memory configuration should be adjusted to suit your system, since the optimum settings will depend on the amount of RAM, the host OS and other factors. The memory can be configured as follows:

For example, the default 8 GB configuration has 6 GB assigned to the VM, leaving 2 GB for the host OS and applications. HIPE is configured to use up to 4.5 GB, leaving 1.5 GB for the Linux guest OS.

Increasing Disk Space

The VM has a 12 GB virtual disk of which just over 4 GB is free for user data. If you need more disk space, there are several possibilities which are described below:

Shared Folder

The simplest way to increase disk space is to create a directory on the host operating system and mount it as a shared folder on the guest OS. It is useful to do this anyway as it provides a convenient way to transfer files between the guest and host.

Note that shared folders require the VirtualBox Guest Additions, but these are already installed.

USB Disk

Another simple solution is to plug an external USB disk into the host and mount it on the guest OS. The disk may be formatted with FAT32 or a Linux partition (e.g. ext4). Data transfer is likely to be faster with a Linux partition. Also bear in mind the 4GB file size limitation of FAT32.

Second Virtual Disk

Another solution is to add a second virtual disk. This is more complex to set up than a shared folder or USB disk, but should give better performance. For details, see "Advanced Topics" below.

Updating the Guest Additions

VirtualBox may prompt you to update the Guest Additions. Updating isn't always necessary but should be tried if any of the Guest Addition features are not working properly.

Advanced Topics

Adding a Second Virtual Disk

The disk space available to the guest can be increased by creating a second virtual disk. It is recommended to back-up the VM before attempting this.

Using other Hypervisors

The VM was created with VirtualBox but uses the following standards to provide compatibility with other hypervisors:

The HIPE VM is pre-configured with the VirtualBox Guest Additions to allow simple out-of-the-box operation with VirtualBox. These provide useful features such as:

However, the Guest Additions must be removed for use with other hypervisors. To uninstall them, run the following command in a VM terminal window:

   sudo /opt/VBoxGuestAdditions-5.1.20/

The following sections provide some notes on known issues with various hypervisors.

VMware Fusion or VMware Workstation

If the VMware import fails with a warning about OVF compliance, press "Retry" and it should work the second time.

For VMware, similar functionality to the VirtualBox Guest Additions is available from either VMware Tools or open-vm-tools. The latter can be installed by running the following command in a VM terminal window and then restarting the VM:

  sudo apt-get install open-vm-tools-desktop


The OVA file can in principle be converted for Hyper-V using the Microsoft Virtual Machine Converter.

However, there is a known issue with the format of the VirtualBox VMDK virtual disk files which makes this conversion fail (The disk UUID entries in VMDK file header are not accepted by the converter).