[dependabot]

Bumps hyperlight-guest from 0.18.0 to 0.19.0.

Release notes

Sourced from hyperlight-guest's releases.

Release v0.19.0

What's Changed

Added

• Sandbox::snapshot_with_options takes a snapshot with SnapshotOptions. SnapshotOptions::scratch_size gives the sandbox, and later restores of the snapshot, a different scratch size. A guest can boot with the scratch its initialisation needs and run guest function calls from a snapshot with only the scratch they need, so each restore costs less. It can also give a guest more scratch than it booted with.
• Sandbox::scratch_allocated_bytes returns how much scratch the guest has allocated since the sandbox was last restored or snapshotted. The guest controls the value it is read from.
• hyperlight-component-csharp crate for generating C# host bindings from WIT worlds by @​ludfjig in hyperlight-dev/hyperlight#1946

Changed

• Core dumps no longer record the guest binary path. The process name and command line are always <unknown>, as they already were for sandboxes created from snapshots by @​ludfjig in hyperlight-dev/hyperlight#1975

• Breaking: Generated libc bindings use usize for size_t arguments and return values, including strlen and memcpy. Rust callers that use u64 or c_ulong need explicit conversions. The C ABI is unchanged.

• Breaking: Snapshots use ABI 9 and config schema v5. Existing snapshots must be regenerated.

• Breaking: PtRootFinder receives a SnapshotMemoryReader and returns a Result<Vec<u64>>. Read snapshot bytes with snapshot.read_exact(gpa, buffer)? and return roots with Ok(roots).

• Related snapshots share immutable memory layers. This reduces capture time and memory use. A guest can read data it overwrote before a snapshot from the older layers of that snapshot.

• KVM: deleting a memory slot flushes only that slot's guest mappings on Linux 6.12 and later. This speeds up the first guest call after a snapshot, restore, or unmap changes memory slots.

• Breaking: Sandbox::snapshot installs the captured snapshot into the sandbox and removes map_region and map_file_cow regions, which only restore removed before. Region pages the guest has not mapped into its page tables become unreachable at the snapshot instead of at the next restore.

• vmem::walk_va_spaces merges adjacent mappings of the same kind into one mapping.

• A new sandbox writes only the guest code, PEB and init data into its memory. The host populates other pages on first guest touch, which speeds up sandbox creation.

• Use talc as the guest heap allocator. Guest init writes only the start and end of the heap, which speeds up sandbox creation.

• Breaking: Snapshots no longer contain a zero-filled heap region, which makes them smaller and faster to create, save, and load. The guest heap is backed by scratch and has no fixed size. Running out of scratch aborts the guest with MallocFailed instead of failing the allocation.

• Breaking: The transport arena sits one unmapped guard page below the reserved scratch-top pages, at an address independent of the scratch size, and the page tables at the scratch base. The guest's page allocator stops at the arena GPA the host publishes in the scratch-top metadata, so guests must be rebuilt. hyperlight_common::layout::scratch_allocator_limit_gpa is renamed scratch_reserved_top_gpa, the start of the reserved pages. An allocator that stops there runs into the arena. The minimum scratch size grows by that guard page. Snapshot ABI 7: existing snapshots must be regenerated.

• Breaking: hyperlight-component-macro: host_bindgen! and guest_bindgen! encode values little-endian and qualify function names with their interface, such as wasi:http/types@0.2.0#[method]fields.get by @​ludfjig in hyperlight-dev/hyperlight#1946

Removed

• Breaking: SandboxConfiguration::set_heap_size, SandboxConfiguration::DEFAULT_HEAP_SIZE, SandboxBuilder::heap_size, and SandboxBuilder::get_heap_size.

Fixed

... (truncated)

Changelog

Sourced from hyperlight-guest's changelog.

[v0.19.0] - 2026-11-04

Added

• Sandbox::snapshot_with_options takes a snapshot with SnapshotOptions. SnapshotOptions::scratch_size gives the sandbox, and later restores of the snapshot, a different scratch size. A guest can boot with the scratch its initialisation needs and run guest function calls from a snapshot with only the scratch they need, so each restore costs less. It can also give a guest more scratch than it booted with.
• Sandbox::scratch_allocated_bytes returns how much scratch the guest has allocated since the sandbox was last restored or snapshotted. The guest controls the value it is read from.
• hyperlight-component-csharp crate for generating C# host bindings from WIT worlds by @​ludfjig in hyperlight-dev/hyperlight#1946

