Stephen Finucane 9d3ebd58aa libvirt: Don't allow "reserving" file-backed memory ... When file-backed memory is configured, it is the only "memory" reported by nova and used by instances, with RAM used in caching capacity. We should be warning users of this and insisting they explicitly configure the '[DEFAULT] reserved_host_memory_mb' config option to 0. However, doing so now would be breaking change. Instead, start logging a warning instead, failing only for the truly broken combination of reserving more file-backed memory than we have allocated. Change-Id: I9619338ad0f60253b628d96543f8ce3ac86242e3 Signed-off-by: Stephen Finucane <stephenfin@redhat.com> Closes-Bug: #1882821 (cherry picked from commit 3b99747b42)		2020-06-30 15:42:10 +00:00
..
_extra	Remove 'nova-xvpvncproxy'	2019-12-23 14:20:28 +00:00
_static	docs: Remove a whole load of unused images, most remainder	2019-10-02 17:36:21 +01:00
admin	libvirt: Don't allow "reserving" file-backed memory	2020-06-30 15:42:10 +00:00
cli	Add nova-status upgrade check and reno for policy new defaults	2020-05-04 18:33:37 +00:00
common	Deprecate CONF.workarounds.enable_numa_live_migration	2019-09-12 17:34:34 -04:00
configuration	Add docs and releasenotes for BP policy-defaults-refresh	2020-04-23 02:06:06 +00:00
contributor	[Trivial] FUP: addressed comments in support non-admin filter instances	2020-04-10 09:17:48 +00:00
install	Add nova-status upgrade check and reno for policy new defaults	2020-05-04 18:33:37 +00:00
reference	doc: Fix term mismatch warnings in glossary	2020-04-12 13:06:49 +09:00
user	docs: Add stable device rescue docs	2020-04-21 10:54:18 +01:00
conf.py	docs: Add documentation for flavor extra specs	2020-04-08 13:20:15 +00:00
index.rst	[Community goal] Update contributor documentation	2020-03-25 12:01:37 +00:00