It sounds like this is corrected in later versions of the OpenVZ kernel but Iam not sure, it may also be that a much newer kernel is needed and Centos may not have a recent enough kernel.
*Debain 7.0 however does work fine as a temporary fix or work around.
Debian 8 OpenVZ no IP and networking not working:
lo Link encap:Local Loopback
If you move your hard drive(s) around to other computers/servers, you'll find that your eth0 keeps getting higher, the first time it will become eth1 and then eth2 etc and even higher if your server has dual or quad NICs. The reason is that udevd basically assigns eth0 tot he first NIC it finds and remembers it, if it encounters a NIC with a differentMAC, it assigns it one higher (eg. eth1).
See the example below, I have eth2 now so how doI fix it?........
There are all kinds of threads and links on the internet, and this seems to be a contentious issue butI don't know why.
95th percentile is either a good deal for some or a big rip off for others, Ijust said it there :)
But the reality is that for MOST people who transfer low amounts of data but burst to higher speeds such as 40mbit+ even for short periods of time, then you'll pay a lot of money to do that.
Basically 95th percentile is an-old archaic method........
Different distributions such as Debian and Centos behave differently when trying to shutdown your system.
shutdown -H now on Debian does not do what you'd expect. The system won't power down, it will halt and do everything but power down.
shutdown -PH now will do the job though (actually power the system off). This is important to test especially if you are not near the system. If you just use -P it forcefully shuts off which is not........