= Stable ={{Warning|The majority of the content on this page only applies to older, unsupported Debian versions and is archived on this page for historical reasons only. '''The page you need is [[Installation on Debian]].'''}}
== Edit apt settings ==OpenVZ consists of a kernel, user-level tools, and container templates.
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>)
== Packages {{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.systsdebian.org (dso) ==/vzctl}}
precreated OpenVZ Debian Packages{{Note|By default, on Ubuntu systems root tasks are executed with [https://help.ubuntu.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>
== Installing the kernels and OpenVZ toolset ==Then '''apt-get update && apt-get dist-upgrade''' to upgrade to lenny.
Example: install the stable OpenVZ kernel, tools and debian OS Template== Kernel installation ==
# aptitude install ovzkernel-2.6.9 vzctl vzquota vzctl-ostmpl-debian=== Wheezy and Lenny ===
Maybe you need {{Note|The best kernel to update you "linuxuse is [[Download/kernel/rhel6|RHEL6-loader" like lilo or grub:based]]. Please see [[Install_kernel_from_RPM_on_Debian_6.0]]}}
for the "GRUB": # /sbin/grub-update=== Etch ===
Reboot in your new Debian Stable OpenVZ System==== 1. Using openvz kernel repositories ====
# reboot{{Note|In case you want to recompile the OpenVZ kernel yourself on Debian, see [[Compiling the OpenVZ kernel (the Debian way)]].}}
That's all :-)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 !! Description !! Hardware !! Debian Architecture
|-
! 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
|}
{| class=Etch (testing)="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>
OpenVZ is now a part of Debian Etch (a.k.a. "testing") repository. This article describes how to install OpenVZ on a Debian Etch system.===== Configuring the bootloader =====
== Installing In case GRUB is used as the utilities and kernel patch ==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:
To install the kernel-source, OpenVZ kernel patch and utilities, run the following:
<pre>
apt[...] title Debian GNU/Linux, kernel 2.6.18-ovz-028stab051.1-get update686 root (hd0,1)apt kernel /vmlinuz-get install linux2.6.18-ovz-028stab051.1-source686 root=/dev/sda5 ro vga=791 initrd /initrd.img-2.6.18 kernel-patchovz-028stab051.1-openvz vzctl vzquota686 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}} == Creating === Installing the kernel package user-level tools =====
First you need OpenVZ needs some user-level tools installed. Those are: ; vzctl: A utility to unpack the kernelcontrol OpenVZ containers (create, destroy, start, stop, set parameters etc.); vzquota:A utility to manage quotas for containers. Mostly used indirectly (by vzctl).
<pre>
cd /usr/srctar xjf linux # [sudo] apt-source-2.6.18cd linux-source-2.6.18get install vzctl vzquota
</pre>
Next, you need to get a kernel config. You can use the config of the debian-kernel:==== 2 Using Debian lenny repositories ====
If you upgrade to lenny, you can search openvz kernel and can install with:
<pre>
apt-get install linux-image-openvz-686
</pre>
this command will install latest kernel and all required packages like:
<pre>
cp /boot/configapt-get install iproute libatm1 linux-image-2.6.1826-31-openvz-686 .configlinux-image-openvz-686 rsync vzctl vzquota libcgroup-dev
</pre>
and will arrange grub bootloader properly.
Now you can apply openvz === Rebooting into OpenVZ kernel patch and compile the 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.}}
Now reboot the machine and choose the OpenVZ Linux Kernel on the boot loader menu. If the OpenVZ kernel has been booted successfully, proceed to installing the user-level tools for OpenVZ.
=== Confirm proper installation ===
1. Kernel:
<pre>
make # uname -kpkg --append_to_version=r 2.6.26-1-openvz --added_patches=openvz --revision=1 kernel_image686 #
</pre>
You will have to answer some conifg-questions2.Openvz kernel facility:<pre> # ps ax | grep vz 2349 ? S 0:00 [vzmond]</pre>
== Install the kernel package ==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>
Install == Configuring == === sysctl === 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, automatically inserts these options at the kernel and update initramfs:last of <tt>/etc/sysctl.conf</tt>, except for net.ipv4.ip_forward}}
<pre>
cd [...] # On Hardware Node we generally need# packet forwarding enabled and proxy arp disabled net.ipv4.conf.default.forwarding=1net.ipv4.conf.default.proxy_arp=0net.ipv4.ip_forward=1 # Enables source route verificationdpkg -i linux-image-2net.ipv4.conf.6all.18rp_filter=1 # Enables the magic-sysrq keykernel.sysrq=1-openvz_1_i386 # TCP Explict Congestion Notification#net.ipv4.debtcp_ecn=0 update-initramfs -c -k 2# we do not want all our interfaces to send redirectsnet.ipv4.conf.6default.18-send_redirects=1-openvzupdate-grubnet.ipv4.conf.all.send_redirects=0 [...]
</pre>
Just reboot # [sudo] sysctl -p {{Note|You can make a symlink from /var/lib/vz to /vz as backwardcompatibility to OpenVZ as installed in other distributions(Debian vz root directory is /var/lib/vz to be FHS-compliant.}} # [sudo] ln -s /var/lib/vz /vz === OS templates === {{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}} To install a container, you need OS template(s). 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 template creation]], [[Ubuntu Gutsy template creation]] and [[:Category: Templates]]. {{Note|Setup your prefered standard OS Template : edit the /etc/vz/vz.conf}} # [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) ; [[vzdump]]: A utility to backup and restore container. # [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 openvzfile: 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 OS templateto 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]]