docs(readme): full-VM validation, distros covered, and backports#46
Merged
Conversation
Adds a high-visibility section (right after the CO-RE rationale) covering
the three things users keep asking about:
- validation is full-VM, not static: boots the real distro kernel in a
disposable QEMU/KVM VM and runs the real bpf() load/attach inside the
guest (runners: vm/virtme-ng/firecracker/host; leaves serial.log etc.)
- a distributions-covered table (Ubuntu, Debian, RHEL family via
Alma/Rocky/CentOS, Oracle UEK, Amazon Linux, SUSE, upstream mainline;
x86_64 + ARM64), linking docs/profile-catalog.md
- kernel version != feature support: enterprise distros heavily backport
(Ubuntu 5.4 fails ringbuf, AlmaLinux 8's 4.18 passes; AL2 4.14 no-BTF
still loads), linking the 14/14 enterprise case study
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a scannable section to the README (after the CO-RE rationale) answering the three things users keep asking:
.bpf.ointo the guest, runs the realbpf()load/attach inside that kernel, and keeps per-target evidence (serial.log,qemu.log,validator-result.json). Runners:vm/virtme-ng/firecracker/host.docs/profile-catalog.md.All facts sourced from the profile catalog and the enterprise-kernels case study. Cloud-native profiles (Bottlerocket/Talos/Flatcar) are deliberately omitted since they're cataloged but currently non-runnable via the SSH executor.
🤖 Generated with Claude Code