more/cloud-hypervisor/release-notes.md

51 …- [Optimized Boot Time with Parallel Memory Prefault](#optimized-boot-time-with-parallel-memory-pr…
175     - [`AArch64` Memory Map Improvements](#aarch64-memory-map-improvements)
289     - [Memory Zones](#memory-zones)
302     - [Virtio Memory Ballooning Support](#virtio-memory-ballooning-support)
318 …- [Block, Network, Persistent Memory (PMEM), VirtioFS and Vsock hotplug](#block-network-persistent…
322     - [Alternative Memory Hotplug: `virtio-mem`](#alternative-memory-hotplug-virtio-mem)
356     - [Memory mapped virtio transport](#memory-mapped-virtio-transport)
359     - [Large memory guests](#large-memory-guests)
371     - [Virtual persistent memory](#virtual-persistent-memory)
503 expected to improve performance, such as reducing memory usage and reduce CPU
588 * Fix memory resize error due to incorrect bounds checks (#6736)
628 physical memory properties to allow optimisations and security features.
816 ### Optimized Boot Time with Parallel Memory Prefault
819 memory prefault.
883 Now VFIO devices with 32-bit memory BARs can be attached to non-zero PCI
959 nodes. Examples can be found from the [memory documentation](docs/memory.md)
1032 * Use wrapping add for memory offset from instruction emulator (#5719)
1073 Requesting to dump the guest memory as core dump will now transparently pause
1141 * Ensure all guest memory regions are page-size aligned (#5496)
1246 Before this change, user can set a directory to `file` of the `--memory-zone`
1249 the native support for hugepages and allocating anonymous shared memory.
1406 * Memory mapped into the guest is now marked as non-dumpable which prevents large core files (#5016)
1419   supporting huge pages or shared memory backing which is now natively supported
1480 By default, but controllable through `--memory thp=off` if it possible to back
1481 the guest memory with Transparent Huge Pages (no file backing/`shared=off`)
1492   memory consumption (#4835)
1570   feature) and dumping guest memory.
1691 Under the `guest_debug` feature flag it is now possible to extract the memory
1762 * Fix algorithm finding HOB memory resources (#3983)
1768 * Only create ACPI memory manager DSDT when resizable (#4013)
1823 ### `AArch64` Memory Map Improvements
1825 The memory map when running on `AArch64` has been improved for the handling of
1839 * ACPI tables are not produced for memory hotplug when running with
1903 memory density.
1936 * Fix sporadic seccomp violation from glibc memory freeing (#3610, #3609)
1963 added in which the memory for the VM is not compared from source to
2036 Based on VFIO region capabilities, all regions can be memory mapped, limiting
2096 based memory hotplug and the `virtio-balloon` device now supports live
2102 `virtio-mem` based memory hotplug and unplug.
2110 * ACPI hotplugged memory is correctly restored after a live migration or
2114 * Live migration with large blocks of memory was buggy due to an in issue in
2479 Through the addition of `hugepage_size` on `--memory` it is now possible to
2481 memory. The user is required to ensure they have sufficient pages of the
2619 Control of the setup of `virtio-balloon` has been moved from `--memory` to its
2621 controls without overloading `--memory`.
2634 * `virtio-pmem` with`discard_writes=on` no longer marks the guest memory as
2637 * When using the ACPI method to resize the guest memory the full reserved size
2673 ### Memory Zones
2675 …memory allocation for the guest. This includes controlling the backing of sections of guest memory…
2688 - `cloud-hypervisor` no longer panics when started with `--memory hotplug_method=virtio-mem` and no…
2689 - After a reboot memory can remove when using `--memory hotplug_method=virtio-mem` (#1593)
2741 ### Virtio Memory Ballooning Support
2743 …ugh the `resize` control, which allows the reclamation of host memory by resizing a memory balloon…
2882 ### Block, Network, Persistent Memory (PMEM), VirtioFS and Vsock hotplug
2907 be loaded into the guest memory to be used as the kernel initial filesystem.
2912 ### Alternative Memory Hotplug: `virtio-mem`
2916 `hotplug_method` parameter on the `--memory` command line option. It currently
2936 * Use `--memory`'s `shared` and `hugepages` controls for determining backing
2937   memory instead of providing a path.
2943   shared memory is in use if any attempt is made to used a `vhost-user` backed
2982 resources. After adding support for CPU and memory hotplug, Cloud Hypervisor
3046 * Prevent memory overcommit via virtio-fs (#763) - Sebastien Boeuf
3058 memory hot plug as well. This allows to dynamically resize Cloud Hypervisor
3060 The memory hot plug implementation is based on the same framework as the CPU hot
3123 hot plug framework to other resources, namely PCI devices and memory.
3224 ### Memory mapped virtio transport
3249 ### Large memory guests
3252 support guests with large amount of memory (more than 64GB).
3288 enabling VT-d through the KVM and VFIO APIs, our guest memory writes and reads
3289 were (in many cases) not cached. After correctly tagging the guest memory from
3295 We added shared memory region with [DAX](https://www.kernel.org/doc/Documentation/filesystems/dax.t…
3298 memory footprint.
3335 ### Virtual persistent memory
3337 The `virtio-pmem` implementation emulates a virtual persistent memory device
3339 allows to bypass the guest page cache and improve the guest memory footprint.