[SOLVED] openvz vzcalc strange output

zeshanuk · 05-29-2015, 02:20 AM

hi i have made a conf file for a container 1G RAM and 2G SWAP:

Code:

# Configuration file generated by vzsplit for 24 containers
# on HN with total amount of physical memory 32156 Mb,
# low memory 32156 Mb, swap size 0 Mb, max threads 16000.
# Resource commit level 0:
# Free resource distribution. Any parameters may be increased

# This is VSwap-enabled configuration
# NOTE this configuration needs OpenVZ kernel 042stab042 or newer!

PHYSPAGES="0:262144"
SWAPPAGES="0:524288"

KMEMSIZE="unlimited"
DCACHESIZE="unlimited"
LOCKEDPAGES="unlimited"
PRIVVMPAGES="unlimited"
SHMPAGES="unlimited"
NUMPROC="unlimited"
VMGUARPAGES="0:unlimited"
OOMGUARPAGES="0:unlimited"
NUMTCPSOCK="unlimited"
NUMFLOCK="unlimited"
NUMPTY="unlimited"
NUMSIGINFO="unlimited"
TCPSNDBUF="unlimited"
TCPRCVBUF="unlimited"
OTHERSOCKBUF="unlimited"
DGRAMRCVBUF="unlimited"
NUMOTHERSOCK="unlimited"
NUMFILE="unlimited"
NUMIPTENT="unlimited"

DISKSPACE="108598924:119458817"
DISKINODES="3425169:3767687"
CPUUNITS="1000"
VE_ROOT="/var/lib/vz/root/$VEID"
VE_PRIVATE="/var/lib/vz/private/$VEID"
OSTEMPLATE="debian-7.0-x86_64"
ORIGIN_SAMPLE="splitfile"

However when i run vzcalc:

Quote:

vzcalc -v 128

i get:

Code:

root@server1:~# vzcalc -v 128
Resource     Current()  Promised(%)  Max(%)
Low Mem           n/a 341925155979.32 341925155979.32
Total RAM         n/a        n/a        n/a
Mem + Swap        n/a 45031732669.26        n/a
Alloc. Mem        n/a 45031732669.26 36935027135323.63
Num. Proc         n/a        n/a 1793617297383632.75
--------------------------------------------
Memory            n/a 341925155979.32 1793617297383632.75

Why are the values so large and Total RAM n/a? I have been thinking about it for ages and have no idea. can anyone help me?

I know low mem is not relevant for my arch x86_64 so not worried about that but the other rows all concern me.

wpeckham · 05-29-2015, 06:28 AM

I find OpenVZ facinating, and one of the most useful tools. If only they had a kernel install set for RHEL7 and kernel version 4!

This is a bit off the cuff, as I have NOT looked it up, but...

In newer OpenVZ containers (ploop based) with most settings not needed at all (but defaulting to 'unlimited', the numbers should be based upon the capacity of the hardware. If you check the /proc/user_beancounters for container 0 (the host) you will see huge numbers much like those. It makes sense also that some limits are now N/A because there is no limit to apply: the limit is the hardware limit.

I am still using about 60 containers using simfs on older platforms, and about 30 using ploop. I am finding a few oddities with the ploop containers, but no disadvantages. It does make some of the numbers less meaningful, and not only in vzstat.

Have you asked over on the OpenVZ site forum?

zeshanuk · 05-29-2015, 10:46 AM

hi wpeckham, thanks for your help. /proc/user_beancounters is the way to check inside the container how much ram is being allocated - physpages