Parallels Virtualization and Automation Software

RESOLUTION

1. VE starts but then just shuts down in a few minutes.
   
   You probably do not have a valid Virtuozzo license installed - it can be expired or number of VEs is exceeded. Please, check the output of 'vzlicview' command. The status of the license should be ACTIVE and 'used VE' should be not more than 've_total'. More information about Virtuozzo licenses can be found in this article.
   
   Another possible reason - VE was created with so called class 1 (Light VE) and exceeds defined in license limits for a number of resources such as privvmpages, numproc, shmpages and other. You will find error messages like this in /var/log/messages file on a node:
   
   VE 101 violates UB_PRIVVMPAGES
   
   In this case it is recommended to change VE class to 2 (Unlimited VE) using 'vzctl set VE_ID --class 2 --save'.
   
   
2. VE cannot be started because it is locked.
   
   Please, follow the instructions from this article.
   
   
3. VE starts but displays error "/bin/bash: no such file" or the like.
   
   The owner of the VE could have removed some important package such as bash or glibc.
   In this case you may recover VE private area using 'vzctl recover VEID'.
   
   You may also have OS template the VE is absed on missed on hardware node, you may check it using 'vzpkgls VE_ID' and install missed OS template if it is needed.
   
   The VE can also be compromised, see below.
   
   
4. The VE starts but Segmentation fault occurs very soon after starting.
   
   The VE can be compromised, please check the corresponding article.
   
   
5. The VE failed to start with the message like this:
   ERROR: Can't write to file /etc/sysconfig/network-scripts/ifcfg-venet0
   vzquota : (warning) block_hard_limit [50100] < block_current_usage [60279]
   vzquota : (warning) block_hard_limit [50100] < block_current_usage [60279]
   
   This error message means that VE exceeded its disk space quota and can not be started because it is impossible to change system files during VE startup. Solution - increase diskspace (and probably inodes) alloted to VE using 'vzctl' utility:
   
   # vzctl set VE_ID --diskspace BARRIER:LIMIT --save
vzctl set VE_ID --diskinodes BARRIER:LIMIT --save
   
   If increasing blocks and inodes limits does not help, try to re-init quota for this VE with:
   
   # vzctl quotainit VE_ID
   
   Then start VE.