hypervisor/qemu: note seccomp sandbox as Phase 3 consideration

seccompsandbox already maps to -sandbox in cmdline_generator.rs via
seccomp_sandbox: Option<String> in HypervisorConfig. When Platform
takes over argument emission in Phase 3, sandbox support needs a typed
Objects::seccomp_sandbox field so the legacy generator can be removed
cleanly.

Assisted-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Zvonko Kaiser <zkaiser@nvidia.com>
This commit is contained in:
Zvonko Kaiser
2026-07-13 20:54:30 +00:00
parent 9ae0ceca59
commit 75f032153c

View File

@@ -644,6 +644,11 @@ Final PR in Phase 2: remove all remaining `#[cfg(target_arch)]` blocks from
`MemoryBackend::File`.
- Wire hugepages via `Platform::with_hugepages`.
- Lift `ObjectIoThread` / `ObjectRngRandom` into `Objects`.
- Consider wiring `seccompsandbox` (QEMU `-sandbox`) through `Platform`:
the config field `seccomp_sandbox: Option<String>` already maps to
`-sandbox` in `cmdline_generator.rs`, but the new path needs a typed
`Objects::seccomp_sandbox: Option<SeccompSandbox>` so the emission
is controlled by `Platform` rather than the legacy generator.
This is the phase that enables hugepages for `runtime-rs` (issue #12125).