<div dir="ltr">Hi Stephen, <div><br></div><div>I've just tested in Virtualbox, same thing happened to CentOS but the loss is lesser than in AWS.</div><div><br></div><div>Both machines are allocated with 4096MB in Vagrantfile.</div><div><br></div><div>```</div><div><div>[vagrant@my-multi-centos-72 ~]$ cat /proc/meminfo</div><div>MemTotal: 3882384 kB</div><div>MemFree: 3527648 kB</div><div><br></div><div>vagrant@my-multi-ubuntu-1604:~$ cat /proc/meminfo</div><div>MemTotal: 4046708 kB</div><div>MemFree: 3695204 kB</div></div><div dir="ltr"><div><div>```</div><div><br></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Aug 1, 2016 at 8:29 PM Stephen John Smoogen <<a href="mailto:smooge@gmail.com" target="_blank">smooge@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 1 August 2016 at 07:30, Dũng Trần-Dương <<a href="mailto:chris.duong83@gmail.com" target="_blank">chris.duong83@gmail.com</a>> wrote:<br>
> Hi,<br>
><br>
> I launched an AWS instance `t2.medium` (use CentOS 7 image "ami-7abd0209",<br>
> product code: <a href="https://aws.amazon.com/marketplace/pp/B00O7WM7QW" rel="noreferrer" target="_blank">https://aws.amazon.com/marketplace/pp/B00O7WM7QW</a>), which is<br>
> supposed to have 4GB Memory in total, but turn out it is only "3.5GB".<br>
><br>
<br>
A rough guess would be that the system has reserved some memory for<br>
crashkernel but that is a guess. I would look at /proc/commandline to<br>
see what the kernel is starting up with.<br>
<br>
<br>
--<br>
Stephen J Smoogen.<br>
_______________________________________________<br>
CentOS-virt mailing list<br>
<a href="mailto:CentOS-virt@centos.org" target="_blank">CentOS-virt@centos.org</a><br>
<a href="https://lists.centos.org/mailman/listinfo/centos-virt" rel="noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/centos-virt</a><br>
</blockquote></div></div></div></div>