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 ==
rm /etc/mtab
ln -s /proc/mounts /etc/mtab
=== /dev ===
Vserver mounts /dev/pts filesystem for container transparently, whereas openvz does not. To compensate the ommission, you need to move aside /dev directory in the vserver-originating container and copy /dev directory from openvz based container.
=== Ubuntu udev ===
Additionally, Ubuntu based vservers have the udev package installed which prevents access to the console in openvz. This error message is an example of the problem:
# vzctl enter 345
enter into CT 345 failed
Unable to open pty: No such file or directory
The fix is to remove the udev package from the guest:
# vzctl exec 345 'dpkg --force-depends --purge udev'
(Reading database ... dpkg: udev: dependency problems, but removing anyway as you request:
initramfs-tools depends on udev (>= 117-5).
15227 files and directories currently installed.)
Removing udev ...
Purging configuration files for udev ...
dpkg - warning: while removing udev, directory `/lib/udev/devices/net' not empty so not removed.
dpkg - warning: while removing udev, directory `/lib/udev/devices' not empty so not removed.
Now restart the container, you should now be able to use the console.
# vzctl restart 345
Restarting container
...
<SNIP>
...
Container start in progress...
# vzctl enter 345
entered into CT 345
root@test:/#
=== /proc ===
The /proc filesystem is not automatically mounted by openvz. So the vserver needs to mount it itself. The simplests (not the best) way it can be done, is by sticking following command at the end of /etc/init.d/bootmisc.sh:
mount /proc
[[Category:HOWTO]]