From 572c2b18e27f6fcbbd4a1f416b0ec21098b3ba74 Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Wed, 3 Mar 2021 00:49:22 +0000 Subject: Add locked_memory extra spec and image property This change adds a new hw:locked_memory extra spec and hw_locked_memory image property to contol preventing guest memory from swapping. This change adds docs and extend the flavor validators for the new extra spec. Also add new image property. Blueprint: libvirt-viommu-device Change-Id: Id3779594f0078a5045031aded2ed68ee4301abbd --- .../notes/new_locked_memory_option-b68a031779366828.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 releasenotes/notes/new_locked_memory_option-b68a031779366828.yaml (limited to 'releasenotes') diff --git a/releasenotes/notes/new_locked_memory_option-b68a031779366828.yaml b/releasenotes/notes/new_locked_memory_option-b68a031779366828.yaml new file mode 100644 index 0000000000..72d6e763aa --- /dev/null +++ b/releasenotes/notes/new_locked_memory_option-b68a031779366828.yaml @@ -0,0 +1,13 @@ +--- +features: + - | + Add new ``hw:locked_memory`` extra spec and ``hw_locked_memory`` image + property to lock memory on libvirt guest. Locking memory marks the guest + memory allocations as unmovable and unswappable. + ``hw:locked_memory`` extra spec and ``hw_locked_memory`` image property + accept boolean values in string format like 'Yes' or 'false' value. + Exception `LockMemoryForbidden` will raise, if you set lock memory value + but not set either flavor extra spec + ``hw:mem_page_size`` or image property ``hw_mem_page_size``, + so we can ensure that the scheduler can actually account for this correctly + and prevent out of memory events. -- cgit v1.2.1