What you will find there:

• Getting started that was run end to end: requirements, the build, a guest image script, and a quick start.
• Nine tutorials, each printing the output you should see: your first SSD, garbage collection and WAF, zoned namespaces, Flexible Data Placement, latency tuning, several namespaces, key-value, a CXL SSD as memory, and configuration files.
• A guide per mode, including the CXL SSD, and feature guides for FDP, multiple namespaces, namespace management with protection information, and the CXL caching API.
• Reference pages generated from the binary: every device property, the runtime properties, log pages and counters, and the scripts.
• The design chapters and the changelog, and the whole manual as a PDF.

The manual is maintained in the FEMU repository, where every example is checked in CI. To correct a page, use its "Edit this page" link, which opens the file upstream. The website's own pages are now design notes, experiment tools, research and community material that build on the manual.

POSE does not fund new emulator features. It funds the work that turns a widely used research tool into a project its users can sustain together. The award has three objectives:

1. Ecosystem discovery and community engagement. Learn who uses FEMU, for what, and what keeps people from contributing. We are interviewing users in universities and industry this fall.
2. Contributor infrastructure and training. Onboarding paths, continuous integration and testing, and teaching material. The FEMU Manual and its nine tutorials are the first results.
3. Governance and security. A transparent governance charter and security policies. The proposed charter is open for comment, and the security policy is in the repository.

Where we start​

We will report progress against these numbers, taken from GitHub on October 2, 2026:

How to take part​

• Tell us how you use FEMU. Post in Show and tell: your lab, course or company, and what you emulate. It shapes what we build next.
• Ask and discuss on Discord, in GitHub Discussions, or on the mailing list, femu@googlegroups.com.
• Contribute with the first model test, a standalone exercise that needs no guest or KVM.
• Teach with FEMU using the teaching guide.

This material is based upon work supported by the U.S. National Science Foundation under Award No. 2550145. Any opinions, findings and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation.

The guides describe mapping and garbage-collection policies, NAND timing, configuration interactions, and the boundaries of each device model. They are pinned to FEMU commit 9d176f89138dfb00dcd2fba2aa61072268d9bf4a so readers can check a description against the reviewed implementation.

• Configuration recipes provide 19 complete examples with downloadable INI files.
• Observability explains counter interpretation and includes a decoder for FEMU's vendor statistics log.
• The developer learning path starts with a standalone test, follows a write through the emulator, and explains how to prepare a focused contribution.

The configurations have been checked against source declarations and expanded through the configuration helper. Guest execution remains a separate validation step. When sharing results or reporting a problem, include the FEMU commit, complete configuration, guest kernel and tools, and workload command.

Found a missing prerequisite or a mismatch with the code? Use the community guide to share a reproducible report or contribute a correction.