Skip to content

doc: name every guest the validation suites boot #472

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Pedro Henrique Penna (ppenna) merged 1 commit into from
Oct 10, 2026
Merged

doc: name every guest the validation suites boot #472

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions doc/design/validation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,15 @@ The implementation is exercised at three levels:
- OpenVMM VMM tests invoked through `nvx.py test-openvmm`: a test-harness
microVM lifecycle test and a management-RPC lifecycle, SMP, and snapshot
test that uses NVX's ACPI-free, MP-enabled x86-64 Linux-direct kernel and
initramfs; and
Alpine initramfs; and
- NVX-owned process tests using this repository's Linux kernel and selected
Alpine or Ubuntu initramfs through the public OpenVMM CLI.
Alpine, Ubuntu, or Azure Linux initramfs through the public OpenVMM CLI.

Alpine, the only sandbox-control guest, supports every NVX-owned scenario.
Ubuntu and Azure Linux reject the scenarios that
[`test-microvm`](../usage.md#test-microvm) lists, and their guest chapters
list what CI runs on them: [Ubuntu](../guests/ubuntu-guest.md#validation) and
[Azure Linux](../guests/azurelinux-guest.md#validation).

The harness lifecycle test covers portb I/O, status shutdown, rejection of
host save and pulse save/restore, and a snapshot request that continues
Expand Down
Loading