[FEATURE] MK6: Demonstrate independent process execution #203

Open
opened 2026-10-30 09:30:46 +01:00 by erikinkinen · 0 comments
Owner

Problem and motivation

Alpha 1 needs direct evidence that EriX functions as a secure microkernel OS. Launch multiple processes, communicate through IPC, access files and collect exit statuses.

Proposed behavior and scope

Demonstrate this requirement on the actual x86-64 QEMU/OVMF release image, using the applicable 1, 2 and 4-vCPU configurations. This strengthens architectural acceptance without adding production-scale features.

Authority, security and reliability

Process launch, IPC, file access and exit observation use original explicit authority and lifetimes. Apply security, reliability, then performance.

Acceptance criteria

  • Launch several independent userspace processes, exchange IPC messages and access authorized files.
  • Collect each actual exit status; cover denied IPC/file access, failed launch and concurrent process retirement.
  • Publish source-linked release-image results and document relevant kernel/userspace responsibilities and privileged-service boundaries.

Process lifecycle dependencies

Alternatives and tradeoffs

Isolated unit tests support this gate but do not establish end-to-end acceptance. Production SMP scaling, NUMA, CPU hotplug, networking, a graphical desktop, broad hardware support, comprehensive service supervision, full POSIX compliance and formal verification remain beyond Alpha 1.

Tracking and rollout

Part of the Alpha 1 microkernel demonstration gate, alongside the existing self-hosting acceptance. Keep implementation dependencies and evidence linked here.

## Problem and motivation Alpha 1 needs direct evidence that EriX functions as a secure microkernel OS. Launch multiple processes, communicate through IPC, access files and collect exit statuses. ## Proposed behavior and scope Demonstrate this requirement on the actual x86-64 QEMU/OVMF release image, using the applicable 1, 2 and 4-vCPU configurations. This strengthens architectural acceptance without adding production-scale features. ## Authority, security and reliability Process launch, IPC, file access and exit observation use original explicit authority and lifetimes. Apply security, reliability, then performance. ## Acceptance criteria - [ ] Launch several independent userspace processes, exchange IPC messages and access authorized files. - [ ] Collect each actual exit status; cover denied IPC/file access, failed launch and concurrent process retirement. - [ ] Publish source-linked release-image results and document relevant kernel/userspace responsibilities and privileged-service boundaries. ### Process lifecycle dependencies - [ ] [Define parent-death and orphan cleanup for Alpha 1](https://git.erikinkinen.fi/erix/procd/issues/61) - [ ] [Demonstrate forced termination of spinning and blocked processes](https://git.erikinkinen.fi/erix/procd/issues/62) ## Alternatives and tradeoffs Isolated unit tests support this gate but do not establish end-to-end acceptance. Production SMP scaling, NUMA, CPU hotplug, networking, a graphical desktop, broad hardware support, comprehensive service supervision, full POSIX compliance and formal verification remain beyond Alpha 1. ## Tracking and rollout Part of the [Alpha 1 microkernel demonstration gate](https://git.erikinkinen.fi/erix/integration/issues/207), alongside the [existing self-hosting acceptance](https://git.erikinkinen.fi/erix/integration/issues/65). Keep implementation dependencies and evidence linked here.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:22 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/integration#203
No description provided.