We have encountered this in a deployment using reserved hugepages.
350 1G pages were reserved, leaving 22G for hypervisor processes.
Around 14G of this was consumed by metadata-api processes which in combination with the other system processes was leaving little free memory and resulting in memory fragmentation.
The outcome was that qemu was unable to allocate order 6 pages when launching VMs (which were to be backed by hugepages).
I expect in setups using reserved hugepages the effects of this bug would be more pronounced and occur more often.
We have encountered this in a deployment using reserved hugepages.
350 1G pages were reserved, leaving 22G for hypervisor processes.
Around 14G of this was consumed by metadata-api processes which in combination with the other system processes was leaving little free memory and resulting in memory fragmentation.
The outcome was that qemu was unable to allocate order 6 pages when launching VMs (which were to be backed by hugepages).
I expect in setups using reserved hugepages the effects of this bug would be more pronounced and occur more often.