Article ID: 118992, created on Dec 3, 2013, last review on Oct 27, 2014

  • Applies to:
  • Virtuozzo containers for Linux 4.7
  • Virtuozzo containers for Linux 4.6
  • Virtuozzo containers for Linux 4.0

Symptoms

This is only for Parallels Virtozzo Containers (PVC) 4.0 and 4.6.

Parallels Cloud Server 6.0 and Parallels Virtuozzo Containers 4.7 are not affected.

  1. Use a PVC 4.6 host on CentOS (2.6.18-028stab109.2 or later).
  2. Create a container with a CentOS 6 template.
  3. Upgrade to the newest CentOS 6.x version (iproute-2.6.32-31.el6.x86_64 will be installed).
  4. Restart the container.

After step 4, the network is unavailable:

~# /etc/init.d/network start
Bringing up loopback interface:  RTNETLINK answers: Operation not supported
Failed to bring up lo.                                             [FAILED]
Bringing up interface venet0:  RTNETLINK answers: Operation not supported
Failed to bring up venet0.                                         [FAILED]
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
~#

Cause

The iproute package was upgraded to iproute-2.6.32-31.el6.x86_64.

The issue is recognized as PCLIN-32219 and the fix is planned to be included in an upcoming Parallels Virtuozzo Containers 4.6 update.

Unfortunately, the issue will not be fixed for Parallels Virtuozzo Containers 4.0 since this version reached its End-Of-Life in June 2013. (For more information, you can refer to End-of-life policy for Parallels server virtualization products.)

Resolution

The latest working version is iproute-2.6.32-23 from CentOS 6 update 4:

As a workaround, you can install this version to the affected containers.

To have this version installed to a new container included in the OS template cache:

  1. Update the list of packages to include the OS template cache, adding the version to the package name:

    ~# sed 's~^iproute$~iproute-2.6.32-23.el6~' -i /vz/template/centos/6/x86{,_64}/config/os/default/packages
    
  2. Add the repository with CentOS 6.4 to the list of repositories:

    ~# echo http://vault.centos.org/6.4/os/x86_64 >> /vz/template/centos/6/x86_64/config/os/default/repositories
    ~# echo http://vault.centos.org/6.4/updates/x86_64 >> /vz/template/centos/6/x86_64/config/os/default/repositories
    
    ~# echo http://vault.centos.org/6.4//os/i386 >> /vz/template/centos/6/x86/config/os/default/repositories
    ~# echo http://vault.centos.org/6.4/updates/i386 >> /vz/template/centos/6/x86/config/os/default/repositories
    
  3. Recreate the OS template cache.

    ~# vzpkg create cache centos-6-x86_64 -f -r
    ~# vzpkg create cache centos-6-x86 -f -r
    
  4. To avoid updating the package by yum for containers, you can modify the post-install script for the OS template.

    The modified post-install script should:

    • Create a /etc/yum/ip-exclude file inside the container containing the list of packets yum should exclude from the update. In our case, it should be the following string:

      exclude=iproute
      
    • Append the following string to the /etc/yum.conf file inside the container:

      include=/etc/yum/ip-exclude
      

Search Words

network problem after yum update

Failed to bring up lo

Operation not supported

Cannot bring up network interface

VZ iproute

RTNETLINK answers

RTNETLINK answers: Operation not supported

Failed to bring up venet0

e8e50b42231236b82df27684e7ec0beb 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f 0c05f0c76fec3dd785e9feafce1099a9 35c16f1fded8e42577cb3df16429c57a 36627b12981f68a16405a79233409a5e

Email subscription for changes to this article
Save as PDF