Repository navigation
microvm: plumb virtio-pmem devices through the VM config and the kata sandbox - #2607
Closed
ajaysundar.k (ajaysundark) wants to merge 2 commits into
Closed
ajaysundar.k (ajaysundark) wants to merge 2 commits into
ajaysundar.k (ajaysundark) wants to merge 2 commits into
Conversation
2 tasks done
Add PMEMConfig and the Pmem field on VmConfig so ateom can attach host files to the guest as virtio-pmem devices with discard_writes for DAX mounts.
…box storages Extend CreateSandboxOpts with PMEM mounts so the agent mounts virtio-pmem devices during sandbox creation before containers start. Pass them using the virtio-fs storage driver, which calls mount(2) directly on Source without waiting for block hotplug uevents or ACPI NFIT devices.
ajaysundar.k (ajaysundark)
force-pushed
the
pr1-pmem-plumbing
branch
from
October 13, 2026 22:11
c697c90 to
9f11711
Compare
This was referenced Oct 13, 2026
Contributor
Author
|
This is redundant now that #2218 is merged |
Contributor
Author
|
/close |
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two small additions that later changes build on: a
PmemConfigentry in the Cloud HypervisorVmConfig(a virtio-pmem device maps a host file into guest physical memory; withdiscard_writesthe file is opened read-only and mapped private, so every guest on a node shares the host's one copy of its pages), and aPmemlist onCreateSandboxOptsthat the kata agent mounts when it creates the sandbox, before any container starts.The agent mount goes through the virtio-fs storage handler: it is the one handler that mounts its
Sourceas given. The block-device handlers wait for a hotplug uevent and the nvdimm handler accepts only ACPI pmem, whereas a virtio-pmem device is a PCI device present before the agent starts.No behavior change on its own: nothing in this PR adds a pmem device to a VM yet. Part 1 of 4 of serving container image layers to micro-VMs as EROFS over virtio-pmem with DAX (the design issue is #2440); parts 2 to 4 follow as stacked PRs.
go test -race ./cmd/ateom-microvm/...,hack/verify-all.shGo checks)