Changes
→Issues
=== Updating different configurations ===
# cd /vz
# mkdir private/345
# mv /vservers/v345 /vz/private/345
In Debian Lenny the path is /var/lib/vz/private/345 instead.
In any case it is a good idea to have the guest file system in a dedicated partition or lvm container (shown in the example below) and just mount it there
instead of moving:
# mkdir /var/lib/vz/private/345
# mount /dev/mapper/vg01-lvol5 /var/lib/vz/private/345
Now it is time for creating configuration files for OpenVZ container. Use the basic sample
# cd /etc/sysconfig/vz-scripts
# cp ve-vps.basic.conf-sample 345.conf
In Debian Lenny the configuration is located in /etc/vz/conf/ , in this case type:
# cd /etc/vz/conf
# cp ve-vps.basic.conf-sample 345.conf
Now, let's set some parameters for the new container.
First, we need to tell which distro the container is running:
# echo "OSTEMPLATE=\"fedora-core-4\"" >> 345.conf
# echo "OSTEMPLATE=\"debian\"" >> 345.conf (for Debian Lenny)
Then we set a few more parameters:
== Issues ==
=== Starting ===
If starting fails with a message '''Unable to start init, probably incorrect template''' either the /sbin/init file is missing in the guest file system, or just not executable. Or the guest file system is completely absent or dislocated. The proper path where you must place is specified in the vz.conf file, namely the parameter VE_PRIVATE. For Debian this file can be found in /etc/vz.
=== Networking ===
