6,534
edits
Changes
add a big fat warning
OpenVZ consists of a kernel, user-level tools, and container templates. This guide tells how to install the kernel and the tools on [http://www.debian.org Debian] StableEtch or Lenny/Squeeze. For Squeeze, use the Lenny directions. For Wheezy (7.0), use the vzctl package included in wheezy, together with the Wheezy OpenVZ kernels from [http://download.openvz.org/debian/ http://download.openvz.org/debian/]. Alternatively reduced functionality may be possible using the stock Debian Wheezy kernel (based on kernel.org version 3.2) and [[Vzctl_for_upstream_kernel]]. You may also wish to check the information on [http://wiki.debian.org/OpenVz the Debian wiki]. For Etch users, this document explains how to partially upgrade to Debian Lenny and install from lenny repositories ('''use this options at your risk''').
== Requirements ==
=== Filesystems ===
It is 's recommended to that you use a separate partition for VEs container private directories (by default <code>/var/lib/vz/private/<veidCTID></code>). The reason why you should do so for this is that if you wish to use the OpenVZ per-VE container disk quota, you won't be able to use usual Linux disk quotas on the same partition. Bear in mind, that "per-VE container quota " in this context includes not only pure per-VE container quota, but also the usual Linux disk quota used in VEcontainer, not on the [[HN]]. At the very least try to avoid using the root partition for containers, because the root user of a container will be able to overcome the 5% disk space barrier in some situations. If the HN root partition is completely filled, it will break the system.
'''If you are using Debian Lenny, this step in no longer required. Openvz kernel packages and tools are available on main repository.'''
=== Repository setup = 1. Using openvz.org repositories ====
At the moment two different repositories are online at http://download.openvz.org :
: apt-uri http://download.openvz.org/debian
: apt-uri http://download.openvz.org/debian-systs
: (Mirror of OpenVZ Repository from http://debian.systs.org/)
{{Note|The next steps used use the Repository repository at http://download.openvz.org/debian-systs, ; the actually actual OpenVZ Tools for Debian are exist only in as unstablebuilds, see http://packages.debian.org/vzctl}} {{Note|By default, on Ubuntu systems root tasks are executed with [https://help.ubuntu.com/community/RootSudo sudo]}} This can be done via the following commands, as root or as privileged "sudo" user<pre># echo -e "\ndeb http://download.openvz.org/debian-systs etch openvz" >> /etc/apt/sources.list# wget -q http://download.openvz.org/debian-systs/dso_archiv_signing_key.asc -O- | apt-key add - && apt-get update</pre> ==== 2. Using Debian repositories (upgrade to lenny) ====
Give etch package priority over lenny packages. Edit '''/etc/apt/preferences''' and set like this:
<pre>
</pre>
Then '''apt-get update && apt-get dist-upgrade''' to upgrade to lenny.
== Kernel installation ==
=== Wheezy and Lenny === {{Note|The best kernel to use is [[Download/kernel/rhel6|RHEL6-based]]. Please see [[Install_kernel_from_RPM_on_Debian_6.0]]}} === Etch === ==== 1. Using openvz kernel repositories ==== {{Note|In case you want to recompile the OpenVZ kernel yourself on Debian, see [[Compiling the OpenVZ Kernel kernel (the debian Debian way)]].}}
First, you need to choose what kernel you want to install.
{| class="wikitable"
|+'''OpenVZ Kernel list built with kernel config from http://download.openvz.org'''
! kernel Kernel !! Description !! Hardware !! Debian ArchitekturArchitecture
|-
! ovzkernel-2.6.18
{| class="wikitable"
|+'''OpenVZ Kernel list built with official Debian kernel config and OpenVZ Settings'''
! kernel Kernel !! Description !! Hardware !! Debian ArchitekturArchitecture
|-
! fzakernel-2.6.18-686
</pre>
===== Configuring the bootloader =====
In case GRUB is used as the boot loader, it will be configured automatically, or execute update-grub; lines similar to these will be added to the <tt>/boot/grub/menu.lst</tt> file:
{{Note|per default on debian/ubuntu, a 2.6.22 kernel will boot before a 2.6.18, please check manually the grub boot order. See man update-grub for more details}}
=== Rebooting into OpenVZ kernel == Installing the user-level tools ===== OpenVZ needs some user-level tools installed. Those are: ; vzctl: A utility to control OpenVZ containers (create, destroy, start, stop, set parameters etc.); vzquota: A utility to manage quotas for containers. Mostly used indirectly (by vzctl). <pre> # [sudo] apt-get install vzctl vzquota</pre>
=== Rebooting into OpenVZ kernel ===
Now reboot the machine and choose the OpenVZ needs some Linux Kernel on the boot loader menu. If the OpenVZ kernel has been booted successfully, proceed to installing the user-level tools installedfor OpenVZ. Those are:
1. Kernel:
<pre>
# uname -r
2.6.26-1-openvz-686
#
</pre>
2. Openvz kernel facility:
<pre>
# ps ax | grep vz 2349 ? S 0:00 [sudovzmond] apt-get install vzctl vzquota
</pre>
3. A network interface for containers:
<pre>
# ifconfig
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
</pre>
== Configuring ==
There are a number of kernel parameters that should be set for OpenVZ to work correctly. These parameters are stored in <tt>/etc/sysctl.conf</tt> file. Here is the relevant part of the file; please edit it accordingly.
{{Note|vzctl version from debian-systs, automate changing automatically inserts these options at the last of <tt>/etc/sysctl options .conf</tt>, except for openvznet.ipv4.ip_forward}}
<pre>
net.ipv4.conf.default.forwarding=1
net.ipv4.conf.default.proxy_arp = 0
net.ipv4.ip_forward=1
# Enables source route verification
net.ipv4.conf.all.rp_filter = 1
# Enables the magic-sysrq key
kernel.sysrq = 1
# TCP Explict Congestion Notification
#net.ipv4.tcp_ecn = 0
# we do not want all our interfaces to send redirects
net.ipv4.conf.default.send_redirects = 1net.ipv4.conf.all.send_redirects = 0
[...]
# [sudo] sysctl -p
{{Note|You can make a symlink from /var/lib/vz to /vz as backward
compatibility to OpenVZ as installed in other distributions
(Debian vz root directory is /var/lib/vz to be FHS-compliant.}}
{{Note|Support of OS templates on 64 bit hosts is somewhat limited for the time being, so that not all tools or features are available - please see [[Making template tools to work on x86_64]] and [[Install OpenVZ on a x86 64 system Centos-Fedora]] for additional details and information on possible workarounds}}
{{Note|Setup your prefered standard OS Template : edit the /etc/vz/vz.conf}}
# [sudo] apt-get install vzctl-ostmpl-debian-5.0-i386-minimal
== Additial user tools Additional User Tools ==
; vzprocps
: A set of utilities to provide system information (vzps and vztop)
# [sudo] apt-get install vzprocps vzdump
On Debian squeeze, vzdump seems packaged in standard aptline. For lenny, See [[Backup_of_a_running_container_with_vzdump]]
== Secure it ==
If you want to secure your container with individual firewall rules (instead or additionally to securing the host node) then you must run iptables inside the container. This works slightly different than on a physical server. So make sure that you check that iptables rules are indeed applied as expected inside the container.
Iptables modules required by the container must be specified in the general vz.conf file or the vzXXX.conf file of the container.
Add the following line into vz.conf to activate the respective iptables modules for all containers.
IPTABLES="ip_tables ipt_REJECT ipt_tos ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl
ipt_length ip_conntrack ip_conntrack_ftp ip_conntrack_irc ipt_LOG ipt_conntrack ipt_helper ipt_state iptable_nat ip_nat_ftp ip_nat_irc ipt_TOS"
[[http://wiki.debian.org/DebianFirewall][Configure]] your iptable rules inside the container.
{{Warning|Note that iptables rules inside the container are not applied automatically as on a physical server by starting the iptables module! Follow the instructions below}}
To make sure the iptables rules are applied on a startup/reboot we'll create a new file:
nano /etc/network/if-pre-up.d/iptables
Add these lines to it:
#!/bin/bash
/sbin/iptables-restore < /etc/iptables.up.rules
The file needs to be executable so change the permissions:
chmod +x /etc/network/if-pre-up.d/iptables
Start iptables
/etc/init.d/iptables start
If the startup shows errors then you have probably not activated the needed iptables modules. See above.
Check inside the container that your iptables rules are indeed applied:
iptables -L
If the rules do not show up as you would expect on a physical server then you might not have activated the needed iptables modules.
== Start it! ==
# [sudo] /etc/init.d/vz start
This does not make the vz system automatically start at boot time. For automatic start:
# [sudo] update-rc.d vz defaults 98
== Use it! ==
After installing the OpenVZ kernel, user tools and a Minimal VE minimal OS Template templateto create a first VE container and do some [[Basic basic operations in OpenVZ environment]] and read . Read the [[download:doc/OpenVZ-Users-Guide.pdf|doc/OpenVZ-Users-Guide.pdf]] and , browse this wiki.
[[Category: HOWTO]]
[[Category: Debian]]
[[Category: Installation]]