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