Hello Team, We noticed the same Behavior, We ended reducing the Huge pages, as I have had 512GB RAM on Huge pages, and the systems did not allocate any of that to the VM. It use the Unallocated Space, Showing Used Memory on the server as the Hughe Pages+ the VMs assigned memory - our VMs uses from 16GB to 512GB of RAM and makes this noticeable.
Tata Y. > On Jul 27, 2025, at 7:13 AM, akrasnov-drv (via GitHub) <g...@apache.org> > wrote: > > > GitHub user akrasnov-drv edited a comment on the discussion: Support for > hugepages in KVM VMs > > First of all I did not manage to add it via extraconfig, because CS blocks > it. > CS wrote for that extraconfig that hugepages are supported only for DPDK. > > But that's not the main issue. I can add hugepages block via hook. The issue > is that CS checks free memory in host without considering hugepages. If I > have 256Gb of RAM and set 240Gb to be in huge pages, CS rejects to start 32Gb > VM on that host, even if all hugepages are free and VM should use hugepages. > And opposite, if it fills all hugepages, but still there are some regular > memory, CS thinks there is space for more VMs but actually there is no. I > could possibly solve this issue by adding some reserved memory to CS config, > but there is just single percent value that should match all hosts. > In any case, making CS to recognize and. use hugepages (as I wrote in the > description) would be a proper solution. > > GitHub link: > https://github.com/apache/cloudstack/discussions/11187#discussioncomment-13860876 > > ---- > This is an automatically sent email for users@cloudstack.apache.org. > To unsubscribe, please send an email to: > users-unsubscr...@cloudstack.apache.org >
