| Re: CentOS forums claim OpenVZ containers/host as unsupported, so... [message #41651 is a reply to message #41467] |
Sun, 13 February 2011 05:03   |
pyite
Messages: 20
Registered: January 2007
|
Junior Member |
|
|
Looks like you got some good advice already, I'll just add to a couple of the replies:
3 & 4: apart from the kernel module issues, the biggest difference is how the memory (and other) limitations work.
Because of the many fine-tuning options, OpenVZ can cause software to fail in unusual ways that are unlikely to happen on a real server (e.g. running out of TCP receive buffers or kernel memory). It is possible to get some unusual failure conditions, especially with software like Java. Also, top will show that there is no swap space inside the VM, which is a little weird at first for some people. The hardware node handles the decision of when to use swap, it is invisible to the VM's.
There are many pages that discuss these issues, search for "user_beancounters" (aka ubc) and on your VZ machine try this with a 132 column terminal: cat /proc/user_beancounters
At first, I would strongly suggest using the "unlimited" configuration file examples when creating a new VM/VPS/VE/whatever you want to call it. Run your VM for awhile, then take a look at the "maxheld" column in the stats. Use this number to do your final adjustment to the config file (maybe bump the limits up by 20%? Use your judgment). I'd recommend working on some monitoring so you know when these limits are reached.
5) 64 bit works quite well, I've had no issues. Give it a try!
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
