A container is running, but cannot be entered with
>vzctl enter 57571 ERROR: Response timeout for operation 'exec' Environment is not changed. Command 'enter' is successfully finished
On stopping the container, the following error is received:
vzctl stop 57571 WARNING: Native API function call 'ZwWaitForSingleObject' failed, code 0x102 Timeout waiting for BaseNamedObjects\SC_AutoStartComplete event in session 57571 WARNING: Failed to wait for SC_AutostartComplete in CT 57571
It is not possible to connect to the container over RDP.
Container spends long time in starting\stopping cycle and following error can be found in the vzlog:
T=2015.01.11 23:24:24.149; A=VzSrv; P=2316.1424; S=VZSRV; F=build\4.6.490.0\sources\virtuozzo\vzwin\vzmain\vzsrv\klpc.c,KlpcProcessMessage,106; L=INFO; R=0(0); C=0(0); M=135  Container 123 requested REBOOT action
Some services are hanging inside the container, leading to the malfunctioning of other services by dependencies.
System.evtx log from
%vzroot%\root\%ctid%\c\windows\system32\winevt\Logs, open it on the host and try to locate the problematic service.
If there is a clearly identifiable non-starting service, it can be disabled:
Stop the container
Mount the container:
vzctl mount CTID
Open the registry editor on the host (regedit.exe), and disable the faulty service inside the container:
Set "start" -> 4
- Start the container.
If there is no clear evidence as to which service cannot start properly, contact Parallels Technical Support for assistance.
Other causes of a failing
vzctl enter may include:
115821 PVA Agent service is stuck in "START_PENDING" state
112775 Cannot connect to a container using RDP