Article ID: 128606, created on Apr 2, 2016, last review on May 1, 2016

  • Applies to:
  • Operations Automation 6.0


A virtual machine gets migrated online from a node with Virtuozzo 6.0 Update 10 (or earlier) to a node with Update 11 (or later). The VM contains 2 network interfaces, the secondary one being a routed adapter, a typical configuration in OACI environment.

As a result, a virtual machine loses network connectivity on private network, which is configured on the network adapter in routed mode.

The IP address assigned to the corresponding vme* interface on the hardware node changed from to, but the route inside the VM didn't reflect the change:

root@test:/# ip r l dev eth3  scope link


Virtuozzo 6.0 Update 11 brings a change to the default gateway for routed adapters to comply with the APIPA standard address range change in scope of RFC-3927. During online migration, no network reconfiguration occurs inside the VM, so the new route is not present.


In order to bring the VM connectivity back, two options are possible:

  • add the needed route manually in the VM:


    # ip route add dev eth3 scope link

    where "eth3" is the actual name of the interface that can be found from the output of ip a command.


    route add -P mask if <ID>

    where is the ID of the routed interface that can be found from the output of route print command.

  • (or) restart the VM

It is also recommended to update guest tools inside the virtual machine to correct the issue:

Linux Guest Tools update instructions
Windows Guest Tools update instructions

Additional Information

Reference links:
Virtuozzo 6.0 Update 11
Understanding of Routed Mode

Search Words


private network

privnet traffic lost

Update 11


5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF