Article ID: 113093, created on Jan 10, 2012, last review on May 10, 2014

  • Applies to:
  • Virtuozzo containers for Windows 4.6
  • Virtuozzo containers for Windows 4.5
  • Virtuozzo containers for Windows 4.0


The container does not start, and the output shows the following errors:
ERROR: Container 102 system process terminated unexpectedly
ERROR: Shutdown initiated while waiting for SCM (Service Control Manager) in container 102
INFO: stop_vps_locked: container 102
ERROR: Container 102 is not started
ERROR: Exec '@VzOnShutdown' failed in container 102
INFO: Notify container 102: stopped none


Check the container disk type, disk space limit, and the amount of free disk space on the "\vz" partition.
Most likely, the container disk space limit exceeds the amount of available free disk space, and the container disk type is "plain;" hence, disk space allocation fails.


Check the container disk type, and if it is "plain," change it to "compact."
C:\> vzquota show 102 -t

disk  type             usage     hardlimit  path 
C:    compact (plain)  41360     102400     C:\vz\Private\102\root.efd

C:\> vzctl set 102 --save --disktype compact

Also make sure that the "\vz" partition has enough free space to host all containers in the event that the containers' disk usages begin to approach their limits.

6c20476fe6c3408461ce38cbcab6d03b d02f9caf3e11b191a38179103495106f 965b49118115a610e93635d21c5694a8 28d0f7cc091e3b9304fa556c03f9a940 d09cb2230ee0cfa720ed0f2a3cc39452 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF