Do you mean the best way is to enable traditional hugepage memory only on virtual machines and turn off the default transparent hugepage memory on physical machines and without enabling traditional hugepage memory?
On 10/03/2021 04:03, Strahil Nikolov via Users wrote: vdsm supports dynamic allocation of Huge Pages, but https://access.redhat.com/solutions/4904441 indicates the issues in 4.3 related to hugepages (you can see the solution via RH dev subscription). If you needed to set them manually and everything works normally, I would have picked something like 90-95% in HugePages. Yet, due to the issues described in that solution - it's better to enable HugePages only in the Guest. Best Regards, Strahil Nikolov On Sat, Oct 2, 2021 at 10:13, Tommy Sway <sz_cui...@163.com> wrote: _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/CEXZE5QYTWWNMFQU5ASJR75IWOOIFYLJ/
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/KLHJDZMPLKPPXABYSP55DA472UPCKCDO/
