vzquota taking 1.2GB of actual memory upon startup [message #32755] |
Thu, 28 August 2008 07:07  |
vztester
Messages: 19 Registered: August 2008
|
Junior Member |
|
|
I have two hosts and one host when I start the only VE which 128MB of RAM it won't start and vzquota starts and takes 1.2gb of RAM.
Then I get this error when manually trying to start the VE:
Received signal: 9 in /usr/sbin/vzquota
Received signal: 9 in /usr/sbin/vzquota
Does anyone have an idea why it does this?
rtt
|
|
|
|
Re: vzquota taking 1.2GB of actual memory upon startup [message #32777 is a reply to message #32755] |
Thu, 28 August 2008 22:45   |
vztester
Messages: 19 Registered: August 2008
|
Junior Member |
|
|
Started by:
vzctl start VEID
The messages that appeared are the ones mentioned:
Received signal: 9 in /usr/sbin/vzquota
Received signal: 9 in /usr/sbin/vzquota
Actually as soon as OpenVZ is started it tries taking up all available RAM.
I'll shed some more light, which may help.
One system is running 2Gigs of RAM, the VE starts fine on that (the VE itself is allocated on 128MB of RAM).
The system the problem is happening on, has 1.5 Gigs of RAM and the config files for OpenVZ are the same on both machines.
Is there some configuration option that makes OpenVZ try to allocate all the available memory it can? It seems this is what is happening.
As soon as OpenVZ starts it takes 1.2 -1.3 gigs of resident memory and the system swaps like crazy.
Any help would be appreciated
rtt
|
|
|
Re: vzquota taking 1.2GB of actual memory upon startup [message #32778 is a reply to message #32777] |
Thu, 28 August 2008 22:48   |
vztester
Messages: 19 Registered: August 2008
|
Junior Member |
|
|
From vzctl.log:
2008-08-28T15:35:44-0700 vzctl : Setting CPU units: 1000
2008-08-28T15:35:44-0700 vzctl : WARNING: Settings were not saved and will be re setted to original values on next start (use --save flag)
2008-08-28T15:35:44-0700 vzctl : VE 1001 : Starting VE ...
2008-08-28T15:37:33-0700 vzctl : VE 1001 : Received signal: 9 in /usr/sbin/vzqu ota
2008-08-28T15:39:18-0700 vzctl : VE 1001 : Received signal: 9 in /usr/sbin/vzqu ota
2008-08-28T15:39:19-0700 vzctl : VE 1001 : vzquota on failed [3]
2008-08-28T15:42:33-0700 vzctl : Setting CPU units: 1000
2008-08-28T15:42:33-0700 vzctl : WARNING: Settings were not saved and will be re setted to original values on next start (use --save flag)
2008-08-28T15:42:33-0700 vzctl : VE 1001 : Starting VE ...
2008-08-28T15:44:15-0700 vzctl : VE 1001 : Received signal: 9 in /usr/sbin/vzqu ota
2008-08-28T15:46:02-0700 vzctl : VE 1001 : Received signal: 9 in /usr/sbin/vzqu ota
2008-08-28T15:46:02-0700 vzctl : VE 1001 : vzquota on failed [3]
rtt
|
|
|
|
Re: vzquota taking 1.2GB of actual memory upon startup [message #32811 is a reply to message #32785] |
Mon, 01 September 2008 05:55   |
vztester
Messages: 19 Registered: August 2008
|
Junior Member |
|
|
I think this shows there is a lack of compatibility and it is also kind of my fault.
One OS is Centos 4.6 64-bit kernel.
The other is Centos 5.2 with 32-bit kernel.
VEs created in 64bit kernel's will not work on the 32 bit host and vice versa, that's when I get the memory usage error and also the other error messages.
Is this the normal behaviour for OpenVZ?
I also tried using 64bit and i386 vzctl and vzquota with the same results.
I've also received errors like this (even though the VE worked previously, if you start it on a different host it doesn't work):
vzctl start 1001
Starting VE ...
vzquota : (warning) block_hard_limit [1153124] < block_current_usage [4194273]
vzquota : (error) path to mount point can't be read from config file,
use -p <mount_point> option
vzquota on failed [13]
======================
I can also say everything is fine with pure i386 HN's.
It seems that 64bit and 32bit HN's create containers that are not compatible.
rtt
|
|
|
|
Re: vzquota taking 1.2GB of actual memory upon startup [message #32838 is a reply to message #32755] |
Mon, 01 September 2008 21:45  |
vztester
Messages: 19 Registered: August 2008
|
Junior Member |
|
|
Hi maratrus
VE's were created with vzctl command, migration was not done with the utilities though.
I meant I hoped that a 32-bit VE could be used in a 64-bit HN with 32-bit.
I think you are correct that 32-bit utilities on a 64-bit HN are not really compatible.
Might it be possible in the future for more compatibility?
At least now I know why the strange behaviour and errors happened.
rtt
|
|
|