-
Notifications
You must be signed in to change notification settings - Fork 0
Filesystem and Storage
André Borchert edited this page Jun 13, 2026
·
7 revisions
This page describes the minimal storage plan for OSAI.
The initial storage plan includes:
- boot partition;
- system image;
- app data;
- repository worktrees;
- build artifacts;
- logs and telemetry;
- rollback snapshots.
QEMU uses VirtIO block first. GPT parsing and a simple read-only filesystem are enough for early boot.
The system image should be reproducible and generated from scripts. Build artifacts belong in build/, out/, or another ignored output directory.
Each app agent should use explicit worktrees and build output directories. Build artifacts should not contaminate source trees.
Snapshot and rollback are required before code-changing agents can safely modify running services.
NVMe is the first real storage target after VirtIO. Queue ownership and NUMA locality matter for Intel Xeon.
This page defines the GitHub Wiki navigation sidebar.
- Architecture
- AI Cells
- CPU AI Runtime
- App Agents
- Memory System
- Networking
- Scheduler and Core Isolation
- Filesystem and Storage
- Driver Model
- Security Model
- Build System
- Build System
- Project Tracker
- Implementation Plan
- QEMU Full OS Core Workdown
- QEMU 100 Completion Plan
- Example Apps
- Codex Work Packages
- Testing and Benchmarking