The additional GB: perhaps you increased the memory capacity on the VM, but live resizing is not supported? You may need to turn the machine off and turn it back on. Setting the correct virtual hardware can allow you to live add memory, depending on your guest OS.
I don’t think this is true. Hardware properties go via the compute resources, in this case talking directly to VMware API. Reported data is extracted from facts, which comes from sources such Ansible, Puppet, or RHSM.
To be able to add CPU/Memory on the fly in VMware, when you make the VM, you want to drop down both the CPU and Memory dropdown and make sure the check boxes are selected for:
CPU Hot Plug
Memory Hot Plug
You will need to power off the VM, check those boxes and power it up, after that you should be able to add more CPU/Ram on the fly. Each OS has a limit of how much can be added so it does not cause a crash with the Kernel or in Windows.
None of my hosts are provisioned by Foreman, only added to Foreman after the fact using the “Register Host” curl command. Tried to look for a pattern comparing HW properties to OS but it seems for some hosts it is correct but for most it is either 1 GB wrong or totally wrong like 257 GB instead of configured 16 GB and for some all that information is totally empty.
The issue is only for VM’s running in VMware. Have 100+ VM’s using AHV (Nutanix) as hypervisor and all of them are good.
If I register a server with 1 GB of RAM, 1 GB of RAM is shown in “HW properties”.
If I register a server with 2 GB of RAM, 2 GB of RAM is shown in “HW properties”.
If I register a server with 4 GB of RAM, 5 GB of RAM is shown in “HW properties”.
If I register a server with 8 GB of RAM, 9 GB of RAM is shown in “HW properties”.