On Fri, 11 Aug 2023 17:26:24 +0200 David Hildenbrand <da...@redhat.com> wrote:
[...] > Nowadays, "-mem-path" always defaults to MAP_PRIVATE. For the original > hugetlb use case, it's still good enough. For anything else, I'm not so > sure. We can deprecate -mem-path and direct users to use explicitly defined memory backend with legacy compatible example. That way users won't come back again trying to fix it or try inventing options to alter its behavior when using explicit '-machine memory-backend=foo' can do the job.