OpenVZ Virtuozzo Containers Wiki - User contributions [en]

Using private IPs for Hardware Nodes

2008-12-01T01:55:32Z

Ysidoro: /* Create On-umount script for remove HW → CT route(s) */ where to put vps.umount script

This article describes how to assign public IPs to containers running on OVZ Hardware Nodes in case you have a following network topology:

[[Image:PrivateIPs_fig1.gif|An initial network topology]]

== Prerequisites ==
This configuration was tested on a RHEL5 OpenVZ Hardware Node and a container based on a Fedora Core 5 template.
Other host OSs and templates might require some configuration changes, please add corresponding OS specific changes if you've faced any.

This article assumes the presence of 'brctl', 'ip' and 'ifconfig' utils. You may need to install missing packages like 'bridge-utils'/'iproute'/'net-tools' or others which contain those utilities.

This article assumes you have already [[Quick installation|installed OpenVZ]],
prepared the [[OS template cache]](s) and have
[[Basic_operations_in_OpenVZ_environment|container(s) created]]. If not, follow the links to perform the steps needed.
{{Note|don't assign an IP after container creation.}}

== An OVZ Hardware Node has the only one Ethernet interface ==
(assume eth0)

=== Hardware Node configuration ===

==== Create a bridge device ====
[HN]# brctl addbr br0

==== Remove an IP from eth0 interface ====
[HN]# ifconfig eth0 0

==== Add eth0 interface into the bridge ====
[HN]# brctl addif br0 eth0

==== Assign the IP to the bridge ====
(the same that was assigned on eth0 earlier)
[HN]# ifconfig br0 10.0.0.2/24

==== Resurrect the default routing ====
[HN]# ip route add default via 10.0.0.1 dev br0

{{Warning|if you are '''configuring''' the node '''remotely''' you '''must''' prepare a '''script''' with the above commands and run it in background with the redirected output or you'll '''lose the access''' to the Node.}}

==== A script example ====
<pre>
[HN]# cat /tmp/br_add
#!/bin/bash

brctl addbr br0
ifconfig eth0 0
brctl addif br0 eth0
ifconfig br0 10.0.0.2/24
ip route add default via 10.0.0.1 dev br0
</pre>

[HN]# /tmp/br_add >/dev/null 2>&1 &

=== Container configuration ===

==== Start a container ====
[HN]# vzctl start 101

==== Add a [[Virtual_Ethernet_device|veth interface]] to the container ====
[HN]# vzctl set 101 --netif_add eth0 --save

==== Set up an IP to the newly created container's veth interface ====
[HN]# vzctl exec 101 ifconfig eth0 85.86.87.195/26

==== Add the container's veth interface to the bridge ====
[HN]# brctl addif br0 veth101.0

{{Note|There will be a delay of about 15 seconds(default for 2.6.18 kernel) while the bridge software runs STP to detect loops and transitions the veth interface to the forwarding state.
}}

==== Set up the default route for the container ====
[HN]# vzctl exec 101 ip route add default via 85.86.87.193 dev eth0

==== (Optional) Add CT↔HN routes ====
The above configuration provides the following connections:
* CT X ↔ CT Y (where CT X and CT Y can locate on any OVZ HN)
* CT ↔ Internet

Note that

* The accessability of the CT from the HN depends on the local gateway providing NAT (probably - yes)

* The accessability of the HN from the CT depends on the ISP gateway being aware of the local network (probably not)

So to provide CT ↔ HN accessibility despite the gateways' configuration you can add the following routes:

[HN]# ip route add 85.86.87.195 dev br0
[HN]# vzctl exec 101 ip route add 10.0.0.2 dev eth0

=== Resulting OpenVZ Node configuration ===
[[Image:PrivateIPs_fig2.gif|Resulting OpenVZ Node configuration]]

=== Making the configuration persistent ===

==== Set up a bridge on a HN ====
This can be done by configuring the <code>ifcfg-*</code> files located in <code>/etc/sysconfig/network-scripts/</code>.

Assuming you had a configuration file (e.g. <code>ifcfg-eth0</code>) like:
<pre>
DEVICE=eth0
ONBOOT=yes
IPADDR=10.0.0.2
NETMASK=255.255.255.0
GATEWAY=10.0.0.1
</pre>

To automatically create bridge <code>br0</code> you can create <code>ifcfg-br0</code>:
<pre>
DEVICE=br0
TYPE=Bridge
ONBOOT=yes
IPADDR=10.0.0.2
NETMASK=255.255.255.0
GATEWAY=10.0.0.1
</pre>

and edit <code>ifcfg-eth0</code> to add the <code>eth0</code> interface into the bridge <code>br0</code>:
<pre>
DEVICE=eth0
ONBOOT=yes
BRIDGE=br0
</pre>

==== Edit the container's configuration ====
Add these parameters to the <code>/etc/vz/conf/$CTID.conf</code> file which will be used during the network configuration:
* Add/change <code>CONFIG_CUSTOMIZED="yes"</code> (indicates that a custom
script should be run on a container start)
* Add <code>VETH_IP_ADDRESS="IP/MASK"</code> (a container can have multiple
IPs separated by spaces)
* Add <code>VE_DEFAULT_GATEWAY="CT DEFAULT GATEWAY"</code>
* Add <code>BRIDGEDEV="BRIDGE NAME"</code> (a bridge name to which the
container veth interface should be added)

An example:
<pre>
# Network customization section
CONFIG_CUSTOMIZED="yes"
VETH_IP_ADDRESS="85.86.87.195/26"
VE_DEFAULT_GATEWAY="85.86.87.193"
BRIDGEDEV="br0"
</pre>

==== Create a custom network configuration script ====
which should be called each time a container is started (e.g. <code>/usr/sbin/vznetcfg.custom</code>):
<pre>
#!/bin/bash
# /usr/sbin/vznetcfg.custom
# a script to bring up bridged network interfaces (veth's) in a container

GLOBALCONFIGFILE=/etc/vz/vz.conf
CTCONFIGFILE=/etc/vz/conf/$VEID.conf
vzctl=/usr/sbin/vzctl
brctl=/usr/sbin/brctl
ip=/sbin/ip
ifconfig=/sbin/ifconfig
. $GLOBALCONFIGFILE
. $CTCONFIGFILE

NETIF_OPTIONS=`echo $NETIF | sed 's/,/\n/g'`
for str in $NETIF_OPTIONS; do \
# getting 'ifname' parameter value
if echo "$str" | grep -o "^ifname=" ; then
# remove the parameter name from the string (along with '=')
CTIFNAME=${str#*=};
fi
# getting 'host_ifname' parameter value
if echo "$str" | grep -o "^host_ifname=" ; then
# remove the parameter name from the string (along with '=')
VZHOSTIF=${str#*=};
fi
done

if [ ! -n "$VETH_IP_ADDRESS" ]; then
echo "According to $CONFIGFILE CT$VEID has no veth IPs configured."
exit 1
fi

if [ ! -n "$VZHOSTIF" ]; then
echo "According to $CONFIGFILE CT$VEID has no veth interface configured."
exit 1
fi

if [ ! -n "$CTIFNAME" ]; then
echo "Corrupted $CONFIGFILE: no 'ifname' defined for host_ifname $VZHOSTIF."
exit 1
fi

echo "Initializing interface $VZHOSTIF for CT$VEID."
$ifconfig $VZHOSTIF 0

CTROUTEDEV=$VZHOSTIF

if [ -n "$BRIDGEDEV" ]; then
echo "Adding interface $VZHOSTIF to the bridge $BRIDGEDEV."
CTROUTEDEV=$BRIDGEDEV
$brctl addif $BRIDGEDEV $VZHOSTIF
fi

# Up the interface $CTIFNAME link in CT$VEID
$vzctl exec $VEID $ip link set $CTIFNAME up

for IP in $VETH_IP_ADDRESS; do
echo "Adding an IP $IP to the $CTIFNAME for CT$VEID."
$vzctl exec $VEID $ip address add $IP dev $CTIFNAME

# removing the netmask
IP_STRIP=${IP%%/*};

echo "Adding a route from CT0 to CT$VEID using $IP_STRIP."
$ip route add $IP_STRIP dev $CTROUTEDEV
done

if [ -n "$CT0_IP" ]; then
echo "Adding a route from CT$VEID to CT0."
$vzctl exec $VEID $ip route add $CT0_IP dev $CTIFNAME
fi

if [ -n "$VE_DEFAULT_GATEWAY" ]; then
echo "Setting $VE_DEFAULT_GATEWAY as a default gateway for CT$VEID."
$vzctl exec $VEID \
$ip route add default via $VE_DEFAULT_GATEWAY dev $CTIFNAME
fi

exit 0
</pre>
<p><small>Note: this script can be easily extended to work for multiple triples <bridge, ip address, veth device>, see http://vireso.blogspot.com/2008/02/2-veth-with-2-brindges-on-openvz-at.html </small></p>

==== Make the script to be run on a container start ====
In order to run above script on a container start create the file
<code>/etc/vz/vznet.conf</code> with the following contents:

EXTERNAL_SCRIPT="/usr/sbin/vznetcfg.custom"

{{Note|<code>/usr/sbin/vznetcfg.custom</code> should be executable (chmod +x /usr/sbin/vznetcfg.custom)}}

{{Note|When CT is stoped there are HW → CT route(s) still present in route table. We can use On-umount script for solve this.}}

==== Create On-umount script for remove HW → CT route(s) ====
which should be called each time a container with VEID (<code>/etc/sysconfig/vz/$VEID.umount</code>), or any container (<code>/etc/sysconfig/vz/vps.umount</code>) is stoped.

On a Debian system you can have per VE mount/umount scripts /etc/vz/conf/${VEID}.{mount|umount}
or mount/umount scripts which all VEs will run /etc/vz/conf/vps.{mount|umount}
<pre>
#!/bin/bash
# /etc/sysconfig/vz/$VEID.umount or /etc/sysconfig/vz/vps.umount
# a script to remove routes to container with veth-bridge from bridge

CTCONFIGFILE=/etc/vz/conf/$VEID.conf
ip=/sbin/ip
. $CTCONFIGFILE

if [ ! -n "$VETH_IP_ADDRESS" ]; then
exit 0
fi

if [ ! -n "$BRIDGEDEV" ]; then
exit 0
fi

for IP in $VETH_IP_ADDRESS; do
# removing the netmask
IP_STRIP=${IP%%/*};

echo "Remove a route from CT0 to CT$VEID using $IP_STRIP."
$ip route del $IP_STRIP dev $BRIDGEDEV
done

exit 0
</pre>

{{Note|The script should be executable (chmod +x /etc/sysconfig/vz/vps.umount)}}

==== Setting the route CT → HN ====
To set up a route from the CT to the HN, the custom script has to get a HN IP (the $CT0_IP variable in the script). There are several ways to specify it:

# Add an entry CT0_IP="CT0 IP" to the <code>$VEID.conf</code>
# Add an entry CT0_IP="CT0 IP" to the <code>/etc/vz/vz.conf</code> (the global configuration config file)
# Implement some smart algorithm to determine the CT0 IP right in the custom network configuration script

Each variant has its pros and cons, nevertheless for HN static IP configuration variant 2 seems to be acceptable (and the most simple).

== An OpenVZ Hardware Node has two Ethernet interfaces ==
Assuming you have 2 interfaces eth0 and eth1 and want to separate local traffic (10.0.0.0/24) from external traffic.
Let's assign eth0 for the external traffic and eth1 for the local one.

If there is no need to make the container accessible from the HN and vice versa, it's enough to replace 'br0' with 'eth1' in the following steps of the above configuration:
* Hardware Node configuration → [[Using_private_IPs_for_Hardware_Nodes#Assign_the_IP_to_the_bridge|Assign the IP to the bridge]]
* Hardware Node configuration → [[Using_private_IPs_for_Hardware_Nodes#Resurrect_the_default_routing|Resurrect the default routing]]

It is nesessary to set a local IP for 'br0' to ensure CT ↔ HN connection availability.

== Putting containers to different subnetworks ==
It's enough to set up the correct $VETH_IP_ADDRESS and $VE_DEFAULT_GATEWAY values in the
[[Using_private_IPs_for_Hardware_Nodes#Edit_the_container.27s_configuration|above configuration]].

== See also ==
* [[Virtual network device]]
* [[Differences between venet and veth]]

[[Category: HOWTO]]
[[Category: Networking]]

User:Ysidoro

2008-11-29T18:33:31Z

Ysidoro: Helly

= Ysidoro =

Hello, I am Rodolfo Pilas, you can reach me at http://www.pilas.net/

Installation on Debian/old

2008-11-29T18:30:48Z

Ysidoro: introduction how to partialy upgrade to lenny

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] stable.

Additionally, this document explain how to partialy upgrade to Debian testing (lenny) and install from lenny repositories ('''use this options at your risk''').

== Requirements ==

=== Filesystems ===
It is recommended to use a separate partition for container private
directories (by default <code>/var/lib/vz/private/<CTID></code>). The reason why you should do so is that if you wish to use 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 usual Linux disk quota used in container, not on [[HN]].

At least try to avoid using root partition for containers because the root user of 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 so use one of these filesystems (ext3 is recommended) if you need per-container disk quota.

=== Repository setup ===

==== 1. Using openvz.org repositories ====

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

{{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}}

{{Note|By default, on Ubuntu systems root tasks are executed with [https://help.ubuntu.com/community/RootSudo sudo]}}

This can be achieved by 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) ====

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

Add lenny repositories to your '''/etc/apt/sources.list'''
<pre>
deb http://DEBIAN-MIRROR/debian/ testing main
deb http://DEBIAN-MIRROR/debian-security/ testing/updates main
</pre>

Enlarge apt-cache adding to '''/etc/apt/apt.conf''' this line:
<pre>
APT::Cache-Limit "100000000";
</pre>

Give etch package priority over lenny packages. Edit '''/etc/apt/preferences''' and set like this:
<pre>
Package: *
Pin: release a=etch
Pin-Priority: 700

Package: *
Pin: release a=lenny
Pin-Priority: 650
</pre>

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

== Kernel installation ==

=== 1. Using openvz kernel repositories ===

{{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.

{| 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="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>

==== 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:

<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}}

==== 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>

=== 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>
iproute libatm1 linux-image-2.6.26-1-openvz-686 linux-image-openvz-686 rsync vzctl vzquota
</pre>
and will arrange grub bootloader propertly.

=== Rebooting into OpenVZ kernel ===

{{Warning|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.}}

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>
# uname -r
2.6.26-1-openvz-686
#
</pre>

2. Openvz kernel facility:
<pre>
# ps ax | grep vz
2349 ? S 0:00 [vzmond]
</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 ==

=== 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, automate changing sysctl options for openvz}}

<pre>
[...]

# 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

[...]
</pre>

# [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.}}

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

=== OS templates ===

To install a container, you need OS template(s).

Precreated templates can be found [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

== 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

== 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 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]]

Installation on Debian/old

2008-11-29T18:27:17Z

Ysidoro: /* Rebooting into OpenVZ kernel */ Confirm installation

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] stable.

== Requirements ==

=== Filesystems ===
It is recommended to use a separate partition for container private
directories (by default <code>/var/lib/vz/private/<CTID></code>). The reason why you should do so is that if you wish to use 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 usual Linux disk quota used in container, not on [[HN]].

At least try to avoid using root partition for containers because the root user of 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 so use one of these filesystems (ext3 is recommended) if you need per-container disk quota.

=== Repository setup ===

==== 1. Using openvz.org repositories ====

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

{{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}}

{{Note|By default, on Ubuntu systems root tasks are executed with [https://help.ubuntu.com/community/RootSudo sudo]}}

This can be achieved by 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) ====

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

Add lenny repositories to your '''/etc/apt/sources.list'''
<pre>
deb http://DEBIAN-MIRROR/debian/ testing main
deb http://DEBIAN-MIRROR/debian-security/ testing/updates main
</pre>

Enlarge apt-cache adding to '''/etc/apt/apt.conf''' this line:
<pre>
APT::Cache-Limit "100000000";
</pre>

Give etch package priority over lenny packages. Edit '''/etc/apt/preferences''' and set like this:
<pre>
Package: *
Pin: release a=etch
Pin-Priority: 700

Package: *
Pin: release a=lenny
Pin-Priority: 650
</pre>

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

== Kernel installation ==

=== 1. Using openvz kernel repositories ===

{{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.

{| 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="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>

==== 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:

<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}}

==== 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>

=== 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>
iproute libatm1 linux-image-2.6.26-1-openvz-686 linux-image-openvz-686 rsync vzctl vzquota
</pre>
and will arrange grub bootloader propertly.

=== Rebooting into OpenVZ kernel ===

{{Warning|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.}}

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>
# uname -r
2.6.26-1-openvz-686
#
</pre>

2. Openvz kernel facility:
<pre>
# ps ax | grep vz
2349 ? S 0:00 [vzmond]
</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 ==

=== 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, automate changing sysctl options for openvz}}

<pre>
[...]

# 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

[...]
</pre>

# [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.}}

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

=== OS templates ===

To install a container, you need OS template(s).

Precreated templates can be found [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

== 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

== 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 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]]

Installation on Debian/old

2008-11-29T18:24:35Z

Ysidoro: /* Configuring the bootloader */

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] stable.

== Requirements ==

=== Filesystems ===
It is recommended to use a separate partition for container private
directories (by default <code>/var/lib/vz/private/<CTID></code>). The reason why you should do so is that if you wish to use 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 usual Linux disk quota used in container, not on [[HN]].

At least try to avoid using root partition for containers because the root user of 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 so use one of these filesystems (ext3 is recommended) if you need per-container disk quota.

=== Repository setup ===

==== 1. Using openvz.org repositories ====

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

{{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}}

{{Note|By default, on Ubuntu systems root tasks are executed with [https://help.ubuntu.com/community/RootSudo sudo]}}

This can be achieved by 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) ====

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

Add lenny repositories to your '''/etc/apt/sources.list'''
<pre>
deb http://DEBIAN-MIRROR/debian/ testing main
deb http://DEBIAN-MIRROR/debian-security/ testing/updates main
</pre>

Enlarge apt-cache adding to '''/etc/apt/apt.conf''' this line:
<pre>
APT::Cache-Limit "100000000";
</pre>

Give etch package priority over lenny packages. Edit '''/etc/apt/preferences''' and set like this:
<pre>
Package: *
Pin: release a=etch
Pin-Priority: 700

Package: *
Pin: release a=lenny
Pin-Priority: 650
</pre>

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

== Kernel installation ==

=== 1. Using openvz kernel repositories ===

{{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.

{| 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="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>

==== 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:

<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}}

==== 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>

=== 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>
iproute libatm1 linux-image-2.6.26-1-openvz-686 linux-image-openvz-686 rsync vzctl vzquota
</pre>
and will arrange grub bootloader propertly.

=== Rebooting into OpenVZ kernel ===

{{Warning|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.}}

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.

== 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, automate changing sysctl options for openvz}}

<pre>
[...]

# 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

[...]
</pre>

# [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.}}

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

=== OS templates ===

To install a container, you need OS template(s).

Precreated templates can be found [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

== 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

== 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 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]]

Installation on Debian/old

2008-11-29T18:24:01Z

Ysidoro: /* Installing the user-level tools */

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] stable.

== Requirements ==

=== Filesystems ===
It is recommended to use a separate partition for container private
directories (by default <code>/var/lib/vz/private/<CTID></code>). The reason why you should do so is that if you wish to use 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 usual Linux disk quota used in container, not on [[HN]].

At least try to avoid using root partition for containers because the root user of 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 so use one of these filesystems (ext3 is recommended) if you need per-container disk quota.

=== Repository setup ===

==== 1. Using openvz.org repositories ====

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

{{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}}

{{Note|By default, on Ubuntu systems root tasks are executed with [https://help.ubuntu.com/community/RootSudo sudo]}}

This can be achieved by 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) ====

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

Add lenny repositories to your '''/etc/apt/sources.list'''
<pre>
deb http://DEBIAN-MIRROR/debian/ testing main
deb http://DEBIAN-MIRROR/debian-security/ testing/updates main
</pre>

Enlarge apt-cache adding to '''/etc/apt/apt.conf''' this line:
<pre>
APT::Cache-Limit "100000000";
</pre>

Give etch package priority over lenny packages. Edit '''/etc/apt/preferences''' and set like this:
<pre>
Package: *
Pin: release a=etch
Pin-Priority: 700

Package: *
Pin: release a=lenny
Pin-Priority: 650
</pre>

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

== Kernel installation ==

=== 1. Using openvz kernel repositories ===

{{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.

{| 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="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>

==== 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:

<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}}

=== 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>
iproute libatm1 linux-image-2.6.26-1-openvz-686 linux-image-openvz-686 rsync vzctl vzquota
</pre>
and will arrange grub bootloader propertly.

=== Rebooting into OpenVZ kernel ===

{{Warning|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.}}

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.

== 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, automate changing sysctl options for openvz}}

<pre>
[...]

# 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

[...]
</pre>

# [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.}}

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

=== OS templates ===

To install a container, you need OS template(s).

Precreated templates can be found [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

== 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

== 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 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]]

Installation on Debian/old

2008-11-29T18:22:59Z

Ysidoro: /* Kernel installation */ with lenny repositories

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] stable.

== Requirements ==

=== Filesystems ===
It is recommended to use a separate partition for container private
directories (by default <code>/var/lib/vz/private/<CTID></code>). The reason why you should do so is that if you wish to use 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 usual Linux disk quota used in container, not on [[HN]].

At least try to avoid using root partition for containers because the root user of 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 so use one of these filesystems (ext3 is recommended) if you need per-container disk quota.

=== Repository setup ===

==== 1. Using openvz.org repositories ====

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

{{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}}

{{Note|By default, on Ubuntu systems root tasks are executed with [https://help.ubuntu.com/community/RootSudo sudo]}}

This can be achieved by 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) ====

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

Add lenny repositories to your '''/etc/apt/sources.list'''
<pre>
deb http://DEBIAN-MIRROR/debian/ testing main
deb http://DEBIAN-MIRROR/debian-security/ testing/updates main
</pre>

Enlarge apt-cache adding to '''/etc/apt/apt.conf''' this line:
<pre>
APT::Cache-Limit "100000000";
</pre>

Give etch package priority over lenny packages. Edit '''/etc/apt/preferences''' and set like this:
<pre>
Package: *
Pin: release a=etch
Pin-Priority: 700

Package: *
Pin: release a=lenny
Pin-Priority: 650
</pre>

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

== Kernel installation ==

=== 1. Using openvz kernel repositories ===

{{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.

{| 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="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>

==== 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:

<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}}

=== 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>
iproute libatm1 linux-image-2.6.26-1-openvz-686 linux-image-openvz-686 rsync vzctl vzquota
</pre>
and will arrange grub bootloader propertly.

=== Rebooting into OpenVZ kernel ===

{{Warning|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.}}

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.

== 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>

== 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, automate changing sysctl options for openvz}}

<pre>
[...]

# 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

[...]
</pre>

# [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.}}

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

=== OS templates ===

To install a container, you need OS template(s).

Precreated templates can be found [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

== 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

== 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 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]]

Installation on Debian/old

2008-11-29T18:13:32Z

Ysidoro: /* Repository setup */ lenny repository to installation

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] stable.

== Requirements ==

=== Filesystems ===
It is recommended to use a separate partition for container private
directories (by default <code>/var/lib/vz/private/<CTID></code>). The reason why you should do so is that if you wish to use 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 usual Linux disk quota used in container, not on [[HN]].

At least try to avoid using root partition for containers because the root user of 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 so use one of these filesystems (ext3 is recommended) if you need per-container disk quota.

=== Repository setup ===

==== 1. Using openvz.org repositories ====

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

{{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}}

{{Note|By default, on Ubuntu systems root tasks are executed with [https://help.ubuntu.com/community/RootSudo sudo]}}

This can be achieved by 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) ====

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

Add lenny repositories to your '''/etc/apt/sources.list'''
<pre>
deb http://DEBIAN-MIRROR/debian/ testing main
deb http://DEBIAN-MIRROR/debian-security/ testing/updates main
</pre>

Enlarge apt-cache adding to '''/etc/apt/apt.conf''' this line:
<pre>
APT::Cache-Limit "100000000";
</pre>

Give etch package priority over lenny packages. Edit '''/etc/apt/preferences''' and set like this:
<pre>
Package: *
Pin: release a=etch
Pin-Priority: 700

Package: *
Pin: release a=lenny
Pin-Priority: 650
</pre>

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

== Kernel installation ==

{{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.

{| 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="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>

=== 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:

<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}}

=== Rebooting into OpenVZ kernel ===

{{Warning|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.}}

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.

== 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>

== 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, automate changing sysctl options for openvz}}

<pre>
[...]

# 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

[...]
</pre>

# [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.}}

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

=== OS templates ===

To install a container, you need OS template(s).

Precreated templates can be found [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

== 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

== 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 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]]