SolusLab + OVZ

It has come to our attention that the latest release of vzctl (3.0.25-1) contains several critical bugs.
vzctl 3.0.25-1 (OpenVZ Container Management Tool), has for some reason made it into the stable branch of the OpenVZ repository without being fully tested. If you have this version installed, your containers may have access to the full amount of host memory and tun/tap will not function within the container. We have only found these two issues so far, however the bug has only just been reported.
We have put together a page on our wiki with instructions on how to downgrade to a more stable version of vzctl. It’s a simple process and only needs to be performed if you have version 3.0.25 installed already.
Full instructions are here: http://wiki.solusvm.com/index.php/OpenVZ_Bugs
Please remember to reboot your containers or node after the downgrade and don’t use yum to upgrade vzctl.
As soon as OpenVZ release a new vzctl update, we will fully test it and inform you when it's stable for a production enviroment.
As you can understand, this is totally out of our control and is not a bug within SolusVM. Any system that uses OpenVZ vzctl will experience the same issues and will need the downgrade to function correctly.
Regards
Soluslabs Technical Support Team