= Sarge (Stable) ={{Warning|The OpenVZ packages at http://debian.systs.org/ aimed majority of the content on this page only applies to install OpenVZ in a easy wayolder, some task are done unsupported Debian versions and is archived on install process!this page for historical reasons only. '''The page you need is [[Installation on Debian]].'''}}
OpenVZ consists of a kernel, user-level tools, and container templates.
== edit apt source settings ==Add This guide tells how to your "install the kernel and the tools on [http:/etc/aptwww.debian.org Debian] Etch or Lenny/sourcesSqueeze.list"
<pre>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/]. deb 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.systs.org/ stable openvzOpenVz 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's recommended that you use a separate partition for container privatedirectories (by default <code>/var/lib/prevz/private/<CTID></code>). The reason for this is that if you wish to use the OpenVZ per-container disk quota, you won't be able to use usual Linux disk quotas on the same partition. Bear in mind that "per-container quota" in this context includes not only pure per-container quota but also the usual Linux disk quota used in container, 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. OpenVZ per-container disk quota is supported only for ext2/ext3 filesystems; therefore it makes sense to use one of these filesystems (ext3 is recommended) if you need per-container disk quota. === Repository setup (Etch only) === '''If you are using Debian Lenny, this step in no longer required. Openvz kernel packages and tools are available on main repository.''' ==== 1. Using openvz.org repositories ==== At the moment two different repositories are online at http://download.openvz.org:
and get the new package lists; by Ola Lundqvist <opal@debian.org>: (OpenVZ kernels only): apt-uri http://download.openvz.org/debian
; by Thorsten Schifferdecker <pretsd@debian.systs.org># : apt-get updateuri http://download.openvz.org/debian-systs<: (Mirror of OpenVZ Repository from http://debian.systs.org/pre>)
{{Note|The next steps use the repository at http://download.openvz.org/debian-systs; the actual OpenVZ Tools for Debian exist only as unstable builds, see http://packages.debian.org/vzctl}}
== precompiled kernel images at debian.systs.org (dso) ==The kernel-images {{Note|By default, on debianUbuntu systems root tasks are executed with [https://help.systsubuntu.org (dso) use the same kernel-config taken from OpenVZ.(most kernel-modules are built-in!)com/community/RootSudo sudo]}}
kernel(s) for i368 and amd64This can be done via the following commands, as root or as privileged "sudo" user
<pre>
ovzkernel# echo -2e "\ndeb http://download.6openvz.9 org/debian-systs etch openvz" >> /etc/apt/sources.list ovzkernel# wget -2q http://download.6openvz.9org/debian-smpsysts/dso_archiv_signing_key.asc -O- | apt-key add - && apt-get update</pre>
ovzkernel-==== 2.6.16 ovzkernel-2.6.16-smpUsing Debian repositories (upgrade to lenny) ====
ovzkernel-There is even a '''lenny''' repository with kernel 2.6.18 ovzkernel-2.628.18-smp</pre>'''Use it at your own risk!'''
i386 only:Add lenny repositories to your '''/etc/apt/sources.list'''
<pre>
ovzkerneldeb http://DEBIAN-2.6.18MIRROR/debian/ testing maindeb http://DEBIAN-enterprise MIRROR/debian-security/ testing/updates main
</pre>
OpenVZ tool(s) for i386 and amd64Enlarge apt-cache adding to '''/etc/apt/apt.conf''' this line:
<pre>
vzctl vzquota vzprocpsAPT::Cache-Limit "100000000";
</pre>
template(s) for i368 Give etch package priority over lenny packages. Edit '''/etc/apt/preferences''' and amd64 set like this: Debian 3.1 Minimal
<pre>
vzctlPackage: *Pin: release a=etchPin-ostmplPriority: 700 Package: *Pin: release a=lennyPin-debianPriority: 650
</pre>
Then '''apt-get update && apt-get dist-upgrade''' to upgrade to lenny.
== installing the kernel-images, toolset and debian-os-template Kernel installation ==Example: install the stable OpenVZ kernel, tools and Debian OS Template
# aptitude install ovzkernel-2.6.9 vzctl vzquota vzctl-ostmpl-debian=== 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]]}}
Maybe you need to update you "linux-loader" (can be configured at /etc/kernel-img.conf)=== Etch ===
for the "GRUB": ==== 1. Using openvz kernel repositories ====
# /sbin/grub-update {{Note|In case you want to recompile the OpenVZ kernel yourself on Debian, see [[Compiling the OpenVZ kernel (the Debian way)]].}}
First, you need to choose what kernel you want to install.
Reboot in your new {| class="wikitable"|+'''OpenVZ Kernel list built with kernel config from http://download.openvz.org'''! Kernel !! Description !! Hardware !! Debian Stable OpenVZ SystemArchitecture|-! ovzkernel-2.6.18| uniprocessor| up to 4GB of RAM| i386 and amd64|-! ovzkernel-2.6.18-smp| symmetric multiprocessor| up to 4 GB of RAM| i386 and amd64|-! ovzkernel-2.6.18-enterprise| SMP + PAE support + 4/4GB split| up to 64 GB of RAM| i386 only|}
# reboot{| class="wikitable"|+'''OpenVZ Kernel list built with official Debian kernel config and OpenVZ Settings'''! Kernel !! Description !! Hardware !! Debian Architecture|-! fzakernel-2.6.18-686| uni- and multiprocessor| up to 4GB of RAM| i386|-! fzakernel-2.6.18-686-bigmem| symmetric multiprocessor| up to 64 GB of RAM| i386|-! fzakernel-2.6.18-amd64| uni- and multiprocessor| | amd64|-|}
<pre>
# apt-get install <kernel>
</pre>
That's all :-)===== Configuring the bootloader =====
Now In case GRUB is used as the boot loader, it's time to setup your VE's with the minimal Debian-3.1 Templatewill be configured automatically, create new one or download another precreated OSexecute update-Templategrub; lines similar to these will be added to the <tt>/boot/grub/menu.lst</tt> file:
<pre>
[...]
title Debian GNU/Linux, kernel 2.6.18-ovz-028stab051.1-686
root (hd0,1)
kernel /vmlinuz-2.6.18-ovz-028stab051.1-686 root=/dev/sda5 ro vga=791
initrd /initrd.img-2.6.18-ovz-028stab051.1-686
savedefault
[...]
</pre>
{{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}}
= Etch (Testing) =OpenVZ is now a part of Debian Etch (a.k.a. "testing") repository.=== Installing the user-level tools =====
== install the kernelOpenVZ needs some user-image ==level tools installed. Those are:
=== use precomiled kernel images ===; vzctlCan be found at http://downloadA utility to control OpenVZ containers (create, destroy, start, stop, set parameters etc.openvz); vzquota: A utility to manage quotas for containers. Mostly used indirectly (by vzctl).org/kernel/debian/etch/
<pre>
List of precompiled kernel-images linux-image-2.6.18-openvz-486_02_i386.deb linux-image-2.6.18-openvz-686_02_i386.deb linux-image-2.6.18-openvz-amd64_01_amd64.deb linux-image-2.6.18-openvz-ia64_01_ia64.deb linux-image-2.6.18-openvz-k7_02_i386.deb linux-image-2.6.18-openvz-sparc64-smp_01_sparc.deb linux-image-2.6.18-openvz# [sudo] apt-sparc64_01_sparc.deb get install vzctl vzquota
</pre>
Example: Installing an OpenVZ precompiled ==== 2 Using Debian Kernel-Image for an i686:lenny repositories ====
If you upgrade to lenny, you can search openvz kernel and can install with:
<pre>
# wget http://download.openvz.org/kernel/debian/etch/linuxapt-image-2.6.18-openvz-686_02_i386.deb # dpkg -i get install linux-image-2.6.18-openvz-686_02_i386.deb686
</pre>
=== or build your own kernel-image (debian way) === To this command will install the latest kernel-source and the OpenVZ kernel patch, runall required packages like:
<pre>
# apt-get install kernel-package iproute libatm1 linux-sourceimage-2.6.18 kernel26-patch1-openvz libncurses5-686 linux-image-openvz-686 rsync vzctl vzquota libcgroup-dev
</pre>
and will arrange grub bootloader properly.
=== Rebooting into OpenVZ kernel ===
{{Warning|Before you restart your Server, verify that your system has all needed modules enabled in order to boot your harddisk (e.g. hardware modules, raid system(s), lvm2 etc). You may need an INITRD (initramdisk) or to compile needed kernel modules statically.}}
Unpack Now reboot the machine and choose the OpenVZ Linux Kernel on the boot loader menu. If the OpenVZ kernelhas been booted successfully, proceed to installing the user-source:<pre> # cd /usr/src # tar xjf linux-source-2.6.18.tar.bz2 # cd linux-source-2.6level tools for OpenVZ.18</pre>
=== Confirm proper installation ===
You need a kernel config1.You can use the config of the debian-kernelKernel:
<pre>
# cp /boot/configuname -r 2.6.1826-31-openvz-686 .config #
</pre>
Or get a 2.6.18 Openvz kernel config from httpfacility://download.openvz.org/kernel/devel/current/configs/
<pre>
# wget httpps ax | grep vz 2349 ? S 0://download.openvz.org/kernel/devel/current/configs/kernel-2.6.18-028test007-i686.config.ovz -O .config00 [vzmond]
</pre>
Now you can apply openvz kernel patch and modify your kernel-config3. A network interface for containers:
<pre>
# ../kernelifconfig venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-patches/all/apply/openvz00 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) # make menuconfigTX bytes:0 (0.0 B)
</pre>
== Configuring ==
You need following OpenVZ kernel config settings:<pre></pre>=== sysctl ===
Compile your Kernel (as user root, or you need the --fakerootcmd!)There are a number of kernel parameters that should be set for OpenVZ to work correctly. These parameters are stored in <prett> # make-kpkg --append_to_version=-1-openvz --added_patches=openvz --revision=1 kernel_image --initrd/etc/sysctl.conf</prett>file. Here is the relevant part of the file; please edit it accordingly.
{{Note|vzctl version from debian-systs, automatically inserts these options at the last of <tt>/etc/sysctl.conf</tt>, except for net.ipv4.ip_forward}}
Install the kernel and update initramfs:
<pre>
# dpkg -i [../linux-image-2.6.18-1-openvz_1_i386.deb # update-initramfs -c -k 2.6.18-1-openvz</pre>]
# On Hardware Node we generally need
# packet forwarding enabled and proxy arp disabled
INFO: update-initramfs is done, when make-kpkg is use with --initrd optionnet.ipv4.conf.default.forwarding=1net.ipv4.conf.default.proxy_arp=0net.ipv4.ip_forward=1
INFO: update-grub can be configured by /etc/kernel-img# Enables source route verificationnet.ipv4.conf.all.rp_filter=1
# Enables the magic-sysrq key
kernel.sysrq=1
Update the bootloader (when not done above)# TCP Explict Congestion Notification#net.ipv4.tcp_ecn=0
GRUB :# we do not want all our interfaces to send redirectsnet.ipv4.conf.default.send_redirects=1net.ipv4.conf.all.send_redirects=0
# [...]</usr/sbin/update-grubpre>
INFO: since the Debian ETCH # [sudo] sysctl -release the location of update-grub is moved from /sbin/update-grub to /usr/sbin/update-grub !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.}}
== install the toolset == # [sudo] ln -s /var/lib/vz /vz
You need the toolset for manage-ing OpenVZ Virtual Enviromennt (VE)=== OS templates ===
<pre> # apt{{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 -get install vzctl vzquota</pre>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}}
To install a container, you need OS template(s).
== modify needed settings ==Precreated templates can be found [http://wiki.openvz.org/Download/template/precreated here] and [http://download.openvz.org/contrib/template/precreated/ here].
You can create your own templates, see [[Debian Waytemplate creation]], [[Ubuntu Gutsy template creation]] and [[: Category: Templates]].
If you want network access for {{Note|Setup your prefered standard OS Template : edit the virtual server then you need to enable IP forwarding. Set "ip_forward" to yes in /etc/networkvz/optionvz.conf}}
# editor /etc/network/options[sudo] apt-get install vzctl-ostmpl-debian-5.0-i386-minimal
== Additional User Tools ==
; vzprocps
: A set of utilities to provide system information (vzps and vztop)
In some cases you may need to enable proxy_arp for the network devices that you want your virtual hosts to be accessible on.; [[vzdump]]You can add this : A utility to a specific interface in the network configuration (/etc/network/interfaces) by the following lines, replace %DEV% with your device name (ie. eth0)backup and restore container.
Example: # [sudo] apt-get install vzprocps vzdump
<pre>
[...]
# device: %DEV%
iface %DEV% inet static
address 192.168.0.2
netmask 255.255.255.0
network 192.168.2.0
broadcast 192.168.2.255
gateway 192.168.2.1
up sysctl -w netOn Debian squeeze, vzdump seems packaged in standard aptline.ipv4.conf.%DEV%.proxy_arp=1 pre-down sysctl -w net.ipv4.conf.%DEV%.proxy_arp=0 For lenny, See [[...Backup_of_a_running_container_with_vzdump]]</pre>
or use the /etc/network/if-up/ and /etc/network/if-pre-down.d/ directories.
INFO: # man 5 interfaces (to read more about debian's network interface configuration for ifup and ifdown)== Secure it ==
INFO: Please add If you want to use 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 magic-sysrq key, to your /etc/sysctlcontainer.conf
Iptables modules required by the container must be specified in the general vz.conf file or the vzXXX.conf file of the container.
plain OpenVZ Linux Way:Add the following line into vz.conf to activate the respective iptables modules for all containers.
Add settings to IPTABLES="/etc/sysctl.confip_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"
<pre> # On Hardware Node we generally need # packet forwarding enabled and proxy arp disabled net[[http://wiki.ipv4debian.ip_forward = 1 netorg/DebianFirewall][Configure]] your iptable rules inside the container.ipv4.conf.default.proxy_arp = 0
# Enables source route verification net.ipv4.conf.all.rp_filter = 1{{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}}
# Enables To make sure the magic-sysrq key kernel.sysrq = 1iptables rules are applied on a startup/reboot we'll create a new file:
# TCP Explict Congestion Notification # netnano /etc/network/if-pre-up.ipv4.tcp_ecn = 0d/iptables
# we do not want all our interfaces Add these lines to send redirects net.ipv4.conf.default.send_redirects = 1 net.ipv4.conf.all.send_redirects = 0 </pre>it:
#!/bin/bash
/sbin/iptables-restore < /etc/iptables.up.rules
<pre> INFOThe file needs to be executable so change the permissions: Suggestion: Please make a symlink from /var/lib/vz to /vz as backward compability to Main OpenVZ (Debian vz root directory is installed FHS-like to /var/lib/vz)
# ln -s chmod +x /varetc/libnetwork/vz if-pre-up.d/vz</pre>iptables
Start iptables
'''Before you restart you Server, keep in mind, that your system has all needed modules enabled; booting from your harddisk (e.g. hardware modules, raid system(s), lvm2 /etc). May you need a INITRD (initramdisk) or compile needed kernel modules statically in/init.'''d/iptables start
If the startup shows errors then you have probably not activated the needed iptables modules. See above.
# rebootCheck 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.
That's all== Start it!==
Now it's time to create a OS Template or download another precreated OS-Template # [sudo] /etc/init.d/vz start
This does not make the vz system automatically start at boot time. For automatic start:
INFO: Suggestions: Setup your default OS Template in /etc/# [sudo] update-rc.d vz/vz.confdefaults 98
== Use it! ==
After installing the OpenVZ kernel, user tools and a minimal OS template
to create a first container and do some [[basic operations in OpenVZ environment]]. Read the [[download:doc/OpenVZ-Users-Guide.pdf]], browse this wiki.
[[Category: HOWTO]]
[[Category: Debian]]
[[Category: Installation]]