changed 2 days ago  
Linked with GitHub

Resources

Template

YYYY-MM-DD

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

Agenda

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
  • 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
  • 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
    • [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

  • 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
        Image Not Showing Possible Reasons
        • The image file may be corrupted
        • The server hosting the image is unavailable
        • The image path is incorrect
        • The image format is not supported
        Learn More →

  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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:
    • 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
  • 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)
      • [Mark/David] Hyperlight TAG-Runtime discussion youtube recording
        • 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
      • 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
  • 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
  • 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!)
Select a repo