PAE support inside VE [message #38621] |
Fri, 08 January 2010 08:56 |
eastitaly
Messages: 6 Registered: January 2010
|
Junior Member |
|
|
I've installed OpenVZ (64 bit kernel - CentOS 5.4) on some servers with 8+ GB of RAM.
I've also set up some VEs with a CentOS 5.4 32 bit template and all worked fine until now.
Now the avaiable memory needed for some VEs is increased (for traffic and load) and I need to allocate more than 4 GB for them.
I was wondering if the VE could use more than 4 GB of RAM, then I tried and got a positive answer.
The problem comes as the maximum memory available inside that container seems to be limited to exactly 4613120 Kb (as per /proc/meminfo), even if I try to set the VE's memory allocation to 5 or even 6 GB.
The kernel I'm using for the HN is 2.6.18-128.2.1.el5.028stab064.8 and I've checked the release notes for the subsequent releases and didn't find anything related to this problem.
Any hint?
|
|
|
|
|
|
|
|
|
|
|
[SOLVED] Re: PAE support inside VE [message #38686 is a reply to message #38621] |
Fri, 15 January 2010 09:48 |
eastitaly
Messages: 6 Registered: January 2010
|
Junior Member |
|
|
# Copyright (C) 2000-2008, Parallels, Inc. All rights reserved.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
#
ONBOOT="yes"
# UBC parameters (in form of barrier:limit)
KMEMSIZE="95000000:95000000"
LOCKEDPAGES="256:256"
PRIVVMPAGES="1310720:1310720"
SHMPAGES="21504:21504"
NUMPROC="880:880"
PHYSPAGES="0:9223372036854775807"
VMGUARPAGES="524288:9223372036854775807"
OOMGUARPAGES="26112:9223372036854775807"
NUMTCPSOCK="1000:1000"
NUMFLOCK="188:206"
NUMPTY="16:16"
NUMSIGINFO="384:384"
TCPSNDBUF="8800000:11360000"
TCPRCVBUF="10000000:12560000"
OTHERSOCKBUF="2831155:3752755"
DGRAMRCVBUF="330000:330000"
NUMOTHERSOCK="360:360"
DCACHESIZE="6446000:11520000"
NUMFILE="30000:30000"
AVNUMPROC="180:180"
NUMIPTENT="128:128"
# Disk quota parameters (in form of softlimit:hardlimit)
DISKSPACE="483183820:483183820"
DISKINODES="120795955:134217728"
QUOTATIME="0"
# CPU fair sheduler parameter
CPUUNITS="1000"
# Network customization section
CONFIG_CUSTOMIZED="yes"
VETH_IP_ADDRESS="aaa.aaa.aaa.aaa/bb"
VE_DEFAULT_GATEWAY="ccc.ccc.ccc.ccc"
BRIDGEDEV="br0"
NAMESERVER="ddd.ddd.ddd.ddd"
HOSTNAME="name.domain.tld"
NAME=""
DESCRIPTION=""
VE_ROOT="/vz/root/ct$VEID/data"
VE_PRIVATE="/vz/private/ct$VEID/data"
OSTEMPLATE="centos-5-i386-minimal"
ORIGIN_SAMPLE="vps.basic"
NETIF="ifname=eth0,bridge=br0,mac=xx:xx:xx:xx:xx:xx,host_ifname=veth101.0,host_mac=yy:yy:yy:yy:yy:yy"
QUOTAUGIDLIMIT="15000"
CAPABILITY="SYS_PACCT:on "
NOATIME="yes"
#DEVNODES="loop0:rw "
CPUS="4"
Found the MEMINFO option as you suggested, nuno.
I haven't ever set it, was an addition from an installation of HyperVM.
Removed it and all started magically work as expected.
This, btw, confirms that a 32 bit template is PAE-like enabled.
Thank you so much for addressing me to the right direction!
[Updated on: Fri, 15 January 2010 10:00] Report message to a moderator
|
|
|
Re: PAE support inside VE [message #38687 is a reply to message #38686] |
Fri, 15 January 2010 10:01 |
nuno
Messages: 43 Registered: January 2010
|
Member |
|
|
No problem.
Please note that those values are merelly information. You can define that to 1000 pages, /proc/meminfo will report 4MB of memory, free will report 0% free memory, etc, but your applications will continue to work. The reverse is also true: you can set a huge value and application will fail after exceeding kmemsize, vmguar* or some other limit.
|
|
|