Article ID: 117617, created on Sep 30, 2013, last review on May 7, 2014

  • Applies to:
  • Virtuozzo containers for Windows


Node constantly crashes after Virtuozzo service startup, on starting all containers in a bunch.


The causes for the problem may vary. This article describes an efficient way to identify the faulty container(s) and disable them from starting up.


  1. Disable autoboot for all containers. Right after "Virtuozzo Management Service" is started and before containers get the actual time to start, run the commands :

    for /f %i in ('vzlist -Hao veid') do for /f %j in ('vzcfgt get %i autoboot') do echo %i %j >> \autoboot.txt
    for /f %i in ('vzlist -Hao veid') do vzcfgt set %i autoboot 0
  2. Start containers one by one and find the one that crashes the server :

    for /f %i in ('vzlist -Hao veid') do vzctl start %i
  3. After node reboot, continue starting containers, having isolated the faulty one, detected on the previous step. One of the ways to isolate containers is to rename their private area directory :

    ren D:\vz\private\CTID CTID.broken
  4. Once all bad containers are identified, restore the autoboot settings :

    for /f "tokens=1,2" %i in (\autoboot.txt) do vzcfgt set %i autoboot %j

Search Words



d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223 965b49118115a610e93635d21c5694a8

Email subscription for changes to this article
Save as PDF