Changed

• Core dumps no longer record the guest binary path. The process name and command line are always <unknown>, as they already were for sandboxes created from snapshots by @​ludfjig in hyperlight-dev/hyperlight#1975

• Breaking: Generated libc bindings use usize for size_t arguments and return values, including strlen and memcpy. Rust callers that use u64 or c_ulong need explicit conversions. The C ABI is unchanged.

• Breaking: Snapshots use ABI 9 and config schema v5. Existing snapshots must be regenerated.

• Breaking: PtRootFinder receives a SnapshotMemoryReader and returns a Result<Vec<u64>>. Read snapshot bytes with snapshot.read_exact(gpa, buffer)? and return roots with Ok(roots).

• Related snapshots share immutable memory layers. This reduces capture time and memory use. A guest can read data it overwrote before a snapshot from the older layers of that snapshot.

• KVM: deleting a memory slot flushes only that slot's guest mappings on Linux 6.12 and later. This speeds up the first guest call after a snapshot, restore, or unmap changes memory slots.

• Breaking: Sandbox::snapshot installs the captured snapshot into the sandbox and removes map_region and map_file_cow regions, which only restore removed before. Region pages the guest has not mapped into its page tables become unreachable at the snapshot instead of at the next restore.

• vmem::walk_va_spaces merges adjacent mappings of the same kind into one mapping.

• A new sandbox writes only the guest code, PEB and init data into its memory. The host populates other pages on first guest touch, which speeds up sandbox creation.

• Use talc as the guest heap allocator. Guest init writes only the start and end of the heap, which speeds up sandbox creation.

• Breaking: Snapshots no longer contain a zero-filled heap region, which makes them smaller and faster to create, save, and load. The guest heap is backed by scratch and has no fixed size. Running out of scratch aborts the guest with MallocFailed instead of failing the allocation.

• Breaking: The transport arena sits one unmapped guard page below the reserved scratch-top pages, at an address independent of the scratch size, and the page tables at the scratch base. The guest's page allocator stops at the arena GPA the host publishes in the scratch-top metadata, so guests must be rebuilt. hyperlight_common::layout::scratch_allocator_limit_gpa is renamed scratch_reserved_top_gpa, the start of the reserved pages. An allocator that stops there runs into the arena. The minimum scratch size grows by that guard page. Snapshot ABI 7: existing snapshots must be regenerated.

• Breaking: hyperlight-component-macro: host_bindgen! and guest_bindgen! encode values little-endian and qualify function names with their interface, such as wasi:http/types@0.2.0#[method]fields.get by @​ludfjig in hyperlight-dev/hyperlight#1946

Removed

• Breaking: SandboxConfiguration::set_heap_size, SandboxConfiguration::DEFAULT_HEAP_SIZE, SandboxBuilder::heap_size, and SandboxBuilder::get_heap_size.

Fixed

• Guest libc accepts null buffers for zero-length writes.

... (truncated)

Commits

• a030884 chore: prepare release v0.19.0 (#2024)
• 94071f4 Remove the legacy heap region from snapshots (#1968)
• 4d2ab91 Add crate for host-side .net component bindings (#1946)
• 6c17f7c Expose how much scratch a sandbox has allocated (#2019)
• 3294ee3 Restore the guest TSC exactly on KVM (#2015)
• 6793de9 fix(trace): read each guest trace batch once (#1991)
• b8169a2 Fix flaky reset_vcpu_simple and log cpu in CI (#2018)
• 35dd236 chore(deps): bump cc from 1.9.0 to 1.10.0 (#2006)
• fa13116 HIP 0005 - Structured Labels (#1978)
• 9414e2d chore(deps): bump smallvec from 1.16.3 to 1.16.4 (#2008)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[simongdavies]

@dependabot ignore this minor version

[dependabot]

OK, I won't notify you about version 0.19.x again, unless you re-open this PR.