You are reading the documentation for v1.3.0. The current release is v1.4.0.

Evaluation appliance

The build account is gone. Previous appliances — including the published
v1.2.0-63 — shipped the Vagrant build account: user vagrant with the
well-known default password, passwordless sudo, and sshd accepting password
authentication on a forwarded port. That is remote root on any reachable
appliance, guessable without ever downloading the image. The account, its
sudoers grants and the build host keys are now removed before export, SSH
password authentication is off, and each appliance regenerates its own host
keys on first boot.

Console access is preserved: a random root password is generated per build
and recorded in /root/QUICKSTART.md beside the web credentials. It is a
console credential — it will not work over SSH.

Other appliance changes:

  • The Vagrant shared folder is no longer exported. It pointed at the build
    machine's directory, so VirtualBox reported invalid storage on import and the
    OVA leaked the builder's filesystem layout.
  • The documented 8 GiB minimum is now actually reachable. Preflight
    floor-divided MemTotal, which excludes firmware reservation, so a genuine
    8 GiB box read as 7 GiB and was refused — on real hardware, not just in a VM.
    It rounds to the nearest GiB now.
  • Hugepages are sized to the box. The installer reserved a flat 8 GiB
    regardless of RAM, which on an 8 GiB box is the entire machine. The budget is
    tiered (8192 MiB at ≥12 GiB, 2048 MiB at ≥6 GiB, 1024 MiB below), so boxes at
    or above 12 GiB — the perf rig and every production target — are unchanged.
  • The intermittent first-boot hang is fixed. Roughly 1 first boot in 6-10
    after import never reached the web console, stalling in
    systemd-tmpfiles-setup-dev-early with a (no limit) job timer. It was
    present in v1.2.0-63 at the same rate, so it is not new in this release, and
    a power cycle always recovered it — but a first impression should not need
    one. The cause is a stalled expedited RCU grace period:
    synchronize_rcu_expedited() signals every CPU and waits for each to
    acknowledge, and under VirtualBox one vCPU intermittently never does, so
    every caller blocks indefinitely. The appliance now boots with
    rcupdate.rcu_normal=1, which uses ordinary grace periods and removes that
    dependency. Measured with a repeated fresh-import harness at 8 GiB: 75
    consecutive clean boots
    (30 at 4 vCPU, 30 on the shortcut test image, 15 at
    the shipped 3 vCPU), against 2 failures in 15 on the previous build. Every
    boot came up in 7-8 seconds.
  • The appliance ships 3 vCPU / 8 GiB — the fewest that satisfies the
    CPU-pinning rules (core 0 Linux housekeeping, core 1 VPP main, core 2 VPP
    worker). The single worker runs at ~15% of vector capacity while sustaining
    ~1 Gbps through the appliance's veth pair for the first time.
  • The appliance's virtual disk advertises 64 GiB but occupies ~4.3 GiB.
    It is dynamically allocated: VirtualBox writes blocks on demand and does not
    pre-check the host against the advertised size, so you do not need 64 GiB
    free to import or run it
    . Verified by importing and booting this appliance
    on a 9.8 GiB volume — it used 4.3 GiB and left 5.5 GiB free. Budget roughly
    7 GiB in total: 2.1 GiB for the download plus ~4.3 GiB for the imported VM.
    The guest's root filesystem is 31 GiB, so the file can grow toward that under
    heavy use; on a tight volume leave headroom, since a full host pauses the VM
    with a disk-full error. (Earlier notes said 20 GiB, which was never what
    shipped.)
  • CPESIM v0.4.16: struct-packed DHCP relay frames (36× on the rig, 17.2×
    measured on the appliance, byte-identical to the previous output), each frame
    parsed once instead of twice, a tick_hz throttle that had been declared and
    never referenced while costing 76% of the onboard loop, and QoS scoring that
    no longer counts subscribers which produced no measurement.