OpenVZ Forum: Support » Can't enter a VE

Home » General » Support » Can't enter a VE

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Can't enter a VE [message #24517]

Wed, 05 December 2007 18:31

parf
Messages: 11
Registered: December 2007
Location: USA

Junior Member

[root@app-2 ~]# vzlist
VEID NPROC STATUS IP_ADDR HOSTNAME
202 9 running 10.1.1.202 -
[root@app-2 ~]# vzctl enter 202
Unable to fork: Resource temporarily unavailable

System is recently booted up Centos 5.0 w/o any load
there are also no load inside VE
System have more than enough resources (16gb ram 2*quad core x64)
VE is CentOS5
there are no messages in /var/log/messages

PS:
Stopping takes a long time ~2-3 min
when i restarted system i can get in VE

PPS:
~10 minutes after i start VE and try to get into it i receive a message:

[root@app-2 log]# vzctl enter 202
entered into VE 202
-bash: echo: write error: Cannot allocate memory
-bash: fork: Cannot allocate memory

where i can specify memory for VE?

[root@app-2 vz]# vzquota stat 202
resource usage softlimit hardlimit grace
1k-blocks 694088 1048576 1153434
inodes 24837 200000 220000

[Updated on: Wed, 05 December 2007 18:37]

Report message to a moderator