Difference between revisions of "Installation on Debian/old"

From OpenVZ Virtuozzo Containers Wiki
Jump to: navigation, search
m (precompiled kernel images at debian.systs.org (dso))
(add a big fat warning)
 
(113 intermediate revisions by 49 users not shown)
Line 1: Line 1:
= Sarge-Dapper (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]].'''}}
The OpenVZ packages at http://debian.systs.org/ aimed to install OpenVZ in a easy way, some task are done on install process!
 
  
 +
OpenVZ consists of a kernel, user-level tools, and container templates.
  
== edit apt source settings ==
+
This guide tells how to install the kernel and the tools on [http://www.debian.org Debian] Etch or Lenny/Squeeze.  
Add to your "/etc/apt/sources.list"
 
  
<pre>
+
For Squeeze, use the Lenny directions.
  deb http://debian.systs.org/ sarge openvz
+
 
</pre>
+
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's recommended that you use a separate partition for container private
 +
directories (by default <code>/var/lib/vz/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.
  
and get the new package lists
+
=== Repository setup (Etch only) ===
  
<pre>
+
'''If you are using Debian Lenny, this step in no longer required. Openvz kernel packages and tools are available on main repository.'''
# apt-get update
 
</pre>
 
  
 +
==== 1. Using openvz.org repositories ====
  
== precompiled kernel images at debian.systs.org (dso) ==
+
At the moment two different repositories are online at http://download.openvz.org:
The kernel-images on debian.systs.org (dso) use the same kernel-config taken from OpenVZ.
 
(most kernel-modules are built-in!)
 
  
If there is more than one CPU available (or a CPU with hyperthreading), use the kernel-smp RPM.
+
; by Ola Lundqvist <opal@debian.org>
If there is more than 4 Gb of RAM available, use the kernel-enterprise RPM.
+
: (OpenVZ kernels only)
Otherwise, use the plain kernel RPM (kernel).
+
: apt-uri http://download.openvz.org/debian
  
{| class="wikitable"
+
; by Thorsten Schifferdecker <tsd@debian.systs.org>
|+'''Kernel flavors list'''
+
: apt-uri http://download.openvz.org/debian-systs
! Kernel type !! Description !! Hardware !! Use case
+
: (Mirror of OpenVZ Repository from http://debian.systs.org/)
|-
 
! -
 
| uniprocessor
 
| up to 4GB of RAM
 
|
 
|-
 
! -smp
 
| symmetric multiprocessor
 
| up to 4 GB of RAM
 
| 10-20 VPSs
 
|-
 
! -entnosplit
 
| SMP + PAE support
 
| up to 64 GB of RAM
 
| 10-30 VPSs
 
|-
 
! -enterprise
 
| SMP + PAE support + 4/4GB split
 
| up to 64 GB of RAM
 
| >20-30 VPSs
 
|}
 
  
kernel(s) for i368 and amd64
+
{{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}}
<pre>
 
ovzkernel-2.6.9
 
ovzkernel-2.6.9-enterprise
 
ovzkernel-2.6.9-entnosplit
 
ovzkernel-2.6.9-smp
 
  
ovzkernel-2.6.18
+
{{Note|By default, on Ubuntu systems root tasks are executed with [https://help.ubuntu.com/community/RootSudo sudo]}}
ovzkernel-2.6.18-enterprise
 
ovzkernel-2.6.18-smp
 
</pre>
 
  
i386 only:
+
This can be done via the following commands, as root or as privileged "sudo" user
 
<pre>
 
<pre>
ovzkernel-2.6.18-enterprise   
+
# 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>
 
</pre>
  
OpenVZ tool(s) for i386 and amd64
+
==== 2. Using Debian repositories (upgrade to lenny) ====
 +
 
 +
There is even a '''lenny''' repository with kernel 2.6.28. '''Use it at your own risk!'''
 +
 
 +
Add lenny repositories to your '''/etc/apt/sources.list'''
 
<pre>
 
<pre>
vzctl
+
deb http://DEBIAN-MIRROR/debian/ testing main
vzquota
+
deb http://DEBIAN-MIRROR/debian-security/ testing/updates main
vzprocps
 
vzdump
 
 
</pre>
 
</pre>
  
template(s) for i368 and amd64 : Debian 3.1 Minimal
+
Enlarge apt-cache adding to '''/etc/apt/apt.conf''' this line:
 
<pre>
 
<pre>
vzctl-ostmpl-debian
+
APT::Cache-Limit "100000000";
 
</pre>
 
</pre>
  
== installing the kernel-images, toolset and debian-os-template ==
+
Give etch package priority over lenny packages. Edit '''/etc/apt/preferences''' and set like this:
Example: install the stable OpenVZ kernel, tools and Debian OS Template
+
<pre>
 +
Package: *
 +
Pin: release a=etch
 +
Pin-Priority: 700
  
# aptitude install ovzkernel-2.6.9 vzctl vzquota vzdump vzctl-ostmpl-debian
+
Package: *
 +
Pin: release a=lenny
 +
Pin-Priority: 650
 +
</pre>
  
 +
Then '''apt-get update && apt-get dist-upgrade''' to upgrade to lenny.
  
Maybe you need to update your "linux-loader" (can be configured at /etc/kernel-img.conf)
+
== Kernel installation ==
  
for the "GRUB":
+
=== Wheezy and Lenny ===
  
# /sbin/grub-update
+
{{Note|The best kernel to use is [[Download/kernel/rhel6|RHEL6-based]]. Please see [[Install_kernel_from_RPM_on_Debian_6.0]]}}
  
 +
=== 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)]].}}
  
 +
First, you need to choose what kernel you want to install.
  
That's all :-)
+
{| 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
 +
|}
  
Now it's time to setup your VE's with the minimal Debian-3.1 Template, create new one or download another precreated OS-Template.
+
{| 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
 +
|-
 +
|}
  
= Etch (Testing) =
+
<pre>
OpenVZ is now a part of Debian Etch (a.k.a. "testing") repository.
+
# apt-get install <kernel>
 +
</pre>
  
== install the kernel-image ==
+
===== Configuring the bootloader =====
  
=== use precomiled kernel images ===
+
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:
Can be found at http://download.openvz.org/kernel/debian/etch/
 
  
 
<pre>
 
<pre>
List of precompiled kernel-images
+
[...]
 
+
  title          Debian GNU/Linux, kernel 2.6.18-ovz-028stab051.1-686
linux-image-2.6.18-openvz-486_02_i386.deb
+
  root            (hd0,1)
linux-image-2.6.18-openvz-686_02_i386.deb
+
  kernel          /vmlinuz-2.6.18-ovz-028stab051.1-686 root=/dev/sda5 ro vga=791
linux-image-2.6.18-openvz-amd64_01_amd64.deb
+
  initrd          /initrd.img-2.6.18-ovz-028stab051.1-686
linux-image-2.6.18-openvz-ia64_01_ia64.deb
+
  savedefault
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-sparc64_01_sparc.deb     
 
 
</pre>
 
</pre>
  
Example: Installing an OpenVZ precompiled Debian Kernel-Image for an i686:
+
{{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}}
  
<pre>
+
===== Installing the user-level tools =====
# wget http://download.openvz.org/kernel/debian/etch/linux-image-2.6.18-openvz-686_02_i386.deb
 
# dpkg -i linux-image-2.6.18-openvz-686_02_i386.deb
 
</pre>
 
  
 +
OpenVZ needs some user-level tools installed. Those are:
  
=== or build your own kernel-image (debian way) ===
+
; 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).
  
To install the kernel-source and the OpenVZ kernel patch, run:
 
 
<pre>
 
<pre>
  # apt-get install kernel-package linux-source-2.6.18 kernel-patch-openvz libncurses5-dev
+
  # [sudo] apt-get install vzctl vzquota
 
</pre>
 
</pre>
  
 +
==== 2 Using Debian lenny repositories ====
  
Unpack the kernel-source:
+
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>
 
<pre>
# cd /usr/src
+
apt-get install iproute libatm1 linux-image-2.6.26-1-openvz-686 linux-image-openvz-686 rsync vzctl vzquota libcgroup-dev
# tar xjf linux-source-2.6.18.tar.bz2
 
# cd linux-source-2.6.18
 
 
</pre>
 
</pre>
 +
and will arrange grub bootloader properly.
  
 +
=== Rebooting into OpenVZ kernel ===
  
You need a kernel config.
+
{{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.}}
You can use the config of the debian-kernel:
+
 
<pre>
+
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.
# cp /boot/config-2.6.18-3-686 .config
 
</pre>
 
  
 +
=== Confirm proper installation ===
  
Or get a 2.6.18 kernel config from http://download.openvz.org/kernel/devel/current/configs/
+
1. Kernel:
 
<pre>
 
<pre>
  # wget http://download.openvz.org/kernel/devel/current/configs/kernel-2.6.18-028test010-i686.config.ovz -O .config
+
  # uname -r
 +
2.6.26-1-openvz-686
 +
#
 
</pre>
 
</pre>
  
 
+
2. Openvz kernel facility:
Now you can apply openvz kernel patch and modify your kernel-config:
 
 
<pre>
 
<pre>
  # ../kernel-patches/all/apply/openvz
+
  # ps ax | grep vz
  # make menuconfig
+
  2349 ?        S      0:00 [vzmond]
 
</pre>
 
</pre>
  
 
+
3. A network interface for containers:
You need following OpenVZ kernel config settings:
 
 
<pre>
 
<pre>
(taken from a OpenVZ Kernel 2.6.18-028test010.1 on 686)
+
# 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>
  
Filesystem
+
== Configuring ==
\_ [*] Second extended fs support (CONFIG_EXT2_FS)
 
\_ [*] Ext3 journalling file system support (CONFIG_EXT3_FS)
 
\_ [*] Quota Support (CONFIG_QUOTA)
 
\_ [*] Compatibility with older quotactl interface (CONFIG_QUOTA_COMPAT)
 
\_ [*]Quota format v2 support (CONFIG_QFMT_V2)
 
\_ [*] VPS filesystem (CONFIG_SIM_FS)
 
\_ [*] Virtuozzo Disk Quota support (CONFIG_VZ_QUOTA)
 
\-> [*] Per-user and per-group quota in Virtuozzo quota partitions (VZ_QUOTA_UGID)
 
  
OpenVZ ... (what else :-)
+
=== sysctl ===
\_[*] Virtual Environment support (CONFIG_VE)
 
\_ <M> VE calls interface (CONFIG_VE_CALLS)
 
\_ <M> VE networking (CONFIG_VE_NETDEV)
 
\_ <M> Virtual ethernet device (CONFIG_VE_ETHDEV)
 
\_ <M> VE device (CONFIG_VZ_DEV)
 
\_ [*] VE netfiltering (CONFIG_VE_IPTABLES)
 
\_ <M> VE watchdog module (CONFIG_VZ_WDOG)
 
\_ <M> Checkpointing & restoring Virtual Environments (CONFIG_VZ_CHECKPOINT)
 
  
User resources ... (User Beancounters)
+
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.
\_ [*] Enable user resource accounting (CONFIG_USER_RESOURCE)
 
\_ [*] Account physical memory usage ( CONFIG_USER_RSS_ACCOUNTING)
 
\_ [*] Account disk IO (CONFIG_UBC_IO_ACCT)
 
\_ [*] Account swap usage (CONFIG_USER_SWAP_ACCOUNTING)
 
\_ [*] Report resource usage in /proc (CONFIG_USER_RESOURCE_PROC)
 
\_ [*] User resources debug features (CONFIG_UBC_DEBUG)
 
\_ [*] Debug kmemsize with cache counters (CONFIG_UBC_DEBUG_KMEM)
 
</pre>
 
  
 +
{{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}}
  
 
<pre>
 
<pre>
INFO: Better to build the kernel-headers as well, so afterward other kernel-modules can
+
[...]
      built without whole kernel tree (e.g. drbd -> drbd0.7-module-source)
+
 
      See also :
+
# On Hardware Node we generally need
      # make-kpkg --targets
+
# packet forwarding enabled and proxy arp disabled
</pre>
 
  
 +
net.ipv4.conf.default.forwarding=1
 +
net.ipv4.conf.default.proxy_arp=0
 +
net.ipv4.ip_forward=1
  
Compile your Kernel (as user root, or you need the --rootcmd!)
+
# Enables source route verification
<pre>
+
net.ipv4.conf.all.rp_filter=1
# make-kpkg --append_to_version=-1-openvz --added_patches=openvz --revision=1 --initrd binary-arch
 
 
  or all above with one step
 
  
# make-kpkg --append_to_version=-1-openvz --added_patches=openvz --revision=1 --initrd --config menuconfig binary-arch
+
# Enables the magic-sysrq key
</pre>
+
kernel.sysrq=1
  
 +
# TCP Explict Congestion Notification
 +
#net.ipv4.tcp_ecn=0
  
Install the kernel and update initramfs:
+
# we do not want all our interfaces to send redirects
<pre>
+
net.ipv4.conf.default.send_redirects=1
# dpkg -i ../linux-image-2.6.18-1-openvz_1_i386.deb
+
net.ipv4.conf.all.send_redirects=0
# update-initramfs -c -k 2.6.18-1-openvz
 
</pre>
 
  
<pre>
+
[...]
INFO: update-initramfs is done, when make-kpkg is use with --initrd option
 
INFO: update-grub can be configured by /etc/kernel-img.conf
 
 
</pre>
 
</pre>
  
Update the bootloader (when not done above)
+
  # [sudo] sysctl -p
  
GRUB :
+
{{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.}}
  
# /usr/sbin/update-grub
+
  # [sudo] ln -s /var/lib/vz /vz
  
INFO: since the Debian ETCH-release the location of update-grub is moved from /sbin/update-grub to /usr/sbin/update-grub !
+
=== 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}}
  
== install the toolset ==
+
To install a container, you need OS template(s).
  
You need the toolset for manage-ing OpenVZ Virtual Enviromennt (VE)
+
Precreated templates can be found [http://wiki.openvz.org/Download/template/precreated here] and [http://download.openvz.org/contrib/template/precreated/ here].
  
<pre>
+
You can create your own templates, see
# apt-get install vzctl vzquota
+
[[Debian template creation]], [[Ubuntu Gutsy template creation]] and [[:Category: Templates]].
</pre>
 
  
 +
{{Note|Setup your prefered standard OS Template : edit the /etc/vz/vz.conf}}
  
== modify needed settings ==
+
  # [sudo] apt-get install vzctl-ostmpl-debian-5.0-i386-minimal
  
a Debian Way:
+
== Additional User Tools ==
  
If you want network access for the virtual server then you need to enable IP forwarding. Set "ip_forward" to yes in /etc/network/option.
+
; vzprocps
 +
:    A set of utilities to provide system information (vzps and vztop)
  
# editor /etc/network/options
+
; [[vzdump]]
 +
:    A utility to backup and restore container.
  
 +
  # [sudo] apt-get install vzprocps vzdump
  
  
In some cases you may need to enable proxy_arp for the network devices that you want your virtual hosts to be accessible on.
+
On Debian squeeze, vzdump seems packaged in standard aptline. For lenny, See [[Backup_of_a_running_container_with_vzdump]]
You can add this to a specific interface in the network configuration (/etc/network/interfaces) by the following lines, replace %DEV% with your device name (ie. eth0).
 
  
Example:
 
  
<pre>
+
== Secure it ==
[...]
 
# 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 net.ipv4.conf.%DEV%.proxy_arp=0
+
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.
        pre-down sysctl -w net.ipv4.conf.%DEV%.proxy_arp=1
 
[...]
 
</pre>
 
  
or use the /etc/network/if-up/ and /etc/network/if-down.d/ directories.
+
Iptables modules required by the container must be specified in the general vz.conf file or the vzXXX.conf file of the container.
 
 
<pre>
 
INFO: # man 5 interfaces (to read more about debian's network interface configuration for ifup and ifdown)
 
INFO: Please add to use the magic-sysrq key, to your /etc/sysctl.conf
 
</pre>
 
  
a (plain) OpenVZ Linux Way:
+
Add the following line into vz.conf to activate the respective iptables modules for all containers.
  
Add settings to "/etc/sysctl.conf"
+
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"
  
<pre>
+
[[http://wiki.debian.org/DebianFirewall][Configure]] your iptable rules inside the container.
# On Hardware Node we generally need
 
# packet forwarding enabled and proxy arp disabled
 
net.ipv4.ip_forward = 1
 
net.ipv4.conf.default.proxy_arp = 0
 
  
# Enables source route verification
+
{{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}}
net.ipv4.conf.all.rp_filter = 1
 
  
# Enables the magic-sysrq key
+
To make sure the iptables rules are applied on a startup/reboot we'll create a new file:
kernel.sysrq = 1
 
  
  # TCP Explict Congestion Notification
+
  nano /etc/network/if-pre-up.d/iptables
# net.ipv4.tcp_ecn = 0
 
  
# we do not want all our interfaces to send redirects
+
Add these lines to it:
net.ipv4.conf.default.send_redirects = 1
 
net.ipv4.conf.all.send_redirects = 0
 
</pre>
 
  
 +
#!/bin/bash
 +
/sbin/iptables-restore < /etc/iptables.up.rules
  
<pre>
+
The file needs to be executable so change the permissions:
INFO: 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 /var/lib/vz /vz
+
  chmod +x /etc/network/if-pre-up.d/iptables
</pre>
 
  
 +
Start iptables
  
'''Before you restart your 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.'''
+
/etc/init.d/iptables start
  
 +
If the startup shows errors then you have probably not activated the needed iptables modules. See above.
  
# reboot
+
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.
  
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/vz/vz.conf
+
  # [sudo] update-rc.d vz defaults 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: HOWTO]]
 +
[[Category: Debian]]
 
[[Category: Installation]]
 
[[Category: Installation]]

Latest revision as of 20:30, 8 October 2013

Warning.svg 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.

OpenVZ consists of a kernel, user-level tools, and container templates.

This guide tells how to install the kernel and the tools on Debian Etch 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/. 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 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[edit]

Filesystems[edit]

It's recommended that you use a separate partition for container private directories (by default /var/lib/vz/private/<CTID>). 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)[edit]

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[edit]

At the moment two different repositories are online at http://download.openvz.org:

by Ola Lundqvist <opal@debian.org>
(OpenVZ kernels only)
apt-uri http://download.openvz.org/debian
by Thorsten Schifferdecker <tsd@debian.systs.org>
apt-uri http://download.openvz.org/debian-systs
(Mirror of OpenVZ Repository from http://debian.systs.org/)
Yellowpin.svg 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
Yellowpin.svg Note: By default, on Ubuntu systems root tasks are executed with sudo

This can be done via the following commands, as root or as privileged "sudo" user

# 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

2. Using Debian repositories (upgrade to lenny)[edit]

There is even a lenny repository with kernel 2.6.28. Use it at your own risk!

Add lenny repositories to your /etc/apt/sources.list

deb http://DEBIAN-MIRROR/debian/ testing main
deb http://DEBIAN-MIRROR/debian-security/ testing/updates main

Enlarge apt-cache adding to /etc/apt/apt.conf this line:

APT::Cache-Limit "100000000";

Give etch package priority over lenny packages. Edit /etc/apt/preferences and set like this:

Package: *
Pin: release a=etch
Pin-Priority: 700

Package: *
Pin: release a=lenny
Pin-Priority: 650

Then apt-get update && apt-get dist-upgrade to upgrade to lenny.

Kernel installation[edit]

Wheezy and Lenny[edit]

Yellowpin.svg Note: The best kernel to use is RHEL6-based. Please see Install_kernel_from_RPM_on_Debian_6.0

Etch[edit]

1. Using openvz kernel repositories[edit]

Yellowpin.svg 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.

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
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
 # apt-get install <kernel>
Configuring the bootloader[edit]

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 /boot/grub/menu.lst file:

[...]
  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
[...]
Yellowpin.svg 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
Installing the user-level tools[edit]

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).
 # [sudo] apt-get install vzctl vzquota

2 Using Debian lenny repositories[edit]

If you upgrade to lenny, you can search openvz kernel and can install with:

apt-get install linux-image-openvz-686

this command will install latest kernel and all required packages like:

apt-get install iproute libatm1 linux-image-2.6.26-1-openvz-686 linux-image-openvz-686 rsync vzctl vzquota libcgroup-dev

and will arrange grub bootloader properly.

Rebooting into OpenVZ kernel[edit]

Warning.svg 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[edit]

1. Kernel:

 # uname -r
 2.6.26-1-openvz-686
 #

2. Openvz kernel facility:

 # ps ax | grep vz
 2349 ?        S      0:00 [vzmond]

3. A network interface for containers:

 # 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)

Configuring[edit]

sysctl[edit]

There are a number of kernel parameters that should be set for OpenVZ to work correctly. These parameters are stored in /etc/sysctl.conf file. Here is the relevant part of the file; please edit it accordingly.

Yellowpin.svg Note: vzctl version from debian-systs, automatically inserts these options at the last of /etc/sysctl.conf, except for net.ipv4.ip_forward
[...]

# On Hardware Node we generally need
# packet forwarding enabled and proxy arp disabled

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=1
net.ipv4.conf.all.send_redirects=0

[...]
 # [sudo] sysctl -p
Yellowpin.svg 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.

 # [sudo] ln -s /var/lib/vz /vz

OS templates[edit]

Yellowpin.svg 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 here and here.

You can create your own templates, see Debian template creation, Ubuntu Gutsy template creation and Category: Templates.

Yellowpin.svg 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[edit]

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[edit]

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"

[[1][Configure]] your iptable rules inside the container.

Warning.svg 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![edit]

# [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![edit]

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.