棱镜显示器如何安装内存?

Prism中显示的主机内存容量为memTotalAHV虚拟化环境可使用的值。可以通过查看MemTotal列于猫/proc/meminfoAHV主机回显信息如下:

cat /proc/meminfo | grep MemTotal . exe

• 现在，即使这个文件中的MemTotal值在视觉上被提到为“kB”，但它实际上是根据Redhat文档的kibibytes -https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/deployment_guide/s2-proc-meminfo
• 因此，您可以将这个kibibytes值转换为Gigibytes值，这个值应该与在Prism web控制台中显示的主机内存容量相匹配

同样的内存容量值也可以在使用中找到自由- g命令输出(在GiB中显示内存值)查看AHV主机的Mem Total值。

自由- g

• 因为Mem Total值在上面的输出中直接显示在GiB中，所以你不需要再次将它转换为GiB -这个值应该与在Prism中看到的值相匹配。

按照proc内核文件时，MemTotal值之间存在差异猫/proc/meminfo或免费的命令输出与实际的物理内存安装在硬件节点上的原因MemTotal显示了总可用ram，即物理ram减去一些保留位和内核二进制代码。

对于实际物理内存内存内存值的计算，RAM内存容量总是以2的幂(1kib等于1024b)来衡量，所以32gb实际上就是32gib。它通常被称为GB，因为它比GiB更容易理解。因此，根据这个计算，在这个节点上实际上有32*12 = 384 GiB的物理RAM可用。

现在，在这个384 GiB的物理RAM中，有377.5 GiB的RAM可供AHV管理程序使用(这就是应该出现的情况)猫/proc/meminfo或免费的剩下的RAM被一些保留位和内核二进制代码使用。

我希望这有助于消除Prism web控制台中看到的主机内存容量值与节点中实际安装的物理内存之间的差异。

cat \/proc\/meminfo | grep MemTotal<\/code><\/pre>
Now even though the MemTotal\u00a0value in this file is visually mentioned as \u201ckB\u201d, however it is actually in\u00a0kibibytes\u00a0as per the Redhat documentation -\u00a0https:\/\/access.redhat.com\/documentation\/en-us\/red_hat_enterprise_linux\/6\/html\/deployment_guide\/s2-proc-meminfo<\/a><\/li>\t
So, you can convert this kibibytes values to Gigibytes and this value should match with what is shown under host\u2019s memory capacity in Prism web console\u00a0<\/li><\/ul>
The same memory capacity value can also be found using free -g<\/strong>\u00a0command output (shows memory values in GiB)<\/em>\u00a0on the AHV host and looking into the Mem Total value in it.<\/p>
free -g<\/code><\/pre>
Since Mem Total value is directly shown in GiB in the above output, you don\u2019t need to convert it to GiB again - this value should match to what is being seen in Prism.\u00a0\u00a0<\/li><\/ul>
As per the proc kernel doc<\/a>, there is a discrepancy between the MemTotal values seen in cat \/proc\/meminfo <\/em>or free<\/em>\u00a0command outputs versus to actual physical memory <\/em>installed on the Hardware node is because\u00a0MemTotal shows the<\/strong> Total usable ram which is Physical ram minus a few reserved bits and the kernel binary code.\u00a0<\/strong><\/p>
Regarding the actual\u00a0Physical memory DIMM value calculation, RAM Memory capacity\u00a0is always\u00a0measured in powers of two (1 KiB equals 1024 B), so 32 GB actually means 32 GiB. It is typically stated as GB because it is easier to understand as compared to GiB. Hence, based on this calculation, you actually have 32*12 = 384 GiB of physical RAM available on the node.<\/p>
Now from this 384 GiB of physical RAM, 377.5 GiB of RAM is available for use by the AHV hypervisor (which is what should come up in cat \/proc\/meminfo <\/em>or free<\/em>\u00a0command outputs as well) and remaining RAM is used by some reserved bits and kernel binary code.\u00a0<\/p>
\u00a0<\/p>
I hope this helps to clear the discrepancy between host memory capacity values seen in Prism web console versus to the actual physical memory installed in the node.\u00a0<\/p>
\u00a0<\/p>
\u00a0<\/p>","quoteUsername":"Nupur.Sakhalkar","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
            

             
就像
             
报价