OpenVZ Forum


Home » Mailing lists » Users » vswap question - physpages/oomguarpages
vswap question - physpages/oomguarpages [message #46881] Thu, 21 June 2012 04:44 Go to next message
Rene Dokbua is currently offline  Rene Dokbua
Messages: 24
Registered: May 2012
Junior Member
I just noticed a couple of containers on one of our vswap enabled servers
have non-zero failcnt's (user_beancounters)

uid resource held maxheld
barrier limit failcnt
1413:
physpages 84873 131166
0 131072 61
oomguarpages 94628 377952
0 9223372036854775807 4
1409:
physpages 52986 262155
0 262144 1378
oomguarpages 57155 376725
0 9223372036854775807 18

(I've deleted lines with zero failcnt for clarity)

It was my understanding that if a vswap enabled container try to use more
physpages than available it would start "vswapping" - is that what happens
here? Otherwise how can physpages fail? Is this normal swapping behavior
or a problem?

A second thing is, when I tried to raise the physpages value with vzctl it
again wrote the old "block" values into the vz conf files, i.e.

i.e. before running vzctl the values are like this:
< PHYSPAGES="0:512M"
< SWAPPAGES="0:1024M"

after running vzctl --set 1413 --save --ram 512M --swap 1G the values are
like this:
> PHYSPAGES="0:131072"
> SWAPPAGES="0:262144"

I already opened a bug report on this and I though it had been fixed
already. Is there some undocumented flag that needs to be provided to
vzctl to get it to write out the values in the easy human readable format?

Regards,
Rene
Re: vswap question - physpages/oomguarpages [message #46883 is a reply to message #46881] Thu, 21 June 2012 05:37 Go to previous messageGo to next message
Kirill Korotaev is currently offline  Kirill Korotaev
Messages: 137
Registered: January 2006
Senior Member
I guess it means oom, i.e. out of memory killer had to kill someone since vswap+ram was not enough...

Sent from my iPhonespam SPAMSPAM

On 21.06.2012, at 8:58, "Rene C." <openvz@dokbua.com> wrote:

>
> I just noticed a couple of containers on one of our vswap enabled servers have non-zero failcnt's (user_beancounters)
>
> uid resource held maxheld barrier limit failcnt
> 1413:
> physpages 84873 131166 0 131072 61
> oomguarpages 94628 377952 0 9223372036854775807 4
> 1409:
> physpages 52986 262155 0 262144 1378
> oomguarpages 57155 376725 0 9223372036854775807 18
>
> (I've deleted lines with zero failcnt for clarity)
>
> It was my understanding that if a vswap enabled container try to use more physpages than available it would start "vswapping" - is that what happens here? Otherwise how can physpages fail? Is this normal swapping behavior or a problem?
>
> A second thing is, when I tried to raise the physpages value with vzctl it again wrote the old "block" values into the vz conf files, i.e.
>
> i.e. before running vzctl the values are like this:
> < PHYSPAGES="0:512M"
> < SWAPPAGES="0:1024M"
>
> after running vzctl --set 1413 --save --ram 512M --swap 1G the values are like this:
> > PHYSPAGES="0:131072"
> > SWAPPAGES="0:262144"
>
> I already opened a bug report on this and I though it had been fixed already. Is there some undocumented flag that needs to be provided to vzctl to get it to write out the values in the easy human readable format?
>
> Regards,
> Rene
>
> <ATT00001.c>
Re: vswap question - physpages/oomguarpages [message #47003 is a reply to message #46881] Tue, 26 June 2012 19:16 Go to previous message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member

On 06/21/2012 08:44 AM, Rene C. wrote:
> A second thing is, when I tried to raise the physpages value with
> vzctl it again wrote the old "block" values into the vz conf files, i.e.
>
> i.e. before running vzctl the values are like this:
> < PHYSPAGES="0:512M"
> < SWAPPAGES="0:1024M"
>
> after running vzctl --set 1413 --save --ram 512M --swap 1G the values
> are like this:
> > PHYSPAGES="0:131072"
> > SWAPPAGES="0:262144"
>
> I already opened a bug report on this and I though it had been fixed
> already.

A bug report is a bug report. It have status, and whenever something
about the bug changes, it is usually reflected in the bug report.

> Is there some undocumented flag that needs to be provided to vzctl to
> get it to write out the values in the easy human readable format?

I have replied in that bug report. vzctl was never doing this (ie it was
always saving parameters in simple numeric form, without any suffixes).
More to day, doing it right requires non-trivial changes, so I set this
bug severity to be enhancement.


Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png
Previous Topic: Netstat on Deb ovz vs Deb Proxmox
Next Topic: funtoo openvz images fails to work with &quot;vzctl enter&quot;
Goto Forum:
  


Current Time: Thu Dec 01 19:51:30 GMT 2022

Total time taken to generate the page: 0.01990 seconds