On Mon, 2023-02-13 at 18:22 +0700, Lazuardi Nasution wrote:
Hi,
There is a weird situation if it is not a bug.
Its not a bug hw_mem_page_size can be used in the image only if hw:mem_page_size=larage or hw:mem_page_size=any in the case of hw:mem_page_size=large the image can be used to choose a speccific hugepage size hw:mem_page_size=large hw_mem_page_size=1G hw:mem_page_size=any will by default be the same as hw:mem_page_size=small and use the smallest pagezise which is typically 4k. the differnece bettwen hw:mem_page_size=any and hw:mem_page_size=small is hw:mem_page_size=any allows the image to set any value for hw_mem_page_size. so hw:mem_page_size=any and hw_mem_page_size=large is valid where as hw:mem_page_size=small and hw_mem_page_size=large is not and will raise an error. when hugepage support was added it was decided that permission form the operator was required to allow you to request hugepages via the image which is why the flavor must have and hw_mem_page_size=large|any set.
Hugepage instance launching is working if I put hw:mem_page_size on the used flavor. But, when I try the same launching configuration and change hw:mem_page_size on used flavor to hw_mem_page_size on used image, it cannot work as expected. It seems that this issue is like on https://bugzilla.redhat.com/show_bug.cgi?id=1791132, but it still happens on Zed. Is this an old bug? Should I submit a bug report for this? no we cloased https://bugzilla.redhat.com/show_bug.cgi?id=1791132 as not a bug because they were not aware of this requriement.
Best regards.