Versions Compared

Old Version 1

changes.mady.by.user Mark Unwin

Saved on

compared with

New Version 2

changes.mady.by.user Mitchell Saunders

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

VirtualBox will import directly from an OVF/OVA file so you can just start up VirtualBox and select "Import Appliance..."

Image Removed

Browse to where you unzipped the file and select the ovf file

Image Removed

Select the file, you should see a screen something like this:

Image Added

On the Import Virtual Appliance window that will display, choose the location of where the FirstWave NMIS OVA was downloaded to. Click Next.

Image Added

You will then be prompted to review the Appliance settings. Click Finish here.

Image AddedImage Removed

The import process may take a couple of minutes to complete. Once imported, we recommend you change the following settings:

Network Adapter from NAT to Bridged

  1. If you find that the virtual machine's network adapter is set to NAT, you will need to change this to Bridged Adapter. Click on the Virtual Machine in Oracle VM VirtualBox Manager, then click Settings.
  2. Click on Network, then in Adapter 1 change the "Attached to" dropdown option to Bridged.

Image Added

Notes

VirtualBox Documentation

, just enough time to grab a cup of coffee I'd say.If you have any trouble the VirtualBox documentation is here:   https://www.virtualbox.org/manual/ch01.html#ovf

NOTE - The virtual machine is configured to use 8GB memory and the network interface may appear as NAT. Please revise the memory to suit and change the NAT adapter to Bridged.

Important Note regarding Ext4:

If your Virtualbox host is Linux and your VMs are stored on XFS or Ext4 file systems, then it is absolutely necessary that you enable the "Host I/O Cache" for all virtual disk controllers after importing the OVF file, or you run the risk of file system corruption in your guest. On one of our test systems (Linux kernel 3.14.23, Virtualbox 4.3.14) the VM wouldn't even fully get through the first boot before the virtual disks got corrupted - but with Host I/O Cache on everything is fine.

Below is an example of how to enable Host I/O Cache using VirtualBox:

Image Removed

Automatic time synchronization

Note - In some cases the system will may log you out over and over repeatedly due to the OVA by default having Automatic time synchronization enabled that may cause some authentication cookie issues. To avoid this issue simply check the "Hardware Clock in UTC Time" box in the settings menu under "System" before starting the appliance.

Image Removed

CentOS 7 on VirtualBox

It's now highly unlikely that VirtualBox users will find themselves at the dracut emergency shell prompt when first booting our vm that runs CentOS 7.
We continue to provide this information in case needed:

Image Removed

When faced with this obstacle reboot the vm selecting the rescue kernel. 

Image Removed

After it boots login as normal and try the try the following dacut command.  

...

dracut -f /boot/<kernel_image> <kernel_name>

, you will need to:

  1. Shutdown the virtual machine.
  2. Click on Settings, then System.
  3. Check the "Enable Hardware Clock in UTC time" checkbox and click OK.

Image Added

Image Removed

 If the command completes successfully reboot the vm normally.  Be aware that future kernel updates may require this maneuver be done again.