We have identified the source of the problem.
The vKS IP/MAC pairing was not applied correctly, having an impact before the update.
The vHost reboot triggered the fault at the time of reprogramming the VM MACs.
Corrective measures are being implemented.
Comment by OVH - Tuesday, 21 May 2013, 12:49PM
The corrective measures have been implemented,
so the VMs should all be pinging again.
We did a fix on the robots to reprogramme the
IP/MAC pairings automatically each time the vHost changes.
We have identified the source of the problem.
The vKS IP/MAC pairing was not applied correctly, having an impact before the update.
The vHost reboot triggered the fault at the time of reprogramming the VM MACs.
Corrective measures are being implemented.
The corrective measures have been implemented,
so the VMs should all be pinging again.
We did a fix on the robots to reprogramme the
IP/MAC pairings automatically each time the vHost changes.