Article ID: 115821, created on Mar 26, 2013, last review on Apr 27, 2016

  • Applies to:
  • Virtuozzo containers for Windows
  • Virtual Automation

Symptoms

In Parallels Virtual Automation (PVA), PVA Agent cannot start. The service is in the pending state:

C:\>net start pvaagent
The PVA Agent service is starting...............................................
................................................................................
................................................................................


C:\>sc query pvaagent
SERVICE_NAME: pvaagent
        TYPE               : 10  WIN32_OWN_PROCESS
        STATE              : 2  START_PENDING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x95
        WAIT_HINT          : 0xbb8

Cause

On each startup, PVA Agent performs a health check of all containers by entering them via vzctl exec. If this operation fails, PVA Agent may hang on startup.

In this instance, some containers are not accessible to the "vzctl" utility:

C:\>vzctl enter 1158 
ERROR: Response timeout for operation 'exec'
Environment is not changed.

Reasons for a failing "vzctl" may vary. Some possibilities include:

  1. RDP attacks
  2. No privileges to execute cmd.exe inside the container
  3. The container is damaged from the inside ("cmd.exe" may be missing, or its VZFS link is pointing to a nonexistent file). In this case, we recommend contacting Parallels Technical Support for help.

The issue is recognized as a product bug PVA-34614

Resolution

The permanent fix is included in Virtual Automation Agent 6.1 for Windows Hotfix 3 (6.0-2584)

If the update cannot be installed right away, follow these instructions as a workaround:

  1. Find the containers that have problems:

    echo exit > exit.cmd
    for /f %i in ('vzlist -Ho veid') do vzctl enter %i < exit.cmd
    
  2. Stop the problematic container(s). Repeat Step 1 (above) until all these containers are stopped.

    vzctl stop CTID
    
  3. Kill the hung PVA Agent service:

    taskkill /im pvaagentd.exe
    
  4. Start the PVA Agent service:

    net start pvaagent
    
  5. Restart the problematic container(s).

    vzctl start CTID
    

Search Words

pva agent timeout

hang pvaagent

PVA Agent is not strating up

pva agent stuck

vps provision timeout

d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223 965b49118115a610e93635d21c5694a8 319940068c5fa20655215d590b7be29b

Email subscription for changes to this article
Save as PDF