"Re-Engineering Microsoft’s Hyperlight in Rust"
summary
Microsoft’s Hyperlight moves from .NET/C# to Rust with a gradual FFI-first migration that keeps a C ABI for interop, uses WIT to generate type-safe guest/host bindings, and runs on Hyper‑V and KVM backends. The rework replaces GC-managed memory with explicit ownership, simplifies cleanup via Drop, and yields measurable speedups: sandbox creation 1.6→1.3ms, host call 240μs→26μs, and WIT-generated bindings eliminate runtime signature mismatches while requiring a longer migration and API reshaping.
AI-written summary · about
chapters (11)
- 0:00Introductions and agenda
- 1:21What is Hyperlight?
- 7:28Hyperlight Rust API
- 10:35Hyperlight C# API
- 13:24Why migrate to Rust?
- 17:02Migration strategy
- 19:03Memory management lessons
- 21:04WebAssembly Interface types
- 27:32Key takeaways
- 31:15Community and closing
- 33:33Q&A session
related talks
26mElixir, WebAssembly, and Rust - The Ultimate Hybrid
32mRunning Wasmtime in Hardware-Isolated Microenvironments
30mRust in the Browser for Javascripters:New Frontiers,New Possibilities
22mExtending JavaScript with Rust
47mRewrite the web with Rust and Web Assembly
29mRust & JavaScript Interoperability
30mImproving web app with Rust and WASM
05mKeynote: Modernizing Virtualization Technology for Cloud Native Computing