hypeman-remote-linux-tests

name	hypeman-remote-linux-tests
description	Run Hypeman tests on a remote Linux host that supports the Linux hypervisors. Use when validating cloud-hypervisor, Firecracker, QEMU, embedded guest artifacts, or Linux-only integration behavior on a server over SSH.

Hypeman Remote Linux Tests

Use this skill to run Hypeman tests on a remote Linux server in a way that is repeatable and low-friction for any developer.

Quick Start

1. Pick a short remote working directory under the remote user's home directory.
2. Ensure the remote test shell includes /usr/sbin and /sbin on PATH.
3. Bootstrap embedded artifacts and bundled binaries before running go test.
4. Run the smallest relevant test target first.
5. Treat host-environment failures separately from product failures.

Remote Workspace

Prefer a short path such as ~/hm, ~/hypeman-test, or another short directory name.

Cloud Hypervisor uses UNIX sockets with strict path-length limits. Long paths from default test temp directories or deeply nested clones can make the VMM fail before the actual test starts.

If a new test creates temporary directories for guest data, prefer a short root like:

mktemp -d /tmp/hmcmp-XXXXXX

Remote Bootstrap

Before running Linux hypervisor tests, make sure the remote clone has the generated guest binaries and embedded VMM assets:

export PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:$PATH
make ensure-ch-binaries ensure-firecracker-binaries ensure-caddy-binaries build-embedded

Why:

• go:embed patterns in the repo require the bundled binaries to exist at build time.