Home / Companies / Boxd / Blog / Post Details
Content Deep Dive

fork(), but for somebody else's process

Blog post from Boxd

Post Details
Company
Date Published
Author
Laurentiu Ciobanu
Word Count
1,267
Company Posts That Month
6
Language
English
Hacker News Points
-
Post removed?
No
Summary

Boxd introduces a Linux system call, `import_cow_range`, to rapidly clone a running virtual machine’s guest memory into an independently running VMM process using fork-style copy-on-write semantics. Rather than copying gigabytes of RAM, writing snapshots to disk, forking and then losing memory through `exec()`, or handling page faults in userspace via `userfaultfd`, the new mechanism shares the parent’s memory pages while copying only page-table entries and write-protecting both mappings. When either machine modifies a shared page, the kernel handles the fault and creates a private page copy, while untouched pages remain shared. The design uses pidfds to avoid process-ID reuse races, requires guest RAM at the same fixed virtual address in both processes, and relies on existing ptrace permission checks. Cloning requires the source VM to remain alive and briefly paused while its mapping is imported, but can create a running machine in under 200 milliseconds without disk I/O or initial RAM copying, enabling live machines to serve as branchable templates for parallel tasks and experiments.

Trends Found in this Post

No tracked trend matches for this post yet.

Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.