Installing And Using OpenVZ On CentOS 5.2 - Page 2

On this page

2 Using OpenVZ

Before we can create virtual machines with OpenVZ, we need to have a template for the distribution that we want to use in the virtual machines in the /vz/template/cache directory. The virtual machines will be created from that template. You can find a list of precreated templates on http://wiki.openvz.org/Download/template/precreated.

I want to use CentOS 5 in my virtual machines, so I download a CentOS 5 template (a default CentOS 5 template in this case):

The 101 must be a uniqe ID - each virtual machine must have its own unique ID. You can use the last part of the virtual machine's IP address for it. For example, if the virtual machine's IP address is 192.168.0.101, you use 101 as the ID.

(Instead of using the vzctl set commands, you can as well directly edit the vm's configuration file which is stored in the /etc/vz/conf directory. If the ID of the vm is 101, then the configuration file is /etc/vz/conf/101.conf.)

To start the vm, run

vzctl start 101

To set a root password for the vm, execute

vzctl exec 101 passwd

You can now either connect to the vm via SSH (e.g. with PuTTY), or you enter it as follows:

vzctl enter 101

To leave the vm's console, type

exit

To stop a vm, run

vzctl stop 101

To restart a vm, run

vzctl restart 101

To delete a vm from the hard drive (it must be stopped before you can do this), run

The failcnt column is very important, it should contain only zeros; if it doesn't, this means that the vm needs more resources than are currently allocated to the vm. Open the vm's configuration file in /etc/vz/conf and raise the appropriate resource, then restart the vm.

Sub pages

2 Comment(s)

Comments

There seems to be a problem with running MySQL within OpenVZ and with its kerenl. I did an instalation on HP Proliant DL380 and it went pretty clean. However when I tried to start MySQL (service mysqld start), I got 'No such file or directory'. I even did a reinstall, removal and a new instalation with yum and got the same, on host as well as within the nodes.

There was a mention on the net that it could be the lack of memory ... I dissagree: 4 Gb RAM, 8 Gb swap; total memory usage RAM 10% / swap 0%.

So, is there anyone with the same problem ... Better yet, with a solution.