The issue will be fixed in future vSphere releases. Meanwhile, you can use the attached Hot Patch to this article "VMware-ESXi-7.0hp-19457183-depot.zip"
For more information about installing the Hot Patch , see “esxcli software vib” commands to patch an ESXi 6.x/7.x host (2008939)
Workaround:
To workaround this issue it is required to modify the VM memory configuration that the memory allocation code is satisfied and doesn't modify the NUMA memory map during pre-allocation.
To define and set (see picture edit VM setting) the correct VM memory configuration following procedure can get used:
The process is to divide the configured VM memory (see below picture) of the SAP HANA VM by the vSphere used memory segment size (32768). If the result is evenly divisible by 32768 and less than 512 then the algorithm won’t change the NUMA memory map and cause the experienced issue.
In addition to this, the VM advanced configuration parameter numa.memory.gransize = "32768" hast to get set in the “Configuration Parameters” section of the VM, see picture below:
To verify the correct memory configuration a customer can use the Intel® Memory Latency Checker* to and check the NUMA latency map. Any misaligned memory configurations will get detected by this check and would require changing the VM memory setting.
1st picture shows an example of a NUMA latency map with a misaligned VM memory value. The 2nd picture shows the NUMA map with an aligned memory setting.