메뉴
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.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/kernel/hypeman --skill hypeman-remote-linux-tests명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| 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. |
Use this skill to run Hypeman tests on a remote Linux server in a way that is repeatable and low-friction for any developer.
/usr/sbin and /sbin on PATH.go test.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
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.mkfs.ext4 is commonly installed in /usr/sbin or /sbin, not always on the default non-login shell PATH.go test before this bootstrap often fails during package setup, not during test execution.QEMU is usually provided by the host OS, so there is no matching bundled ensure-qemu-binaries target. If QEMU tests fail before boot, verify the system qemu-system-* binary separately.
If the main development is happening locally and the Linux host is only for execution, sync only the files you changed rather than recloning every time.
Typical pattern:
rsync -az lib/instances/... remote-host:~/hypeman-test/lib/instances/
After syncing, re-run the bootstrap command if the changes affect embedded binaries, generated assets, or files referenced by go:embed.
Classify failures quickly:
pattern ... no matching files foundmake ensure-ch-binaries ensure-firecracker-binaries ensure-caddy-binaries build-embeddedmkfs.ext4 not found:
exec: "mkfs.ext4": executable file not found/usr/sbin:/sbin to PATH, then retrypath must be shorter than SUN_LEN/tmp or shared test-lock issues:
Improve repository test quality by eliminating flakes first, then reducing slow-test redundancy, and finally optimizing longest tests while preserving coverage. Use when asked to repeatedly run CI-equivalent no-cache test cycles, diagnose flaky tests, and document findings in this skill's notes.
Use when optimizing VM Initializing-to-Running latency while preserving functionality and low implementation complexity.
Add or adjust monitoring for a Hypeman feature using repository standards for logs, traces, and metrics. Use when a user asks for instrumentation, observability reviews, telemetry consistency changes, metric design, or production-signal improvements.