As discussed here [1], for some types of environment it's important to allocate memory upfront. In such cases libvirt needs to reuse the paths. However, since we don't want to expose the paths anywhere, reversed approach is implemented. If enabled in config file, libvirt builds predictable paths for memory-backend-file. 1: https://www.redhat.com/archives/libvir-list/2017-October/msg01036.html As usual, you can also find all the patches on my github: https://github.com/zippy2/libvirt/tree/aliases_from_user_v2 (Why v2? Don't ask.) Michal Privoznik (5): conf: s/virDomainObjGetShortName/virDomainDefGetShortName/ qemu: Move memPath generation from memoryBackingDir to a separate function qemu.conf: Introduce memory_predictable_file_names qemuxml2argvtest: Test memory_predictable_file_names news: Document memory_predictable_file_names docs/news.xml | 10 ++ src/conf/domain_conf.c | 4 +- src/conf/domain_conf.h | 2 +- src/libvirt_private.syms | 2 +- src/qemu/libvirtd_qemu.aug | 1 + src/qemu/qemu.conf | 5 + src/qemu/qemu_command.c | 9 +- src/qemu/qemu_conf.c | 92 +++++++++++++- src/qemu/qemu_conf.h | 11 ++ src/qemu/qemu_domain.c | 4 +- src/qemu/qemu_driver.c | 21 ++- src/qemu/qemu_hotplug.c | 2 +- src/qemu/qemu_process.c | 141 +++++++++++++++------ src/qemu/qemu_process.h | 8 +- src/qemu/test_libvirtd_qemu.aug.in | 1 + .../qemuxml2argv-cpu-numa-memshared.args | 6 +- .../qemuxml2argv-fd-memory-numa-topology.args | 3 +- .../qemuxml2argv-fd-memory-numa-topology2.args | 6 +- .../qemuxml2argv-fd-memory-numa-topology3.args | 9 +- .../qemuxml2argv-hugepages-memaccess2.args | 9 +- tests/qemuxml2argvtest.c | 1 + 21 files changed, 279 insertions(+), 68 deletions(-) -- 2.13.6 -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
