Editing UBC primary parameters
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 91: | Line 91: | ||
(see [[privvmpages]]). The meaning of the <code>limit</code> for the | (see [[privvmpages]]). The meaning of the <code>limit</code> for the | ||
<code>vmguarpages</code> parameter is unspecified in the current version and should be set | <code>vmguarpages</code> parameter is unspecified in the current version and should be set | ||
− | to the maximal allowed value ([[ | + | to the maximal allowed value ([[MAX_ULONG]]). |
If the current amount of allocated memory space does not exceed the | If the current amount of allocated memory space does not exceed the | ||
Line 114: | Line 114: | ||
and the swap space — as discussed in [[UBC systemwide configuration]]. | and the swap space — as discussed in [[UBC systemwide configuration]]. | ||
− | There is a | + | There is a tool - <code>[http://en.dklab.ru/lib/dklab_vzmem/ vzmem]</code> - which allows you to distribute physical memory among all VEs consistently. It shows all the physical memory blocks graphically in /etc/vz/conf/MEM-MAP text file and lets you to move these blocks from one VE to another to redistribute the memory. Also you may specify "additional" memory personally for each VE: such memory will be obtained from system's free memory or swap (it is reflected as modifying of <code>privvmpages</code> parameter). |