search for: 16384m

Hello All, I noticed that my CentOS 6.5 system reports that I only have about 10.9 GiB of RAM when I actually have 16384M. I have already tried adding mem=xxM to the end of the kernel line in grub.conf. The result is the same. Any suggestions? Joe

Hi, during some experiments with many guests I get crashing Dom0s because of too less memory. Actually the OOM killer goes ''round and kills random things, preferably qemu-dm''s ;-) The box in question has 128GB of memory, I start with dom0_mem=8192M (or 16384M, doesn''t matter). I also used "dom0_mem=8192M,min:1536M", but that didn''t make any difference. Xen is c/s 25688. Then I start some guests with 2GB each. This works fine until about 55 guests, then I get some denies from xl when starting guests (which would be OK). Bu...

...is 40 bytes more than twice what is set vsz_limit = 4096M says says OOM Error when trying to allocate 4294967336 bytes which is 40 bytes more than what is set vsz_limit = 8192M says says OOM Error when trying to allocate 17179869224 bytes which is 40 bytes more than twice what is set vsz_limit = 16384M says says OOM Error when trying to allocate 17179869224 bytes which is 40 bytes more than what is set everything set larger than 16384M stays at OOM Error when trying to allocate 17179869224... Replication itself seems to work but the error is always logged. # 2.3.4.1 (f79e8e7e4): /etc/dovecot...

...uncachable 3 disabled 4 disabled 5 disabled 6 disabled 7 disabled x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 original variable MTRRs reg 0, base: 0GB, range: 16GB, type WB reg 1, base: 16GB, range: 1GB, type WB reg 2, base: 3GB, range: 1GB, type UC total RAM covered: 16384M Found optimal setting for mtrr clean up gran_size: 64K chunk_size: 64K num_reg: 5 lose cover RAM: 0G New variable MTRRs reg 0, base: 0GB, range: 2GB, type WB reg 1, base: 2GB, range: 1GB, type WB reg 2, base: 4GB, range: 4GB, type WB reg 3, base: 8GB, range: 8GB, type WB reg 4, base: 16GB, ran...