Install the appliance
The appliance runs TestVibe under systemd on Ubuntu 24.04 LTS. Download the image and matching checksums from the customer portal.
Before you import
Use an x86-64 host with at least 4 vCPU and 8 GB RAM for evaluation. Allow more capacity for concurrent browsers. Review the network boundaries before planning disconnected operation; included software and offline TestVibe license verification alone do not establish full air-gap readiness.
Verify your downloads against the supplied SHA-256 manifest. The installation overview covers package selection.
Import both disks
The VHDX archive contains compressed OS and data disks. Decompress both with zstd and attach both to a Hyper-V Generation 2 VM. Use the Microsoft UEFI Certificate Authority Secure Boot template for Linux, or disable Secure Boot if your host cannot use it.
The OVA contains both disks for VMware or VirtualBox. In VirtualBox, explicitly enable EFI before boot. Connect the VM network adapter to a network reachable from your browser; NAT requires appropriate forwarding.
The data disk holds PostgreSQL, artifacts, installation identity, and generated configuration. A DATA DISK NOT ATTACHED message means you must shut down and attach the correct second disk.
Complete VirtualBox example
Replace the placeholders with your downloaded version and network adapter. Run the checksum command from the directory containing the files named in the manifest.
sha256sum -c SHA256SUMS
VBoxManage import testvibe-<version>.ova --vsys 0 --vmname TestVibe-<version>
VBoxManage modifyvm TestVibe-<version> --firmware efi --cpus 8 --memory 16384
VBoxManage list bridgedifs
VBoxManage modifyvm TestVibe-<version> --nic1 bridged --bridgeadapter1 "<your adapter>"
VBoxManage startvm TestVibe-<version> --type gui
First boot and setup
Keep the VM console visible while initialization runs. Open the displayed application address, choose Create an account, and continue in Settings → Administration. There is no shared default password or separate administration website. See first boot.
Upgrades and recovery
Back up before upgrading. Replace the OS disk and retain your existing data disk; never substitute the empty data disk from a new import. Use the VM console's restricted recovery menu when administrator access is lost.