it's quite easy:
[root@dhcp0-95 ~]# cat /proc/vz/vestat
Version: 2.2
VEID user nice system uptime idle strv uptime used maxlat totlat numsched
100 1634 0 1712 343011435 1277332114762816 0 638679179771038 16971458021 4921 5633592426 145722
1 157635 0 29103 488618806 1818929923633445 0 909796661898187 512196984005 4858 50362877628 2524559
101 759 0 1844 488627361 1819537209544684 0 909812591751777 33663331702 4529 10257230389 713559
103 765 0 1468 488628230 1819533866071061 0 909814208459884 28408677122 5117 11686660006 712016
105 4522 0 5088 488628270 1819572969105220 0 909814283772065 22621645151 4949 7557632985 125350
- column 1 "VEID": VE id
- column 2 "user", 3 "nice", 4 "system", 5 "uptime" - corresponding std user/nice/system/uptime values in jiffies to standalone linux /proc/stat. Note, there is no "idle" time here, since it can't be calculated this way.
the next group comes in cycles units:
- column 6 "idle" - idle time, 7 "strv" - not used, 8 "uptime" - uptime in cycles, 9 "used" - used time by VE across all CPUs in cycles
the next group is scheduling latency statistics in cycles:
- column 10 "maxlat" - max latency in cycles meaning how long VE process has to wait before it actually got CPU time.
- column 11/12 "totlat/numsched", i.e. divide 11 on 12 to get average scheduling latency.
you can also read:
[root@dhcp0-95 ~]# cat /proc/vz/stats
Version: 2.6
cycles_per_jiffy: 1860831
jiffies_per_second: 1000
to understand how many cycles and jiffies are per second.