Article ID: 121641, created on May 20, 2014, last review on May 20, 2014

  • Applies to:
  • Virtuozzo
  • Virtuozzo containers for Linux
  • Virtuozzo hypervisor
  • Virtual Automation


  1. A VNC console doesn't open for a Virtual Machine in PVA or Power Panel with the following error displayed:

    Network error: connection has been shutdown : Remote host closed

  2. Power Panel doesn't work for any Virtual Environment on the server.

  3. There has been a change of IP address(es) on the hardware node recently with service network restart, and no server reboot happened ever since.

  4. The old node's IP appears in the proxy log of CT 1 /vz/root/1/var/log/pavm/pim-cp-proxy.log:

    T=2014.05.20 04:19:31.513249; L=[info]; PID=1;  connection created from 9 to 10
    T=2014.05.20 04:19:31.513277; L=[info]; PID=1;  connect to remote host, port 4649 done, fdin -  9, fdout - 10
    T=2014.05.20 04:20:34.512684; L=[info]; PID=1;  connection created from 10 to 9
    T=2014.05.20 04:20:34.512766; L=[info]; PID=1;  disable connection on read from 10, result - -1, strerror - Connection timed out
    T=2014.05.20 04:20:34.512793; L=[info]; PID=1;  connection shutdown from 9 to 10, strerror - Connection timed out
    T=2014.05.20 04:20:44.523203; L=[info]; PID=1;  connection closed from 10 to 9

    In this example, is an old IP and no longer exists on the hardware node.


CT 1 dumps the hardware node's IPs on its start and uses them later for proxying connections on offline management services, which are used for VNC console in PVA and for Power Panel.


Restart container 1:

# vzctl restart 1

Search Words

can't open console

d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223 a26b38f94253cdfbf1028d72cf3a498b e8e50b42231236b82df27684e7ec0beb 319940068c5fa20655215d590b7be29b 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF