SymptomsThe 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
CauseCheck 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.
ResolutionCheck 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.