Troubleshooting — Oracle VirtualBox

If the appliance is deployed but isn't behaving as expected, work through the issues below. If it boots but never connects — or the tunnel drops right after it establishes — the cause is usually firewall L7/TLS inspection or NAC, not this platform: see Connectivity Troubleshooting.

The VM shows a black screen or drops to an EFI shell

EFI firmware is not enabled. Power off the VM, go to Settings → System → Motherboard and tick Enable EFI (special OSes only), then start again. If you used the CLI, confirm VBoxManage modifyvm "rta" --firmware efi ran without error and the VM was fully powered off before you ran it.

The VM boots but cannot reach targets on the LAN

The network adapter is probably set to NAT. Power off the VM, change Settings → Network → Adapter 1 to Bridged Adapter and select the host NIC connected to the engagement LAN, then restart. For the CLI, use VBoxManage modifyvm "rta" --nic1 bridged --bridge-adapter1 "<HOST_NIC>".

How do I check the appliance's status?

This image is customized for your engagement and boots already registered. Open the VM console window in VirtualBox Manager to see the live status and troubleshooting dashboard (network interface, VPN tunnel, connectivity health). If the VM is running headless, use VBoxManage startvm "rta" --type gui or relaunch with the GUI type to view the console.

Import fails with a disk size or format error

Ensure you have at least 40 GB of free space on the VirtualBox default machine folder drive. If the OVA was corrupted during transfer, request a fresh copy from your engagement lead.

The OVA sets fewer than 4 vCPU or less than 8 GB RAM

Override at import time with --vsys 0 --cpus 4 --memory 8192 (CLI), or adjust the values in Settings → System → Processor and Settings → System → Motherboard after import.