Hi
arpsend doesn´t cancel the vz start anymore. It only writes a warning and starts the vz despite the address conflict.
Network inside the container is up (and competing with the other host)
On a plain openvz box it looks like this:
Is this a wanted behaviour?
Regards
Matt
arpsend doesn´t cancel the vz start anymore. It only writes a warning and starts the vz despite the address conflict.
Network inside the container is up (and competing with the other host)
Code:
root@blade2:~# vzctl start 303
Starting container ...
Container is mounted
Adding IP address(es): x.x.x.x
arpsend: x.x.x.x is detected on another computer : 00:15:17:23:xx:xx
vps-net_add WARNING: arpsend -c 1 -w 2 -D -e x.x.x.x vmbr0 FAILED
Setting CPU units: 1000
Setting CPUs: 8
Container start in progress...
On a plain openvz box it looks like this:
Code:
helene:~# vzctl start 124
Starting container ...
Container is mounted
Adding IP address(es): x.x.x.x
Unable to add IP x.x.x.x: Address already in use
Container start failed
Stopping container ...
Container was stopped
Container is unmounted
Is this a wanted behaviour?
Regards
Matt