Problem
The kernel validator now supports a real QEMU/SSH-backed execution path, but it still depends on external VM assets and guest setup that are not packaged or documented as a supported bundle.
Why this matters
Without a maintained guest image + quickstart, the feature is real but not turnkey enough to hand to external researchers or run consistently across machines.
Scope
- publish a recommended guest image format (kernel + disk + SSH auth expectations)
- add a reproducible setup guide for the required env vars
- document supported guest assumptions (
gcc, dmesg, SSH, rootfs layout)
- add one smoke-tested sample image path or build recipe
Acceptance
- a fresh user can boot the VM-backed validator from docs alone
- docs include exact env var contract and one known-good guest recipe
- the workflow is honest about what is provided by repo code vs external assets
Problem
The kernel validator now supports a real QEMU/SSH-backed execution path, but it still depends on external VM assets and guest setup that are not packaged or documented as a supported bundle.
Why this matters
Without a maintained guest image + quickstart, the feature is real but not turnkey enough to hand to external researchers or run consistently across machines.
Scope
gcc,dmesg, SSH, rootfs layout)Acceptance