OpenVZ Forum - RDF feed
type: channel
items: Setting RAM
items: Re: Setting RAM

Setting RAM
type: item
description: I'm a bit confused when it comes to setting the max usable RAM for a single VPS. I think the correct setting is privvmpages=x What I'm confused about is the value of x if I wanted to set 128MB max usable RAM. Thank you.
creator: devnu11
date: 2005-09-23T04:22:25-00:00

Re: Setting RAM
type: item
description: Setting user beancounter parameters is an advanced task (described in soon-to-be-released SLM Guide). Basically, all the parameters are inter-dependant and you can not just change one parameter and hope it will work. So you'd better stick to existing config samples, or at least use vzcfgvalidate to check your new config for validity. And yes, privvmpages parameter's unit is pages. On ix86 architecture a page is equal to 4096 bytes, or 4 kilobytes.
creator: kir
date: 2005-09-23T08:17:30-00:00

Re: Setting RAM
type: item
description: After reading the section on managing system parameters in OpenVZ-Users-Guide.pdf I'm unclear if I want --physpages or --privvmpages What I want to do is for example make a VPS with a minimun of 128 MB of usable RAM. If I tell someone they have 128 MB of RAM at minimum or maximum (not sure if I understand how OVZ does this) which do I set to 32768 if this is the correct number?
creator: devnu11
date: 2005-10-05T20:58:54-00:00

Re: Setting RAM
type: item
description: use --oomguarpages param
creator: dim
date: 2005-10-06T08:11:14-00:00

Re: Setting RAM
type: item
description: All of the UBC parameters are explained and discussed in great details in yet-to-be-released OpenVZ SLM Guide. Below is an except describing the meaning of privvmpages, physpages, vmguarpages and oomguarpages. Finally, make sure you are checking each VPS configuration you create using vzcgfvalidate(8) utility. Quote: vmguarpages: memory allocation guarantee. This parameter controls how much memory is available to the Virtual Private Server (i.e. how much memory its applications can allocate by malloc(3) or other standard Linux memory allocation mechanisms). The more clients are served or the more "heavy" the application is, the more memory it needs. The amount of memory that Virtual Private Server's applications are guaranteed to be able to allocate is specified as the barrier of vmguarpages parameter. The current amount of allocated memory space is accounted into privvmpages parameter, and vmguarpages parameter does not have its own accounting. The barrier and the limit of privvmpages parameter impose an upper limit on the memory allocations. The meaning of the limit for the vmguarpages parameter is unspecified in the current version and should be set to the maximal allowed value (2147483647). If the current amount of allocated memory space does not exceed the guaranteed amount (the barrier of vmguarpages), memory allocations of Virtual Private Server's applications always succeed. If the current amount of allocated memory space exceeds the guarantee but below the barrier of privvmpages, allocations may or may not succeed, depending on the total amount of available memory in the system. Starting from the barrier of privvmpages, normal priority allocations and, starting from the limit of privvmpages, all memory allocations made by the applications fail. The memory allocation guarantee (vmguarpages) is a primary tool for controlling the memory available to Virtual Private Servers, because it allows administrators to provide Service Level Agreements -- agreements guar…
creator: kir
date: 2005-10-06T08:28:32-00:00

Re: Setting RAM
type: item
description: Also, this thread in swsoft's forum might me useful.
creator: kir
date: 2005-10-10T08:25:02-00:00