3.4. Configuring Compute nodes to use file-backed memory for instances
You can use file-backed memory to expand your Compute node memory capacity, by allocating files within the libvirt memory backing directory as instance memory. You can configure the amount of host disk that is available for instance memory, and the location on the disk of the instance memory files.
The Compute service reports the capacity configured for file-backed memory to the Placement service as the total system memory capacity. This allows the Compute node to host more instances than would normally fit within the system memory.
To use file-backed memory for instances, you must enable file-backed memory on the Compute node.
- You cannot live migrate instances between Compute nodes that have file-backed memory enabled and Compute nodes that do not have file-backed memory enabled.
- File-backed memory is not compatible with huge pages. Instances that use huge pages cannot start on a Compute node with file-backed memory enabled. Use host aggregates to ensure that instances that use huge pages are not placed on Compute nodes with file-backed memory enabled.
- File-backed memory is not compatible with memory overcommit.
You cannot reserve memory for host processes using
NovaReservedHostMemory. When file-backed memory is in use, reserved memory corresponds to disk space not set aside for file-backed memory. File-backed memory is reported to the Placement service as the total system memory, with RAM used as cache memory.
NovaRAMAllocationRatiomust be set to "1.0" on the node and any host aggregate the node is added to.
NovaReservedHostMemorymust be set to "0".
- Open your Compute environment file.
Configure the amount of host disk space, in MiB, to make available for instance RAM, by adding the following parameter to your Compute environment file:
parameter_defaults: NovaLibvirtFileBackedMemory: 102400
Optional: To configure the directory to store the memory backing files, set the
QemuMemoryBackingDirparameter in your Compute environment file. If not set, the memory backing directory defaults to
You must locate your backing store in a directory at or above the default directory location,
You can also change the host disk for the backing store. For more information, see Changing the memory backing directory host disk.
- Save the updates to your Compute environment file.
Add your Compute environment file to the stack with your other environment files and deploy the overcloud:
(undercloud)$ openstack overcloud deploy --templates \ -e [your environment files] \ -e /home/stack/templates/<compute_environment_file>.yaml
3.4.1. Changing the memory backing directory host disk
You can move the memory backing directory from the default primary disk location to an alternative disk.
Create a file system on the alternative backing device. For example, enter the following command to create an
# mkfs.ext4 /dev/sdb
Mount the backing device. For example, enter the following command to mount
/dev/sdbon the default libvirt memory backing directory:
# mount /dev/sdb /var/lib/libvirt/qemu/ram注記
The mount point must match the value of the