mirror of
https://github.com/NVIDIA/OpenShell.git
synced 2026-11-09 09:15:23 +08:00
Florent BENOIT
a4c848adbd
* feat(vm): add host bind mount support via virtiofs (libkrun) Introduce host directory bind mounts for libkrun VM sandboxes using the virtiofs4 API with simplified permission semantics. The gateway accepts `enable_bind_mounts` in the `[openshell.drivers.vm]` TOML table and forwards it to the VM driver subprocess. Mounts are specified per-sandbox in driver_config.mounts[] with source, target, optional read_only (default: read-only), and an optional `type` that must be `bind`, so Docker and Podman bind entries (without `selinux_label`) parse unchanged. At sandbox validation the driver rejects mounts unless bind mounts are enabled and resource admission is disabled. It rejects GPU and other QEMU launches, sources with control characters, and more mounts than libkrun has interrupt lines for (32 on aarch64, 3 on x86_64), and checks targets against reserved VM-internal directories and each other (no nested targets). The QEMU check runs again once the launch backend is resolved. Host source directories are checked at provisioning, before image preparation, so a briefly missing source fails provisioning visibly instead of denying recovery of a persisted sandbox. Missing, inaccessible, symlinked, non-directory, and unreadable sources are rejected: libkrun does not follow a final symlink, and on macOS it panics during guest boot when it cannot open the share root. The driver generates virtiofs tags and always writes a guest-side manifest into the overlay disk, together with the init drop-ins, so an image-supplied manifest can never drive guest mounts. The launcher parses its tab-separated --vm-mount arguments from the right, so a source can never shift the tag or mode, and the driver logs each shared directory at launch. Guest init mounts the shares after every /sandbox ownership fixup and the init drop-ins, so recursive chowns never reach host files. It refuses targets that traverse symlinks in the image, hands newly created mount point parents under /sandbox to the sandbox user, and skips an empty manifest. krun_add_virtiofs4 is resolved optionally, so older libkrun runtimes still boot sandboxes without mounts. The kernel config lists CONFIG_FUSE_FS and CONFIG_VIRTIO_FS explicitly; the pinned libkrunfw base config already enables both. A vm_bind_mount e2e test checks a read-write share round-trips data with the host, accepts a new file, directory, and nested file that the host then sees, and that a read-only share rejects writes. libkrun on rootless Linux refuses file creation by a guest user whose UID/GID differ from its own, so the VM e2e gateway runs the sandbox as the gateway user there. It enables bind mounts like the Docker and Podman e2e gateways. The runtimes docs cover the mount limit, the symlink restriction, the guest-kernel exposure, and the rootless Linux UID/GID note. The debug-openshell-cluster skill lists VM bind mount checks. Signed-off-by: Florent Benoit <fbenoit@redhat.com> * fix(nix): refresh vm-runtime hashes to the libkrun v1.19.4 runtime The Nix vm-runtime package fetches the rolling vm-runtime release with fixed hashes pinned on 2026-09-16. The release was rebuilt on 2026-09-21 after the libkrun v1.19.4 / libkrunfw v5.6.1 bump (#3451), but the hashes were not updated, so CI kept substituting the 2026-09-15 runtime (libkrun v1.17.4) from the binary cache. That libkrun lacks krun_add_virtiofs4, which VM bind mounts need. Point the hashes at the current release assets. Signed-off-by: Florent Benoit <fbenoit@redhat.com> --------- Signed-off-by: Florent Benoit <fbenoit@redhat.com>
53 lines
1.9 KiB
Rust
53 lines
1.9 KiB
Rust
// SPDX-FileCopyrightText: Copyright (c) 2025-2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
|
|
// SPDX-License-Identifier: Apache-2.0
|
|
|
|
// `defaults-without-telemetry` is an alias for the default feature set minus
|
|
// `telemetry`, not a switch that turns telemetry off. Cargo cannot subtract a
|
|
// default feature, so adding it on top of the defaults would otherwise produce
|
|
// a telemetry-on build that reads as telemetry-free. Fail the build instead.
|
|
#[cfg(all(feature = "telemetry", feature = "defaults-without-telemetry"))]
|
|
compile_error!(
|
|
"features `telemetry` and `defaults-without-telemetry` are mutually exclusive; \
|
|
build a telemetry-free VM driver with `--no-default-features --features defaults-without-telemetry`"
|
|
);
|
|
|
|
#[cfg(feature = "allocation-tracking")]
|
|
pub mod allocation_tracking;
|
|
|
|
#[cfg(feature = "compute-driver")]
|
|
pub mod driver;
|
|
#[cfg(feature = "compute-driver")]
|
|
mod embedded_runtime;
|
|
#[cfg(feature = "compute-driver")]
|
|
mod ffi;
|
|
#[cfg(feature = "compute-driver")]
|
|
pub mod gpu;
|
|
#[cfg(feature = "compute-driver")]
|
|
mod isolation;
|
|
#[cfg(feature = "compute-driver")]
|
|
mod layer_applier;
|
|
#[cfg(feature = "compute-driver")]
|
|
pub mod lifecycle;
|
|
#[cfg(feature = "compute-driver")]
|
|
pub mod otel_tracing;
|
|
#[cfg(feature = "compute-driver")]
|
|
pub mod procguard;
|
|
#[cfg(feature = "compute-driver")]
|
|
mod rootfs;
|
|
#[cfg(feature = "compute-driver")]
|
|
mod runtime;
|
|
|
|
#[cfg(feature = "compute-driver")]
|
|
pub use driver::{VmDriver, VmDriverConfig};
|
|
#[cfg(feature = "compute-driver")]
|
|
pub use lifecycle::{
|
|
BackendFeature, ExtensionCapabilities, ExtensionDescriptor, GuestInitDropin, LaunchAbortReason,
|
|
LaunchPlan, LifecycleError, LifecycleExtension, LifecycleExtensionRegistry, LifecycleResult,
|
|
RestoreContext,
|
|
};
|
|
#[cfg(feature = "compute-driver")]
|
|
pub use runtime::{
|
|
VM_RUNTIME_DIR_ENV, VmBackend, VmLaunchConfig, VmMount, VsockPortMap, configured_runtime_dir,
|
|
run_vm,
|
|
};
|