Article ID: 9668, created on Feb 10, 2011, last review on Aug 12, 2014

  • Applies to:
  • Virtuozzo containers for Windows 4.6

Symptoms

Scenario 1:
1) A container was migrated from a physical machine to Parallels Virtuozzo Containers 4.0 or 4.5.
2) PVC was upgraded to 4.6.
The container cannot start with the following errors:
 
C:\>vzctl start CTID
Starting container ...
ResolveGroupOrderList failed with err 2
RestoreVeServicesConfig failed with err 2
Error 0x1 while executing script 'on_vps_startup.cmd CTID'


Scenario 2:
1) A container was migrated from a physical machine to Parallels Virtuozzo Containers 4.0 or 4.5.
2) The container was migrated (copied) to a PVC 4.6 Hardware Node.
The container cannot start with the same errors as in Scenario 1.

Cause

One of the start scripts is looking for a P2V_TYPE parameter in the container configuration, which did not exist in early versions.

Resolution

The issue will be fixed in a future PVC version.

For now, please use this workaround:

1. Stop the container.

2. Set the necessary parameter value by running the following command:
 
vzcfgt set CTID P2VType w2k3

3. Start the CT.

4. Stop the CT.

5. Unset the necessary parameter value by running the following command.

vzcfgt set CTID P2VType ""

6. Start the container.


Note: If you skip steps 3 to 5, you may encounter the following issues:

1. The container will take a very long time to start.

2. You will receive warnings like the following during CT starting:

C:\Documents and Settings\Administrator>vzctl start 999
Starting container ...
WARNING: Native API function call 'ZwWaitForSingleObject' failed, code 0x102 Tim
eout waiting for BaseNamedObjects\TermSrvReadyEvent event in session 999
ERROR: exec (net start termservice) exit code 2
...
Container is mounted
Container was started


3. The container will be inaccessible via RDP because the corresponding service will fail to start:

C:\Documents and Settings\Administrator> vzctl exec 999 net start termservice
The Terminal Services service is starting.
The Terminal Services service could not be started.
The service did not report an error.

Additional Information

The issue may also occur if there are two different OS template caches present on the Node. Refer to this article for more details:
111305 Unable to start a container after upgrading to Parallels Virtuozzo Containers for Windows 4.6

6c20476fe6c3408461ce38cbcab6d03b d02f9caf3e11b191a38179103495106f 965b49118115a610e93635d21c5694a8 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF