Submitted by pcfreak30 on Fri, 02/21/2014 - 19:31
Ive tested and it seems that somehow in some condition, no matter what is set for openvz_memory and openvz_guaranteed_memory, it defaults to unlimited.
Im not sure if it has to do with cloudmin caching the server data or not.
Status:
Active
Comments
Submitted by JamieCameron on Fri, 02/21/2014 - 19:48 Comment #1
Can you explain further what is going wrong here - is the memory limit within the VM incorrect? Or is it being displayed wrongly within Cloudmin ... and if so, on what page?
Submitted by pcfreak30 on Fri, 02/21/2014 - 19:50 Comment #2
Its being shown incorrectly in the resource limits page.
Submitted by JamieCameron on Sat, 02/22/2014 - 00:53 Comment #3
So the memory limit on that page is taken from the PRIVVMPAGES entry in the VM's OpenVZ config file. What is that set to for the problem system?
Submitted by pcfreak30 on Sat, 02/22/2014 - 14:47 Comment #4
its set to unlimited. Though it seems saving to guaranteed sets VMGUARPAGES and OOMGUARPAGES currently. However both data keys in the server .serv file have the right number.
Submitted by JamieCameron on Sat, 02/22/2014 - 16:02 Comment #5
The data keys in the .serv files are just a cache of memory limits, for faster access in some circumstances. When you visit the Resource Limits page, the actual limits from the .conf file should be loaded. For guaranteed memory, that is VMGUARPAGES
Submitted by pcfreak30 on Sat, 02/22/2014 - 17:05 Comment #6
what config property does type_openvz_get_guaranteed_memory use as I may have modified by mistake.
Submitted by JamieCameron on Sat, 02/22/2014 - 23:01 Comment #7
It reads
VMGUARPAGES