<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:10.0pt;
font-family:"Aptos",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-GB" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US">Hi Michael,<o:p></o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt"><br>
> I tried changing the CPU units on one of my CTs on 6109R Aventurine and <br>
> when I save it throws big red errors for numiptent_l and numproc_l <br>
> although I haven’t changed those.<br>
<br>
Yeah, the saving of the parameters sometimes goes off the rails. This is <br>
due to the way how they are calculated may not coincide with maximums <br>
that are actually allowed due to hardware limitations.<br>
<br>
To make sure that one or two of such glitches don't interfere with <br>
saving changes they various parameters are saved individually or in <br>
small groups, so that most changes still go through even if there is an <br>
error in one or two subsidiary parameters.<br>
<br>
"numpitent" is the limit for individual firewall rules.<br>
"numproc" is the limit for the amount of processes a CT might have.<br>
<br>
2K firewall rules might be to small or too big. Hard to say.<br>
131K processes sure is big.<br>
<br>
But here is the thing: These are probably set to "unlimited" anyway. In <br>
the past in older OpenVZ versions you HAD to configure every bloody <br>
parameter to at least some value and that often then went off the rails. <br>
Even the OpenVZ guys eventually realized that this was overkill and <br>
allowed many of the more nonsensical parameters to be set to unlimited. <br>
Or have them default to unlimited when they aren't configured <br>
explicitly. But even there: There is no value "unlimited" that you can <br>
use. As far as the config files go it's still a number and how big that <br>
number is depends on your hardware specs. Which makes it totally <br>
unintuitive and even more complicated to set it correctly.<br>
<br>
> I think this may have something to do with the settings having<br>
> Unlimited (with a capital U) rather than unlimited (lower case)<br>
<br>
Yes and no. The code handles both "Unlimited" and "unlimited" and then <br>
tries to determine what the maximum number that's allowed might be and <br>
tries to set that. And that "guess" is probably wrong for both <br>
parameters. Either way: You can ignore "numiptent" and "numproc", as the <br>
way they are configured now is as close to unlimited as it might get on <br>
your end of things.<br>
<br>
> Looking at the vz conf file for the CT it seems to have applied the<br>
> increased cpuunits but the settings for physpages and swappages don’t<br>
> seem right (should be 8G and 4G)?<br>
<br>
The values for RAM and Swap are stored in pages, not gigabytes. There <br>
also isn't a singular parameter for RAM, as that is broken down into <br>
various subtypes.<br>
<br>
You can try to set 8GB RAM and 2GB swap from the command line like this:<br>
<br>
prlctl set <VPSID> --memsize 8GB --swap 2GB<br>
<br>
That will set and write out the correct limits for memory and swap. It <br>
will break it down automatically to create the correct settings for the <br>
associated memory related parameters such as physpages, lockedpages, <br>
shmpages, privvmpages and vmguarpages.<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks – that all makes sense.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I will ignore the errors. :0)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">All the best<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Colin<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>