On a Hardware Node running Parallels Virtuozzo Containers (PVC) version 3.0 (with or without Service Pack 1), you updated the "initscripts" package in a Container that is based on the CentOS 5 or RHEL 5 OS template to "initscripts-22.214.171.124" or higher. After that, the network in the Container stopped working. The "ifconfig" command executed in the Container does not list any network adapters.
Symptoms of this issue are as follows:
1. During the Container’s start, no warnings are reported, but IP addresses are not assigned:
[root@vzlin30 ~]# vzctl exec 117 ip a
1: lo: <LOOPBACK> mtu 16436 qdisc noop
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: venet0: <BROADCAST,POINTOPOINT,NOARP> mtu 1500 qdisc noop
2. Restarting the service "network" in a Container generates the following error:
[root@vzlin30 ~]# vzctl exec 117 service network restart
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: Device lo does not seem to be present, delaying initialization.
Bringing up interface venet0: Device venet0 does not seem to be present, delaying initialization.
To repair the network in the Container:
- Open the Container configuration file for editing:
# vi /etc/vz/conf/CTID.conf
- Add the "sysfs" value to the TECHNOLOGIES parameter. For example, change this string
TECHNOLOGIES="x86 nptl sysfs"
- Save the file.
- Restart the Container:
# vzctl restart CTID
To have the fix applied to newly created Containers automatically, add the same word to the file "technologies" in the directory of the corresponding EZ OS template. If the file is missing, create it. For example, for CentOS 5 32-bit, the full path to the file would be: