Service Container #1 has 1-4 processes inside and an empty hostname:
[root@vz ~]# vzlist 1 CTID NPROC STATUS IP_ADDR HOSTNAME 1 3 running 192.168.161.108 - [root@vz ~]# vzps -E 1 CTID PID TTY TIME CMD 1 648062 ? 00:00:02 init 1 648063 ? 00:00:00 kthreadd/1 1 648064 ? 00:00:00 khelper/1
It is impossible to enter the container:
[root@vz ~]# vzctl enter 1 Failed to enter Container 1 Unable to open pty: No such file or directory
Previously, the service container was operational with >30 processes inside.
Parallels Virtual Automation Agent is installed on the server. Service Container #1 is used for offline management redirection purposes only.
Parallels Virtual Automation bundle comes by default, starting from Parallels Virtuozzo Container 4.6 / Parallels Server Bare Metal 4.0.
On previous versions of PVC software (4.0 / 3.x), service container carried the installation of Parallels Infrastructure Manager on each Parallels Virtuozzo Containers host.