## Resources

- **This doc**
- https://hackmd.io/blCrncfOSEuqSbRVT9KYkg

- **Code Of Conduct**
- https://github.com/hyperlight-dev/hyperlight/blob/main/CODE_OF_CONDUCT.md

- **Zoom Meeting**
- Every other Wednesday 09:00 (PST/PDT)
- Convert to your [Local Time](https://dateful.com/convert/pst-pdt-pacific-time?t=09)
- Meeting ID: 983 9750 8323
- Passcode: 2a9894bd-0133-4b31-be18-83c188c92441
- Invite Link: [https://zoom-lfx.platform.linuxfoundation.org/meeting/98397508323](https://zoom-lfx.platform.linuxfoundation.org/meeting/98397508323?password=2a9894bd-0133-4b31-be18-83c188c92441)

- **Slack**
- [hyperlight-dev channel](https://cloud-native.slack.com/archives/C08GRGTABJT)
- [Here's details on joining the CNCF Slack where #hyperlight is located](https://www.cncf.io/membership-faq/#how-do-i-join-cncfs-slack)
- [join link](https://join.slack.com/t/hyperlightgroup/shared_invite/zt-2ytby88df-B_S36BsRiOHEUesjf5fFaQ)

- **GitHub**
- [Contributor Guide](https://github.com/hyperlight-dev/hyperlight/blob/main/CONTRIBUTING.md)
- [Roadmap](https://github.com/orgs/hyperlight-dev/projects/2/views/1)
- Issues Project board - coming soon
- PR Project board - comming soon

## Template

### YYYY-MM-DD

- Recording
- Todo: add YT link
- Attendees
- Please add your name / company here
- Announcements
- Dicussion items
- ...
- ...

## Agenda

### 2025-09-17

- Recording
- Todo: add YT link
- Attendees
- David Justice (Microsoft)
- Danilo Chiarlone (Microsoft)
- Mark Rossetti (Microsoft)
- Simon Davies (Microsoft)
- James Sturtevant (Microsoft) (host)
- Shailesh
- Announcements
- Dicussion items
- New member and review of good first issues
- Issue Triage

### 2025-09-03

- Recording
- Todo: add YT link
- Attendees
- Doru Blanzeanu (MSFT)
- Jorge Prendes (MSFT)
- James Sturtevant (MSFT)
- Mark Rossetti (MSFT)
- Lucy Menon (MSFT)
- David Justice (MSFT)
- Adam Perlin (MSFT)
- Please add your name / company here
- Announcements
- [Hyperlight 0.9.0](https://github.com/hyperlight-dev/hyperlight/releases/tag/v0.9.0)
- [Hyperlight-wasm 0.9.0](https://github.com/hyperlight-dev/hyperlight-wasm/releases/tag/v0.9.0)
- Dicussion items
- Musl builds - https://github.com/hyperlight-dev/hyperlight/pull/849
- running on AzureLinux?
- (Jorge) Hyperlight Cargo plugin for building guests
- Makes it easier to get started building guests
- Also helps with ABI's by providing a custom target
- Also helps find and build the c dependencies
- Demo
- (Mark)Would we want to integrat into CI?
- Mabye make the plugin a library so don't need the plugin and it could be used in the build script that way.
- Tracing question [Doru]
- Shows demo of integrating opentelemtery
- working well for basic calls
- Call back through out instruction caues context to get confused.
- Can't use current mechinism, and looking for ideas on how to solve this.
- (Jorge) do you need a way to send some extra data when making host call?
- sort of
- Would a meta data field in the guest call help?
- this could work, it would mean we might loose ability to trace the out function.
- (David) - name of the spans is all the same, should it be different?
- This is configured on host, we should consider changing the name for each span.
- How do we differientiat host/guest traces in the tooling?
- (Jorge) Guest macros
- Calling and registering is verbose
- Added a PR with some potential improvements.
- https://github.com/hyperlight-dev/hyperlight/pull/851
- macro to simplify
- There is a few trade offs between dynamic and static
-

### 2025-08-20

- Recording
- Todo: add YT link
- Attendees
- Mark Rossetti (MSFT)
- James Sturtevant (MSFT)
- Doru Blanzeanu (MSFT)
- Dan Chiarlone (MSFT)
- David Justice (MSFT)
- Lucy Menon (MSFT)
- Jorge Prendes (MSFT)
- Quetzal Bradley (MSFT)
- Ludvig Liljenberg (MSFT)
- Adam Perlin (MSFT)
- Announcements
- [Hyperlight 0.8.0](https://github.com/hyperlight-dev/hyperlight/releases/tag/v0.8.0)
- review notes for some breaking changes around the function call and Snapshotting API
- If you get a warning about Callable trait not being used, it means that you were switched from the old auto-restoring behaviour to the new persistent behaviour.
- [Hyperlight Wasm 0.8.0](https://github.com/hyperlight-dev/hyperlight-wasm/releases/tag/v0.8.0)
- Hyperlight will be @ RustConf (https://rustconf.com/schedule/)!
- Dicussion items
- Issue Triage

### 2025-08-06

- Recording
- Todo: add YT link
- Attendees
- Mark Rossetti (MSFT) (host)
- Lucy Menon (MSFT)
- Danilo Chiarlone (MSFT)
- Jorge Prendes (MSFT) (note-taker)
- Ludvig Liljenberg (MSFT)
- James Sturtevant (MSFT)
- Adam Perlin (MSFT)
- David Justice (MSFT)
- Announcements
- Welcome Adam!
- Dicussion items
- [MaRosset] - New community meeting starting next instance (2025-08-20)
- We will have a new Zoom account without the time limit starting with the next meeting.
- Mark will update links to the meeting (slack/hackmd)
- Please update any links in your personal calendar invites
- https://www.cncf.io/calendar/ -> Search for Hyperlight
- Currently there are 2 meetings, we will delete one of them
- Same notes?
- We will keep the same notes since it's not linked to the zoom account
- New YouTube channel (Mark will back fill old recordings)
- We can't migrate old channel to CNCF because the account doesn't use a @microsoft.com account.
- Mark will back fill the new channel and update links in the agenda (maybe...)
- Restricted access to updload videos, if anyone need access reach out to Mark
- James: do we HAVE TO back fill the videos?
- Mark: probably not, but would be nice to
- 0.8.0 release? (Ludvig)
- We should sync on where we are at, and what we will do
- We need to merge the PR about bringing back the old behaviour of call_guest_function_by_name function
- There's a pending discussion about the Callable trait and what to do there
- We'll give it one more day if Simon is back and get his opinion
- The discussion affects hyperlight-wasm and not hyperlight-host.
- Lucy: The original intention was for hyperlight-wasm to have the non-restoring behaviour (i.e., the new behavour).
- https://cloud-native.slack.com/archives/C08GRGTABJT/p1754331136126179
- https://github.com/hyperlight-dev/hyperlight/pull/761#issuecomment-3156563703
- Consensus: Lets wait one more day to get Simon's opinion
- Milestone Review

### 2025-07-23

- [Recording](https://youtu.be/h1LYMrOlzSU)
- Attendees
- Mark Rossetti (MSFT) (host)
- Dan Chiarlone (MSFT)
- Jorge Prendes (MSFT) (note-taker)
- James Sturtevant (MSFT)
- Ludvig Liljenberg (MSFT)
- Lucy Menon (MSFT)
- David Justice (MSFT)
- Quetzal Bradley (MSFT)
- Benazir Khan (MSFT)
- Announcements
- v0.8.0 releases next week!
- Dicussion items
- Future of dirty pages tracking (ludvig)
- Benefits are much greater on large sandboxes
- main benefit in restoring snapshot
- some befenit on taking a snapshot
- there's a performance regresion due to tracking the dirty pages
- we see regressions mainly on small (and the default size) sandboxes
- I tested with guests that dirty a small amount of pages
- Jorge: Can we not track dirty pages, and detect them comparing memory when we take the snapshot
- Lucy: we loose the restore benefits as well there, since we don't know what pages to restore
- Plan is to measure it against our known use cases and see if improvements are positive, if they are we will merge it otherwise re-assess at that time
- Breaking changes in the pipeline: snapshotting (Jorge)
- Snapshot's now can be taken at any point in time, a consequence is that the after a function is called
- Lucy:
- should push users into the best usage pattern
- by either make depreciating and/or removing
- In agreement, that we should not reuse the function, discussion is around
- Dan: added a new transition for Nanvix, this might be related will follow up.
- Blockers for the release (Jorge)
- blocker tag in issues
- mmap API
- snapshotting with mmap
- Ludvig: we can work around this by forbidding going forwards in time
- call_guest_function_by_name
- Review of issues and milestone

### 2025-07-09

- [Recording](https://youtu.be/yjoPGVEo7YE)
- Attendees
- Mark Rossetti (MSFT) (host)
- Jorge Prendes (MSFT) (note-taker)
- Doru Blânzeanu (MSFT)
- Dan Chiarlone (MSFT)
- Lucy Menon (MSFT)
- James Sturtevant (MSFT)
- David Justice (MSFT)
- Ludvig Liljenberg
- Announcements
- hyperlight-wasm 0.7.0 published (Jorge)
- Issue reported with HL 0.7.0 (Doru)
- issue with debugging when running multiple sandboxes
- we have a [fix](https://github.com/hyperlight-dev/hyperlight/pull/678), but we haven't released a patch yet
- Jorge: should we release a patch or wait until next release?
- Mark: defered decision until after the meeting
- Dicussion items
- Deprecating mshv2 feature (Mark)
- Mariner that supports mshv2 is EOL
- Should we change the default from mshv2 -> mshv3?
- Or directly deprecate the mshv3?
- Mark: There's no way of deprecating features in cargo. What should we do?
- Lucy: We should deprecate, enabling mshv3 already disables mshv2 and there's VERY low chance of anyone actually wanting to use mshv2
- memory mapping in hyperlight-core (Lucy)
- you can now map an arbitrary region of memory into the guest.
- and hyperlight-wasm can use this to avoid copying the wasm module, and make it much faster.
- so far it only works in hyper-v
- would be interesting to magically map things to avoid serialization
- Mark: is there an example on how to use it? we should update some of the examples we have.
- Jorge:
- can we unmap things?
- Lucy: when we unroll things
- performance tradeoff between small serializations and mapping
- Lucy: TODO: fill this
- is there any limitations to the number of regions we can mmap?
- Lucy: TODO: fill this
- Jorge: This work is two folds, the hability for this host to map memory in the guest, and the guest caing able to use virtual memory inside of the sandbox.
- Lucy: yeah, one of them was a requirement for the other
- Ludvig: Yeah, in the benchmark plots you can really see the impact. 

- Issue triage (James)

### 2025-06-25

- [Recording](https://youtu.be/_RYQO_u5RKM)
- Attendees
- James Sturtevant (MSFT) (note-taker)
- David Justice (MSFT) (host)
- Mark Rossetti (MSFT)
- Jorge Prendes (MSFT)
- Dan Chialone (MSFT)
- Ludvig Liljenberg (MSFT)
- Lucy Menon
- Simon Davies (MSFT)
- Announcements
- v0.6.1 release for Hyperlight core
- support for musl
- some fixes to component macro
- brought back memory regions
- Hyperlight benchmark dashboard (soon to be public)
- https://hyperlight-dev.github.io/hyperlight-benchmarks/dev/bench
- Noticible items from the dashboard
- memory usage high on hl-wasm (components)
- might be interesting if we could compare to wasm modules
- There are three strategies to show differences between snapshotting and starting them new
> Benchmark dashboard view as of June 25th: 

- Dicussion items
- Hyperlight Wasm release updates
- challenges to release on crates.io due to build process which builds another crate. Crates.io doesn't like bundling crates. there is a RFC but nothing coming soon
- PR to create a tar and include it in the relase
- its close but running out diskspace
- https://github.com/hyperlight-dev/hyperlight-wasm/pull/78
- once thats in we will need to clean up CI a bit to get the release done
- (James) also update wasmtime versions and got an example running
- (Mark) will take a look at making images. have two options, packer use bigger images or (2) add data disk and configure
- (Jorge) we are running into space issues since we moved where it is being built
- Performance changes from snapshotting (Simon)
- Shares screen with results from benchmarks:
- Dirty page tracking
- Copying entire memory
- We reset the memory between calls so could be shared between tenants
- Measured the guest call where the size of the guest increases
-
- Dirty page tracking
- The time to make the function call doesn't increase too much
- Copying memory
- on small sized guests its faster than page tracking
- The size increases almost linerly with size
- Second set of tests is how long to create a sandbox
- Dirty page tracking
- slow on the default size but doesn't increase to much with size
- copying memory
- major difference between sizes
- Third set of tests measures size of paramaters
- Dirtypage tracking
- again doesn't slow down to much as it gets big
- Copying memory
- faster in small size but starts to slow down as size gets big
- There is a huristic that says we should use dirty pages vs uses replacing memory
- Maybe we come up with a strategy that uses both according to sizes and dirty memory changes
- Propose to go forward with Dirty page tracking and then integrate into
- (ludvig) how do we track page writes?
- (Simon) we only need to dirty pages in the guest.
- (lucy) I assume what you have here is dirtying only a small % of the heap - do you have a sense whether the amount you are using is realistic for regular workloads? Also: might we want to compare with CoW (e.g. write the snapshot into a memfd and mmap(MAP_PRIVATE) or something similar)?
- Simon - good question, and yes that is probalby why the last example demonstrates that
- Yes, we could do that for CoW
- Probably not one solution or one size fits all solution
- (mark) prefer to not do
- (james) do we know if it will help wasm?
- (simon) not sure comes down to what Lucy suggested
- (jorge) I think it might be an improvement
- (simon) maybe
- (jorge) if we use the new copy blob it will also probalby improve perf
- Issue wrangling

### 2025-06-11

- Recording
- Todo: add YT link
- Attendees
- Dan Chiarlone (MSFT)
- James Sturtevant (MSFT)
- David Justice (MSFT)
- Jorge Prendes (MSFT)
- Simon Davies (MSFT)
- Tomasz Andrzejak (MSFT)
- Benazir Khan (MSFT) Host
- Doru Blanzeanu (MSFT) Host
- Announcements
- release 0.6.0: https://github.com/hyperlight-dev/hyperlight/releases/tag/v0.6.0
- component bind-gen
- Handler threads 50% perf improvement
- There are breaking changes, read the release notes!
- support ELF core dump creation on guest crash: https://github.com/hyperlight-dev/hyperlight/pull/417
- generates core dumps
- lots of great docs!
- Dicussion items
- updating hyperlight-wasm to use upstream hyperlight 0.6.x: https://github.com/hyperlight-dev/hyperlight-wasm/pull/64
- 0.6.0 brought some breaking changes but also brought the ability to rely on a crate instead of the
- may need a patch release to make it work
- pagesize is private change
- pretty straight forward but requires a release
- introspection of guest functions
- hyperlight core wasn't using it so we removed it
- but hyperlight wasm might have
- (Simon) it worked before we removed it. We should put it back and then take our time
- do we need it for other runtimes?
- there is a cost to resolve it in host
- It is only used in module support, we need to figure out what we are doing with module support (vs component)
- (Dan) work to revert is done. need adjust a few comments. wants to understand how to handle it in just hyperlight-wasm
- (Jorge) - we also need som PEB support, not sure if that means we need more work? Regarding changes in hyperlight wasm - not to bad but the wrapper that registrers functions does a guest call and we could do it there. Less code than what would be done revert change.
- (Simon) - We will need to do a release either way. We should not hard
- (Dan) - PEB pointer was public?
- (Jorge) - no but code reads info in relation to PEB.
- (Dan) - lets just revert and we can then improve later
- (Jorge) - agree happy with either item
- (Simon) - has one issue for fixing patch release.
- (Mark) - lets update demos to use branches
- enable guest debugging for HyperV on Windows: https://github.com/hyperlight-dev/hyperlight/pull/478
- Brought up to speed, Requesting reviews
- enables debuggin on windows
- Visualizing benchmarks (james)
- review of the Milestone/new issue triage
- CI is broken on KVM (simon)
- support/build with x86_64-unknown-linux-musl (simon)
- a few issues that cause build to fail
- open pr to fix them
- How do we make sure it works? How to test it? Should we just not support it?
- (Jorge) what is the use case?
- wants to build host on ubuntu and deploy on Mariner.
- (Jorge) we have expereince with this from runwasi.
- (doru) - slow CI?
- (Jorge)- just another matrix?
- (Mark) - don't want to add a ton more
- (Simon) - lets get the pr in to unblock and then create an issue to discuss what parts of matrix we want to down size. Maybe daily CI?
- (Mark) maybe downsize fuzzing too
- (Jorge) - would perfer musl release than others. Do we build static binary?
- (Simon) - not to worried about that, can let others figure it out in build
- (Jorge) - particually how do we link libraries (seccomp)?
- (simon) - I think this does static, but not 100% sure, we don't release a binary so up to consumer.

### 2025-05-28

- [Recording](https://youtu.be/Mvi2xUuNr_A)
- Attendees
- Dan Chiarlone (MSFT) (note-taker)
- James Sturtevant (MSFT) (host)
- Mark Rossetti (MSFT)
- Jorge Prendes (MSFT)
- Simon Davies (MSFT)
- Benazir Khan (MSFT)
- Lucy Menon (MSFT)
- David Justice (MSFT)
- Ludvig Liljenberg (MSFT)
- Announcements
- Dicussion items
- Rust toolchain version
- Release
- Threading update
- Notes:
- intro
- v0.5.0 release might be delayed by a week depending on a couple of PRs we want to include on this release (e.g., https://github.com/hyperlight-dev/hyperlight/pull/533)
- [Rust toolchain version] we are encountering Dependabot and CI issues w/ Rust 2024 edition and v1.8.5 because some crates now only build for Rust 2024 edition. Simon made a PR addressing these concerns: https://github.com/hyperlight-dev/hyperlight/pull/534.
- [Release] will include the Rust toolchain version update in the v0.5.0 release and require a larger minimum required Rust version (v1.8.5).
- we also want to include the component bindgen work for the v0.5.0 release. Lucy will be working on fixing merge conflicts and updating the breaking changes w/ hyperlight-wasm. See relevant PR here: https://github.com/hyperlight-dev/hyperlight/pull/376.
- one other idea is to make a release now and just make another release later on (earlier than in 4 weeks time).
- We are set on making the v0.5.0 release today (May 28th). James volunteered to make the release (https://github.com/hyperlight-dev/hyperlight/blob/main/docs/how-to-make-releases.md).
- We'll tentatively release v0.6.0 June 4th. This release will include:
- component bindgen
- rust toolchain update
- threading update
- hl guest library split
- [Threading update] Ludvig introduced an `InterruptHandle` trait. On Linux, this is implemented by spamming a SIGKILL to, for example, on KVM, interrupt a `vcpu_fd.run` call.
- Mark suggested adding a graceful shutndown in the future (e.g., `SIGTERM`).
- People will review the PR and we'll have follow-up convos.

### 2025-05-14

- [Recording](https://youtu.be/lXMOZke2FVk)
- Attendees
- Dan Chiarlone (MSFT)
- Mark Rossetti (MSFT)
- Simon Davies (MSFT)
- Ludvig Liljenberg (MSFT)

- Announcements
- PE support and in-process drivers are getting dropped in v0.5.0 release
- Only ELF binaries support for guest execution :tada:
- Next week's issue wrangle(s):
- Dicussion items
- [Mark R] WSL runners discussion (low priority)
- [Doru B] Crashdump feature demo
- [Simon] Run GH Actions from fork options

### 2025-04-30

- [Recording](https://youtu.be/sdFWR3WbLNg)
- Attendees
- Please add your name / company here
- Mark Rossetti (MSFT)
- Doru Blanzeanu (MSFT)
- David Justice (MSFT)
- Dan Chiarlone (MSFT)
- Simon Davies (MSFT)
- Manoj Yadav (MSFT)
- James Sturtevant (MSFT)
- Ludvig Liljenberg (MSFT)
- Announcements
- Wasm component calculator example published
https://github.com/hyperlight-dev/hyperlight-wasm-calculator-example
- v0.4.0 release for hyperlight expected today
- Next week's issue wrangle(s):
- Dicussion items
- wasm calcualtor example walkthrough
- Hyperlight mesh framework demo

### 2025-04-16

- Recording
- Forgot to record this instance :'(
- Attendees
- Please add your name / company here
- Mark Rossetti (MSFT) (note taker)
- Simon Davies (MSFT)
- Danilo Chiarlone (MSFT) (host)
- David Justice (MSFT)
- Pranoy Dutta (UT Austin)
- Tiffany Kao (UT Austin)
- Ludvig Liljenberg (MSFT)
- Announcements
- Hyperlight @ KubeCon & Rejekts Europe'25
- [Wasm, Envoy, and Hyperlight Walk Into a Pod: No Vulnerabilities Allowed](https://youtu.be/83Dv8vymBZs?feature=shared)
- [Hyperlight Wasm announced](https://opensource.microsoft.com/blog/2025/03/26/hyperlight-wasm-fast-secure-and-os-free/)
- [Hyperlight v0.3.0 release](https://github.com/hyperlight-dev/hyperlight/releases/tag/v0.3.0)
- GDB debuggingin support for MSHV!
- Next week's issue wrangle(s):
- Dicussion items
- (Joe) Demo: Running AI-generated code in securely isolated environment using Hyperlight
- AI has knowledge cut-offs which can result in generating code with known vulnerabilities
- Use hyperlight to safely run untrusted AI-generated code
- Minimal modification to hyperlight-js, just a 'run code' helper method added
- AI was asked to generate code that tried to access memory outside of heap, result was panic in the hyperlight guest which was handled by the host as expected
- Ralph is interested in trying to get AI to try to break out of the hyperlight sandbox
- Joe wants to get AI generated wasm code running in hyperlight-wasm next
- Upcoming work
- Guest memory refactoring
- Guest crash dump debugging
- Future work to implement wasm system interface (wasi) APIs in hyperlight
-
- ...

### 2025-03-19

- [Recording](https://youtu.be/lLY-EQgoTmo)
- Attendees
- Danilo Chiarlone (MSFT) (co-host)
- Mark Rossetti (MSFT) (co-host)
- Doru Blanzeanu (MSFT)
- Ludvig Liljenberg (MSFT) (note taker)
- David Justice (MSFT)
- Simon Davies (MSFT)
- Manoj (MSFT)
- Announcements
- KubeCon and Cloud Native Rejekts coming soon!We have scheduled:
- 1 Cloud Native Rejekts talk,
- 2 booth demos, and
- 1 theatre demo.
- Next week's issue wrangle(s):
- Dicussion items
- Hyperlight v0.3.0 coming out next week.
- Hyperlight-Wasm soon being released–blog post on it will follow.
- Hyperlight core will soon support a flexible memory layout.
- Hyperlight MSHV GDB debugging coming soon.
- Backlog grooming?
- Notes:
- Announcements
- Hyperlight at Kubecon and Cloud Rejekts! Dan has talk at Cloud Rejekts and Hyperlight has booth demos at Kubecon
- Cancel meeting next week because busy at Kubecon
- Hyperlight 0.3.0 releasing next week
- hyperlight-wasm is coming out next week as well, together with a blog post. Hyperlight-wasm allows wasm components/modules to run inside of Hyperlight.
- Memory layout in Hyperlight is changing. Will allow guests rather than hosts to configure the memory layout, which is more flexible than current design.
- GDB will soon be supported on mshv platforms, just like it is for kvm right now.
- The remaining meeting was used for backlog grooming

### 2025-03-05

- [Recording](https://youtu.be/L69dM6g8kaw)
- Attendees
- Mark Rossetti (Microsoft) (meeting co-host)
- Dan Chiarlone (Microsoft) (meeting host)
- Lucy Menon (Microsoft)
- David Justice (Microsoft)
- Ralph Squillace (Microsoft) (scribe)
- Brooke Hamilton (Microsoft)
- Ruoqing He (ISCAS -- Chinese Academy of Sciences)
- Ludvig Liljenberg (Microsoft)
- Manoj Kumar Yadav (Microsoft)
- Simon Davies (Microsoft)
- Announcements
- Hyperlight is joining the CNCF!
- https://github.com/cncf/sandbox/issues/312
- https://github.com/cncf/sandbox/issues/348 (onboarding issue)
- Introductions:
- Discussion Items
- Hyperlight v0.2.0 release. This includes:
- the addition of interrupt handlers in the guest.
- support for KVM guest debugging.
- removal of SingleUseSandbox, and
- more!
- Dan:
- describes the above big features; the goal is now to start having planned releases (trained releases); yesterday we started planning the 0.3.0 release
- Hyperlight v0.3.0 release partially planned:
- https://github.com/orgs/hyperlight-dev/projects/3
- planned for the last week of March (train releases!)
- Puts the project in a new release for the following stuff
- Cloud Native Rejekts, and KubeCon EU 2025 approaching.
- Hyperlight talk at Cloud Native Rejekts: “Wasm, Envoy, and Hyperlight Walk Into a Pod: No Vulnerabilities Allowed”
- hyperlight hosted network filters in envoy
- Hyperlight talks at Azure Booth.
- Next week's issue wrangle(s):
- Notes:
- Extend to other architectures. e.g. RISC-V?
- Ruoquing is interested in RISCV work and works in cloud hypervisor community and has noticed that hyperlight used the rust-vmm crates.
- quick answer: YES.
- David: we were looking at ARM first, but if you're willing to work with us we can take a stab at that earlier
- Ruoquing notes that the RISCV-H proposal for hardware virtualiation support isn't quite ready; we seem to need to set up riscv CI first; if we want to do that, he'll work on a roadmap for this (the possibility exists for hardware support, too, but let's see how we can get there)
- Mark: CI might not be REQUIRED but it's a great thing.
- David: wasmtime and other runtimes do good work with QEMU emulated runner to start, we can do that
- Danilo: we have had other interest in RISCV targets, so this helps.
- TODO: understand how to establish communications on CNCF slack so that we can begin talking about next steps

### 2025-02-19

- [Recording](https://youtu.be/QbsQmjp98Sg)
- Attendees
- Please add your name / company here
- Mark Rossetti (Microsoft) (meeting host)
- Lucy Menon (Microsoft)
- Ralph Squillace (Microsoft) (scribe)
- Danilo Chiarlone (Microsoft) (scribe helper)
- Doru Blanzeanu (Microsoft)
- Brooke Hamilton (Microsoft)
- Manoj Kumar Yadav (Microsoft)
- Ludvig Liljenberg (Microsoft)
- Announcements
- Introductions all around, as we're still new to people
- Next week's issue wrangle(s):
- Doru has taken the lead for the next time around; Manoj is shadow lead (thanks!)
- Dicussion items
- Blogs: (published here for the record)
- [HL intro blog post](https://opensource.microsoft.com/blog/2024/11/07/introducing-hyperlight-virtual-machine-based-security-for-functions-at-scale/)
- [HL demo blog post](https://opensource.microsoft.com/blog/2025/02/11/hyperlight-creating-a-0-0009-second-micro-vm-execution-time/)
- [Mark/David] Hyperlight TAG-Runtime discussion [youtube recording](https://youtu.be/AaEURp1owpY?feature=shared&t=2072)
- Happened on Feb 6; went VERY well. Talked a bit about how it is built, but conversation went beyond that (1.5 hours)–showed demos (e.g., KubeCon NA 2024 demo). Lots of discussion and good questions. Might go back. Next steps? They will schedule us in their agenda to vote on our sandboxing status–will probably happen in March.
- KVM Guest debugging Demo
- https://github.com/hyperlight-dev/hyperlight/pull/111
- Small roadmap discussion for POSIX support item and what to expect (i.e., not full POSIX).
- Question on how Hyperlight fits into CNCF.
- Ralph's response centered around how the CNCF seems to be about containers because that was the core "portable, cloud-agnostic" technology at first; however, Hyperlight makes hypervisors "portable" at some level, and can be used everywhere to provide a different kind of "cloud agnostic" execution environment that is different than containers and webassembly as well as different from firecracker, gvisor, unikernels and so on.

### 2025-02-05

- [Recording](https://youtu.be/AN8nwSgIFRw)
- Attendees
- Please add your name / company here
- Ralph Squillace (Microsoft)
- David Justice (Microsoft) (scribe)
- Mark Rossetti (Microsoft) (host)
- Lucy Menon (Microsoft)
- Simon Davies (Microsoft)
- Aaron Roney (twitchax) (Cruise) (community member)
- Danilo Chiarlone (Microsoft)
- Ludvig Liljenberg (Microsoft)
- Michiel Van Kenhove (Ghent University - imec)
- Benazir Khan (Microsoft)
- Doru Blanzeanu (Microsoft)
- Announcements
- Hyperlight to be discussed at [CNCF tag-runtime meeting on](https://docs.google.com/document/d/1k7VNetgbuDNyIs_87GLQRH2W5SLgjgOhB6pDyv89MYk/edit?tab=t.0#heading=h.pd1gb2b1i6su) Feb 6 8am PT
- Next week's issue wrangle(s):
- Dicussion items
- (group) Quick introductions?
- (?) Release cadence
- Notes
- Curious if Hyperlight has a planned release cadence. Follow up with this in the next topic. There is 1 release and we need to establish a release plan.
- (Justice) Project roadmap and milestone review
- Notes
- Link to project board: https://github.com/orgs/hyperlight-dev/projects/2
- Lets cover some of the big 'boulders' we have on the project roadmap
- Hyperlight doesn't have a lot of examples or guests currently, David gives a quick overview of what we mean by guests for Hyperlight
- QuickJS guest will be an project providing an example on how to run javascript code in Hyperlight and will be maintained but mainly as a sample
- Wasmtime guest will be more of a production grade guest
- Probably will be tightly coupled with wasm component model / WIT
- Discussion on if running Hyperlight in Windows contaieners is possible
- If might be possible with 'host process containers' but more info and use cases are needed
- Operational tasks related to debugging guests / VMM / stuff in Hyperlight
- Doru is working on this by adding GDB support to the guests. KVM first, others to follow
- Future work includes creating a crash dump if there is a crash and guest debugging isn't enabled
- POSIX guest - for workloads that need access to thigns like sockets, filesystem, etc
- Dan gives an overview
- Discussion around releases
- v0.2.0 is overdue but we need to establish a release cadence
- Time-bound releases?
- Start with monthly releases and re-eval once more guests are available?
- Ralph can request out-of-band releases :P
- Rejekts / KubeCon - Is anyone attending?
- WOuld be great to have some in person discussions
- ... See https://cloud-native.rejekts.io/ for all the info on Rejekts. Schedule will be out on Jan 17 (notifications to accepted talks out next week!)