Re: FW: 64 bit Wheezy RAM Limitation
Stephen P. Molnar <s.molnar@sbcglobal.net> wrote:
> computation@debian:~$ free
> total used free shared buffers cached
> Mem: 4972636 1305880 3666756 0 86828 668240
> -/+ buffers/cache: 550812 4421824
> Swap: 10236924 0 10236924
> computation@debian:~$ dmesg | grep BIOS-e820
> [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
> [ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
> [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
> [ 0.000000] BIOS-e820: 0000000000100000 - 00000000dfff0000 (usable)
> [ 0.000000] BIOS-e820: 00000000dfff0000 - 00000000e0000000 (ACPI data)
> [ 0.000000] BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved)
> [ 0.000000] BIOS-e820: 0000000100000000 - 0000000158800000 (usable)
So the upper memory limit is 0x158800000 bytes, which equals 5779750912
bytes in decimal. Subtracting the reserved and ACPI data regions results
5242747904 bytes or 5119871 kbytes of usable memory. The kernel uses
some of that for itself (147235 kbytes in your case) and the rest is
usable for processes.
Now, the interesting part is: how much memory did you tell Virtualbox to
give to your VM? It is _not_ wise to use all memory the host has
available because this will then starve the host itself, rendering it
nearly unusable.
But this is no Wheezy (or Debian or Linux) problem, it is a VirtualBox
configuration issue.
Grüße,
Sven.
--
Sigmentation fault. Core dumped.
Reply to: