NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io · #3808 most downloaded on crates.io
Safe abstractions for accessing the VM physical memory
Last release 10 months ago
11 Dec 2025
Release timing varies
gaps range from 9 days to 7 months
Some releases are documented
notes for 10 of 30 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
30 releases · first in 2020
One column per quarter.
This release includes a major change to the vm-memory API in order …
This release includes a major change to the vm-memory API in order …
This release includes a major change to the vm-memory API in order to support
memory access permissions. The previous GuestMemory trait is now renamed
to GuestMemoryBackend, and GuestMemory has a completely new definition.
However, common interfaces such as GuestAddressSpace and Bytes remain on
GuestMemory; therefore, all callers that just use the Bytes interface
remain completely unchanged.
GuestMemory to GuestMemoryBackend, IoMemory to GuestMemoryIoMemory, IommuMemory, and Iommu/IotlbThis release re-packages the code of vm-memory 0.18.0 while preserving API compatibility with 0.17.1. All the actual implementation comes from version
This release re-packages the code of vm-memory 0.18.0 while preserving
API compatibility with 0.17.1. All the actual implementation comes from
version 0.18.0, which this crate re-exports with GuestMemoryBackend
changed back to GuestMemory.
No visible changes. Needed to fix docs.rs build.
No visible changes. Needed to fix docs.rs build.
[ #307 ] Remove deprecated functions Bytes::read_from , Bytes::read_exact_from , Bytes::write_to , Bytes::write_all_to , GuestMemory::as_slice , Guest…
GuestRegionContainer, a generic container of GuestMemoryRegions, generalizing GuestMemoryMmap (whichGuestRegionContainer<GuestRegionMmap>).GuestMemoryAtomic always implement Clone.GuestAddressSpace a subtrait of Clone.GuestMemory::get_slices()read_volatile_from, read_exact_volatile_from,write_volatile_to and write_all_volatile_to functions from the GuestMemory trait to the Bytes trait.GuestMemory::find_region and GuestMemory::num_regionsGuestMemoryRegionBytes, which enables a default implementation of Bytes<MemoryRegionAddress>GuestMemoryRegion if implemented.GuestMemoryMmap::from_ranges[_with_files]GuestRegionMmap::from_range to be separate from the error type returned by GuestRegionCollection functions.GuestRegionMmap::new from Result to Option.GuestMemoryRegion::bitmap() now returns a BitmapSlice. Accessing the full bitmap is now possible only if the type of the memory region is know, for example with MmapRegion::bitmap().Bytes::load() and Bytes::store() with get_slices() instead of to_region_addr()Bytes::read_from, Bytes::read_exact_from,Bytes::write_to, Bytes::write_all_to, GuestMemory::as_slice, GuestMemory::as_slice_mut, GuestMemory::with_regions,GuestMemory::with_regions_mut, GuestMemory::map_and_fold, VolatileSlice::as_ptr, VolatileRef::as_ptr, andVolatileArrayRef::as_ptr.check_file_offset check when using MmapRegionBuilder.mmap(2) syscall itself already validates that offset and length are valid, and trying to replicate this checkBytes::read() and Bytes::write() not to ignore try_access()'s count parameterGuestMemory::try_access(). Use GuestMemory::get_slices() instead.[ #328 ] Support vmm-sys-util 0.14.0
[ #304 ] Implement ReadVolatile and WriteVolatile for TcpStream
[ #287 ] Support for RISC-V 64-bit platform.
[ #270 ] atomic_bitmap: add capability to reset bits range
read_volatile_from and write_volatile_into[ #279 ] Remove restriction from read_volatile_from and write_volatile_into that made it copy data it chunks of 4096.
read_volatile_from and write_volatile_into that made it copy data it chunks of 4096.[ #266 ] Derive Debug for several types that were missing it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →