feat: Enable explicit hugepages for the GuestVM#9027
Merged
frankdavid merged 2 commits intomasterfrom Feb 25, 2026
Merged
Conversation
Using hugepages helps the host reduce the work of managing the memory pages of the QEMU process. The host already uses transparent huge pages, but the amount of hugepages fluctuates quite a bit during the lifetime of the VM (anywhere between 20-95% of the QEMU's process memory is backed by hugepages). Using explicit hugepages should give more consistent behavior across nodes. The downside: - The Host must allocate the hugepages during startup, this adds ~30 seconds to the Host startup. - QEMU allocates hugepages eagerly during startup, this adds ~5 seconds to the startup time of the Guest VM. However, we save on the QEMU process cleanup time which can be anywhere between 30s and 100s.
Bownairo
approved these changes
Feb 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Using hugepages helps the host reduce the work of managing the memory pages of the QEMU process. The host already uses transparent huge pages, but the amount of hugepages fluctuates quite a bit during the lifetime of the VM (anywhere between 20-95% of the QEMU's process memory is backed by hugepages). Using explicit hugepages should give more consistent behavior across nodes. We only enable hugepages for non-SEV nodes because the Linux kernel does not support hugepages yet for VMs with encrypted memory.
The downside: