Article ID: 120136, created on Feb 14, 2014, last review on Jun 17, 2016

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


When a container is stopped, there are still ARP and routing entries that remain on the hardware node.


[root@pcs ~]# vzlist 101
       101          - stopped     test

[root@pcs ~]# arp -anv | grep
? ( at * PERM PUP on eth1
? ( at * PERM PUP on eth0

[root@pcs ~]# ip route list | grep dev venet0  scope link  metric 1000

Why does this happen and how to prevent it?


Such behavior is explained by enabled offline management option for the container.

With offline management turned on, network requests on container's IP address(es) and port 4643 are still accepted by the hardware node and redirected to CT#1 and Power Panel service. Therefore, the routing entries and ARP cache should exist to allow managing the container in offline mode through Power Panel.

If offline management is not required, it can be switched off for a specific container:

# vzctl set 101 --offline_management off --save

Search Words

venet routing

319940068c5fa20655215d590b7be29b 2897d76d56d2010f4e3a28f864d69223 a26b38f94253cdfbf1028d72cf3a498b d02f9caf3e11b191a38179103495106f 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF