kvm: add support for persistent hugepages #1604
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a reworked version of #1327, where I tried to address some of @apoikos 's concerns and cater to a few more use cases that are important to my organization.
Like the rest of my PRs, this is messy, ugly, hacky, and probably doesn't merit a review yet, but since it "mostly works", I thought I'd give it a go for some feedback.
Compared to my previous PR, there is now an option to start the VM with regular memory-backed RAM if not enough hugepages are available on the host. There's also a flag to make this strict, and another flag to perform NUMA optimizations, which is the most important feature of this patch to our use case.
I'll try to provide more information on this patch in the next couple of weeks here.