OpenVZ Virtuozzo Containers Wiki - User contributions [en]

Download/kernel/rhel5/028stab066.7/changes

2009-11-30T20:19:35Z

Curx: /* Changes */ fix typo softirq(s)

== Changes ==
Since {{kernel link|rhel5|028stab064.8}}:
* Rebase to 2.6.18-164.2.1.el5 kernel, number of CVEs fixed (see below), ext4, driver updates, etc.
* vzquota: ext4 support
* Bug fixes for the following issues:
** a Hardware Node may hang while printing the calltraces for all processes (caused by Alt+SysRQ+p magic key interrupt) due to incorrect NMI handling
** the default size of "tmpfs" filesystem was set to half amount of Hardware Node's memory
** two different UDP sockets may be bound to the same port inside a Container which in particular results in "aim7" test suite fail
** a Container based on Ubuntu 8.04 template may fail to migrate (checkpoint) with the following message: "Error: d_path is invisible /dev" ({{bug|1198}})
** the control script for the Oracle CSS daemon ('init.cssd', a part of Oracle 11g Release 1 RAC software) may fail to work and fill logs with the following messages: "Oprocd detected system hang while in nonfatal mode. Respawning."
** a kernel crash may occur after Packet Generator tool kernel module (pktgen.ko) is loaded ({{bug|1325}})
** the sched_getcpu() function may return incorrect number if current CPU in case a process was migrated to another CPU via user request ({{bug|1149}})
* DRBD update up to v8.3.4
* Improvements:
** memory reclaiming algorithm has been modified, which resulted in significant NUMA nodes performance improvement
** "magic" Alt+SysRQ keys management has been enhanced: now disabling SysRQ keys (via <code>echo 0 > /proc/sys/sysrq</code>) also disables the ability to execute SysRQ key handlers via the /proc/sysrq-trigger file
** a kmemsize debugging mechanism has been added, which simplifies kmemsize leaks investigation
** veth driver statistic has been enhanced to report correct "tx_dropped" packets value
** UDP hash table size has been significantly increased to speed up UDP traffic handling, which is important for example for Containers running Asterisk servers especially in the Full Proxy mode. Alternatively, UDP hash table size can be configured via <code>uhash_entries=</code>kernel boot parameter
** softirq statistics can be now monitored via the /proc/softirqs file
** root on a Hardware Node may now run some new processes even if the overall number of processes/threads on the Node exceeds the value of <code>kernel.threads-max</code> sysctl. In particular, this feature allows root to login to an overloaded Hardware Node

=== Compatibility ===
* No new issues

=== Configs ===
* No OpenVZ-specific changes

== See also ==
* {{RHSA|2009-1193}}
* {{RHSA|2009-1222}}
* {{RHSA|2009-1243}}
* {{RHSA|2009-1455}}
* {{CVE|2007-5966}}
* {{CVE|2009-1385}}
* {{CVE|2009-1389}}
* {{CVE|2009-1895}}
* {{CVE|2009-2406}}
* {{CVE|2009-2407}}
* {{CVE|2009-2848}}
* {{CVE|2009-2847}}
* {{CVE|2009-0745}}
* {{CVE|2009-0746}}
* {{CVE|2009-0747}}
* {{CVE|2009-0748}}
* {{CVE|2009-2849}}

Performance tuning

2009-08-24T15:32:07Z

Curx: a typo repaired

This page describes how to improve the performance of an OpenVZ system.

== HW node environment tuning ==

=== Disable unnecessary services ===

Disable all default services that you do not need to use and then reboot your host.

For example, the <code>audit</code> daemon can significantly decrease performance of linux kernel system calls (up to ~20%) even if you do not use any audit rules, or even if you just stopped this service without host reboot!

To setup default services, use <code>chkconfig</code> or <code>ntsysv</code> in RedHat, or <code>rc-update</code> in Gentoo, <code>update-rc.d</code> on Debian

=== Shell scripts performance improvement ===

To improve performance of small shell scripts, which spends a lot of time starting the shell binary itself (like the shell scripts test from the [http://www.tux.org/pub/tux/niemi/unixbench/ unixbench] package), you can set your <code>LANG</code> environment variable to <code>"C"</code>.

To see current settings, type

# locale

If you want to change it only for the current shell session, do:

# export LANG=C

If you want to change the default value, modify the <code>/etc/sysconfig/i18n</code> file.

If your default <code>LANG</code> environment variable was set to something like <code>en_US.UTF-8</code>, you can reduce shell (bash) startup time up to ~15% with <code>LANG=C</code>.

== Container tuning ==

=== CPU distribution inside container on SMP hosts ===

If the total number of containers in your host is more than CPUs number, and there are many '''threads''' running inside each container it is better to give just a single VCPU to each container.
In this case thread memory locality will significantly reduce overhead on SMP memory coherence and overall performance can be increased up to ~50-100%!

To set the number of CPUs available inside a container, use:

# vzctl set $CTID --cpus N

=== Network checksumming ===

RHEL 5 based kernel supports IP checksum offload.
If network ethernet cards in your host support IP checksum offload then you can switch this feature on also for the virtual network devices (venet, veth).

To check current offload setting for the hardware ethernet card (eth0, for instance) type

# ethtool -k eth0

Make sure that tx/rx features are switched on.

To see current offload settings for the venet0 device, type

# ethtool -k venet0

To set offload settings on for the venet0 device, type

# ethtool -K venet0 tx on sg on

Note, that 'tx on/off' enables/disables both tx and rx checksumming features for the all venet devices for all containers and HN.

The same applies to the veth device except that 'tx on/off' enables/disables tx and rx checksumming features for only given virtual ethernet device in HN and corresponding container.

=== Shell scripts performance improvement ===

Please note, that on container creation the default <code>LANG</code> value will be the same as in the HW node. So you can tune it in node (see [[#Shell scripts performance improvement]] above), or set it in container the same way.

The second important thing is the locale cache. On <code>rpm</code> based distributions, usually it is created by the <code>glibc-common-XXX.rpm</code> post install script and it can be up to 50 MBytes on some distributions. So on some container templates it can be missed to save disk space. But you can always create it inside container later by the following command (you must be the root user):

# build-locale-archive

And again, in some cases shell (bash) startup time can be reduced up to ~15%.

[[Category: HOWTO]]
[[Category: Troubleshooting]]

Traffic accounting through proc

2009-02-03T23:34:19Z

Curx: update to use the cron system of openvz

Traffic Accounting through /proc/net/dev

== Introduction ==
Traffic accounting in OpenVZ can be done through data collection against
<code>/proc/net/dev</code> in the individual containers on a [[HN]].

== Prerequisites ==
* OpenVZ
* RRDTool
* GNU AWK

== Script ==
First create a directory to store your RRD files:

# mkdir /var/lib/rrd/

Then install this script:

<source lang="bash">
#!/bin/sh
# Script Name: vz_direct_traffic_log
# Author: "Brian Harrington, Alticon Inc" <bharrington@alticon.net>
# Website: htty://www.alticon.net

# Time to do the data collection.
for veid in `/usr/sbin/vzlist -o veid -H | sed 's/ //g'`; do

RRDFILE="/var/lib/rrd/$veid.rrd"

if ! test -e $RRDFILE; then
echo $RRDFILE does not exist, creating.
# Place your preferred RRD Creation command here
fi

# Parse out the inbound/outbound traffic and assign them to the corresponding variables
eval `/usr/sbin/vzctl exec $veid "grep venet0 /proc/net/dev" | \
awk -F: '{print $2}' | awk '{printf"CTIN=%-15d\nCTOUT=%-15d\n", $1, $9}'`

# Send the data to the corresponding RRD time with (N)now as the update time
/usr/bin/rrdtool update $RRDFILE N:$CTIN:$CTOUT
done
</source>

== Setup ==
Add this to cron to run every 5 minutes:

# echo "*/5 * * * * root /path/to/script/vz_direct_traffic_log " >> \
/etc/crontab && /etc/init.d/crontab restart

Better use the cron system of OpenVZ

# echo "*/5 * * * * root /path/to/script/vz_direct_traffic_log " >> \
/etc/vz/cron/vz-traffic.sh && /etc/init.d/vz update-cron

To check the output of this later run:

# rrdtool fetch /var/lib/rrd/<veid>.rrd AVERAGE -s -3600

== See also ==

* [[Traffic accounting with iptables]]
* [[Monitoring bandwidth of containers]]

[[Category: Monitoring]]
[[Category: Networking]]

Traffic accounting through proc

2009-02-03T23:27:52Z

Curx: /* See also */

Traffic Accounting through /proc/net/dev

== Introduction ==
Traffic accounting in OpenVZ can be done through data collection against
<code>/proc/net/dev</code> in the individual containers on a [[HN]].

== Prerequisites ==
* OpenVZ
* RRDTool
* GNU AWK

== Script ==
First create a directory to store your RRD files:

# mkdir /var/lib/rrd/

Then install this script:

<source lang="bash">
#!/bin/sh
# Script Name: vz_direct_traffic_log
# Author: "Brian Harrington, Alticon Inc" <bharrington@alticon.net>
# Website: htty://www.alticon.net

# Time to do the data collection.
for veid in `/usr/sbin/vzlist -o veid -H | sed 's/ //g'`; do

RRDFILE="/var/lib/rrd/$veid.rrd"

if ! test -e $RRDFILE; then
echo $RRDFILE does not exist, creating.
# Place your preferred RRD Creation command here
fi

# Parse out the inbound/outbound traffic and assign them to the corresponding variables
eval `/usr/sbin/vzctl exec $veid "grep venet0 /proc/net/dev" | \
awk -F: '{print $2}' | awk '{printf"CTIN=%-15d\nCTOUT=%-15d\n", $1, $9}'`

# Send the data to the corresponding RRD time with (N)now as the update time
/usr/bin/rrdtool update $RRDFILE N:$CTIN:$CTOUT
done
</source>

== Setup ==
Add this to cron to run every 5 minutes:

# echo "*/5 * * * * root /path/to/script/vz_direct_traffic_log " >> \
/etc/crontab && /etc/init.d/crontab restart

To check the output of this later run:

# rrdtool fetch /var/lib/rrd/<veid>.rrd AVERAGE -s -3600

== See also ==

* [[Traffic accounting with iptables]]
* [[Monitoring bandwidth of containers]]

[[Category: Monitoring]]
[[Category: Networking]]

Monitoring bandwidth of containers

2008-12-31T01:09:11Z

Curx: Monitoring bandwith of containers moved to Monitoring bandwidth of containers: typo in Title

{{DISPLAYTITLE:Monitoring bandwith of containers}}

Use the /proc/dev/net inside a container, dump stats into a round robin database (rrd)

<pre>
#!/bin/bash
#
# Bandwidth collection script for OpenVZ by Eric 'phpfreak' Rosebrock
# http://www.serverpowered.com / http://www.thewebfreaks.com
# Please read: http://www.serverpowered.com/openvz-bandwidth-accounting.php
#
#
# No warranties on this script, use it at your own risk!
#
# Special thanks to Rick Blundell for helping me to get this thing going.
#
# Discussions: http://forum.openvz.org/index.php?t=tree&goto=1350

# BWVE is the bandwidth storage VE. This would have been created by the
# tutorial you followed as listed above.

BWVE=1002

# BWDIR is the directory inside the bandwdith VE where the .rrd files
# will be stored.

BWDIR=var/rrd/vz

# You should not need to edit anything below this line.

# Get the date from the first of this month to create new rrd files
TDATE=`date +%Y-%m-01`;
ETIME=`date +%s -d $TDATE`

# Define the full path to the bandwidth VE directory and the storage dir.
CBWDIR=/vz/private/$BWVE/$BWDIR

# Test and make sure that directory is there, if not create it.
if ! test -d $CBWDIR; then
echo $CBWDIR does not exist, creating it.
mkdir $CBWDIR

fi

# Get a list of all of the VE's created on the system, not just the running ones.

for i in `ls $CBWDIR`; do
VES=`echo $i | cut -f2 -d- | cut -f1 -d.`;

# if the VE was there before, an .rrd file will exist. Now if the VE is gone,
# Delete the .rrd file because its obviously not needed anymore.

if ! test -d /vz/private/$VES; then
echo $i will be deleted
rm -rf $CBWDIR/vps-$VES.rrd
fi
done

# Time to do the data collection.
for i in `/usr/sbin/vzlist -Ho veid`; do

RRDFILE=$CBWDIR/vps-$i.rrd

if ! test -e $RRDFILE; then
echo $RRDFILE does not exist, creating.
/usr/bin/rrdtool create $RRDFILE -s 300 \
DS:ds0:DERIVE:600:0:1125000000 \
DS:ds1:DERIVE:600:0:1125000000 \
RRA:AVERAGE:0.5:1:600 \
RRA:AVERAGE:0.5:6:700 \
RRA:AVERAGE:0.5:24:775 \
RRA:AVERAGE:0.5:288:797 \
RRA:MAX:0.5:1:600 \
RRA:MAX:0.5:6:700 \
RRA:MAX:0.5:24:775 \
RRA:MAX:0.5:288:797 \
RRA:MIN:0.5:1:600 \
RRA:MIN:0.5:6:700 \
RRA:MIN:0.5:24:775 \
RRA:MIN:0.5:288:797
fi

X=`/usr/sbin/vzctl exec $i "grep venet0 /proc/net/dev"`
eval `echo $X | cut -f2 -d: | awk '{printf"IN=%-11d\nOUT=%-11d\n", $1, $9}'`

for g in IN OUT;do
if [ -z ${!g} ]; then
echo foo
eval $g=0
fi
done
/usr/bin/rrdtool update $RRDFILE N:$IN:$OUT
done
</pre>

[[Category: HOWTO]]

[[Category: Monitoring]]

Monitoring bandwith of containers

2008-12-31T01:09:11Z

Curx: Monitoring bandwith of containers moved to Monitoring bandwidth of containers: typo in Title

#REDIRECT [[Monitoring bandwidth of containers]]

Monitoring bandwidth of containers

2008-12-31T01:05:02Z

Curx: add script

Debian versions

2008-09-15T05:29:19Z

Curx:

Debian people refer to versions of Debian distribution in a few ways: by nicknames, by numberic versions, and by statuses. The following table summarizes the relations between those referrals.

Note that ''status'' is changing over time, e.g. "Lenny" will become stable (and get a number) some time in future.

{| class="wikitable sortable"
! Name || Version || Status
|-
| Sid || n/a || unstable
|-
| Lenny || 5.0 || testing
|-
| Etch || 4.0 || stable
|-
| Sarge || 3.1 || old stable
|-
| Woody || 3.0 || n/a
|-
| Potato || 2.2 || n/a
|-
| Slink || 2.1 || n/a
|-
| Hamm || 2.0 || n/a
|}

== External links ==
* http://www.debian.org/releases/

[[Category: Debian]]

Ubuntu Hardy TODO

2008-05-26T04:26:45Z

Curx: remove precreated ubuntu templates from forzza.systs.org/ostemplates

This document is to track the status of OpenVZ integration into Ubuntu 8.04 «Hardy Heron».

== Kernel ==

2.6.24 kernel is ready for initial inclusion to Hardy. Below are some resources.

Ubuntu Hardy kernel git:
* http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=summary
* [http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=blob;f=debian/binary-custom.d/README How to add new kernel flavour]

OpenVZ 2.6.24 kernel git (switch to '''2.6.24-openvz''' branch):
* http://git.openvz.org/?p=linux-2.6.24-openvz;a=summary
* http://git.openvz.org/?p=linux-2.6.24-openvz;a=shortlog;h=2.6.24-openvz

'''Status''': adobriyan@ is working on porting our patch set to hardy kernel.

== Tools ==

=== vzctl ===

==== Done ====
* Already updated to 3.0.22, see
** https://bugs.launchpad.net/ubuntu/+source/vzctl/+bug/183774
** http://packages.ubuntu.com/vzctl

==== TODO ====

* Need to fix requirements: vzctl now suggests on linux-patch-openvz, instead it should require linux-image-openvz
* It probably makes sense to automate changing sysctl options on vzctl package installation (like vzctl from debian.systs.org does).

=== vzquota ===

==== DONE ====

* Updated to 3.0.11, see http://packages.ubuntu.com/vzquota

==== TODO ====

* As with vzctl, need to get rid of 'Suggects: kernel-patch-openvz' and require kernel-image-openvz instead.

=== vzpkg ===

Don't have plans to ship vzpkg in Ubuntu

== Documentation ==

* Ubuntu-specific documentation on wiki.openvz.org (see [[:Category:Ubuntu]])
* OpenVZ landing page for ubuntu.com

== Templates ==

The following templates are currently available (check http://openvz.org/download/template/cache/ for full list):
* Ubuntu 7.10 for x86 and x86_64.

We need to create somewhat minimal Hardy template and [probably?] pack it into a package.

As Ubuntu comes with debootstrap, making Ubuntu templates is pretty easy. See [[Ubuntu Gutsy template creation]].

[[Category: Ubuntu]]

Installation on Debian/old

2008-05-19T20:39:34Z

Curx: gitty repository removed, lenny added

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

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 used the Repository at http://download.openvz.org/debian-systs, the actually OpenVZ Tools for Debian are exist only in unstable, see http://packages.debian.org/vzctl}}

{{Note|per default on Ubuntu system, root task are done 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>

There is even an '''lenny''' repository with kernel 2.6.24. '''Use it at your own risk!'''
<pre>
# echo -e "\ndeb http://download.openvz.org/debian-systs lenny 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>

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

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

Ubuntu Hardy TODO

2008-03-01T08:53:13Z

Curx: add url for precreated os templates of ubunutu hardy

This document is to track the status of OpenVZ integration into Ubuntu 8.04 «Hardy Heron».

== Kernel ==

2.6.24 kernel is ready for initial inclusion to Hardy. Below are some resources.

Ubuntu Hardy kernel git:
* http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=summary
* [http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=blob;f=debian/binary-custom.d/README How to add new kernel flavour]

OpenVZ 2.6.24 kernel git (switch to '''2.6.24-openvz''' branch):
* http://git.openvz.org/?p=linux-2.6.24-openvz;a=summary
* http://git.openvz.org/?p=linux-2.6.24-openvz;a=shortlog;h=2.6.24-openvz

'''Status''': adobriyan@ is working on porting our patch set to hardy kernel.

== Tools ==

=== vzctl ===

==== Done ====
* Already updated to 3.0.22, see
** https://bugs.launchpad.net/ubuntu/+source/vzctl/+bug/183774
** http://packages.ubuntu.com/vzctl

==== TODO ====

* Need to fix requirements: vzctl now suggests on linux-patch-openvz, instead it should require linux-image-openvz
* It probably makes sense to automate changing sysctl options on vzctl package installation (like vzctl from debian.systs.org does).

=== vzquota ===

==== DONE ====

* Updated to 3.0.11, see http://packages.ubuntu.com/vzquota

==== TODO ====

* As with vzctl, need to get rid of 'Suggects: kernel-patch-openvz' and require kernel-image-openvz instead.

=== vzpkg ===

Don't have plans to ship vzpkg in Ubuntu

== Documentation ==

* Ubuntu-specific documentation on wiki.openvz.org (see [[:Category:Ubuntu]])
* OpenVZ landing page for ubuntu.com

== Templates ==

The following templates are currently available (check http://openvz.org/download/template/cache/ for full list):
* Ubuntu 7.10 for x86 and x86_64.

We need to create somewhat minimal Hardy template and [probably?] pack it into a package.

* Ubuntu 8.0.4 precreted templates http://forzza.systs.org/ostemplates/

As Ubuntu comes with debootstrap, making Ubuntu templates is pretty easy. See [[Ubuntu Gutsy template creation]].

[[Category: Ubuntu]]

User:Curx

2008-01-05T12:58:20Z

Curx: copytoinstalldeb

"curx" aka Thorsten Schifferdecker

Installation on Debian/old

2008-01-05T12:57:17Z

Curx: typo removed

OpenVZ consists of a kernel, user-level tools, and VE 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 VEs private directories (by default /var/lib/vz/private/<veid>). The reason why you should do so is that if you wish to use OpenVZ per-VE disk quota, you won't be able to use usual Linux disk quotas on the same partition. Bear in mind, that per-VE quota in this context includes not only pure per-VE quota, but also usual Linux disk quota used in VE, not on [[HN]].

At least try to avoid using root partition for VEs, because the root user of VE will be able to overcome 5% disk space barrier in some situations. This way HN root partition can be completely filled and it will break the system.

OpenVZ per-VE disk quota is supported only for ext2/ext3 filesystems. So use one of these filesystems (ext3 is recommended) if you need per-VE disk quota.

=== Repository setup ===

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

Ola Lundqvist <opal@debian.org> "OpenVZ Kernels only" --> apt-uri [http://download.openvz.org/debian http://download.openvz.org/debian]

Thorsten Schifferdecker <tsd@debian.systs.org> --> apt-uri [http://download.openvz.org/debian-systs http://download.openvz.org/debian-systs] (Mirror of OpenVZ Repository from http://debian.systs.org)

{{Note|The next steps used the Repository at http://download.openvz.org/debian-systs, the actually OpenVZ Tools for Debian are exist only in unstable see http://packages.debian.org/vzctl }}

{{Note|per default on ubuntu system, root task are done with [https://help.ubuntu.com/community/RootSudo sudo]}}

This can be achieved by the following commands, as root or as privileged "sudo" user

<pre>
# [sudo] echo "deb http://download.openvz.org/debian-systs etch openvz" >> /etc/apt/sources.list
# wget http://download.openvz.org/debian-systs/dso_archiv_signing_key.asc
# [sudo] apt-key add dso_archiv_signing_key.asc
# [sudo] apt-get update
</pre>

== 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 Architektur
|-
! 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 Architektur
|-
! 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 VPSs (create, destroy, start, stop, set parameters etc.)
; vzquota
: A utility to manage quotas for VPSs. 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

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

{{Note|You can 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}}

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

=== VE OS Templates ===

To install a VE, you need VE OS Template(s), precreated can be found [http://download.openvz.org/contrib/template/precreated/ here] or create it : [http://wiki.openvz.org/Debian_template_creation Debian] , [http://wiki.openvz.org/Ubuntu_Gutsy_template_creation ubuntu] and all infos about [http://wiki.openvz.org/Category:Templates Templates]

{{Note|Setup your prefered standard OS Template : edit the /etc/vz/vz.conf}}

# [sudo] apt-get install vzctl-ostmpl-debian

== Additial user tools ==

; vzprocps
: A set of utilities to provide system information (vzps and vztop)
:
; [http://wiki.openvz.org/Backup_of_a_running_VE_with_vzdump vzdump]
: A utility to backup and restore VE.

# [sudo] apt-get install vzprocps vzdump

== Use it! ==

After installing the OpenVZ kernel, user tools and a Minimal VE OS Template create a first VE and
do some [[Basic operations in OpenVZ environment]] and read the [[download:doc/OpenVZ-Users-Guide.pdf|doc/OpenVZ-Users-Guide.pdf]] and browse this wiki.

[[Category: HOWTO]]
[[Category: Installation]]

Installation on Debian/old

2008-01-05T12:47:00Z

Curx: update to actually state

OpenVZ consists of a kernel, user-level tools, and VE 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 VEs private directories (by default /var/lib/vz/private/<veid>). The reason why you should do so is that if you wish to use OpenVZ per-VE disk quota, you won't be able to use usual Linux disk quotas on the same partition. Bear in mind, that per-VE quota in this context includes not only pure per-VE quota, but also usual Linux disk quota used in VE, not on [[HN]].

At least try to avoid using root partition for VEs, because the root user of VE will be able to overcome 5% disk space barrier in some situations. This way HN root partition can be completely filled and it will break the system.

OpenVZ per-VE disk quota is supported only for ext2/ext3 filesystems. So use one of these filesystems (ext3 is recommended) if you need per-VE disk quota.

=== Repository setup ===

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

Ola Lundqvist <opal@debian.org> "OpenVZ Kernels only" --> apt-uri [http://download.openvz.org/debian http://download.openvz.org/debian]

Thorsten Schiffedecker <tsd@debian.systs.org> --> apt-uri [http://download.openvz.org/debian-systs http://download.openvz.org/debian-systs] (Mirror of OpenVZ Repository from http://debian.systs.org)

{{Note|The next steps used the Repository at http://download.openvz.org/debian-systs, the actually OpenVZ Tools for Debian are exist only in unstable see http://packages.debian.org/vzctl }}

{{Note|per default on ubuntu system, root task are done with [https://help.ubuntu.com/community/RootSudo sudo]}}

This can be achieved by the following commands, as root or as privileged "sudo" user

<pre>
# [sudo] echo "deb http://download.openvz.org/debian-systs etch openvz" >> /etc/apt/sources.list
# wget http://download.openvz.org/debian-systs/dso_archiv_signing_key.asc
# [sudo] apt-key add dso_archiv_signing_key.asc
# [sudo] apt-get update
</pre>

== 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 openvz.org'''
! kernel !! Description !! Hardware !! Debian Architektur
|-
! 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 Architektur
|-
! 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: 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 VPSs (create, destroy, start, stop, set parameters etc.)
; vzquota
: A utility to manage quotas for VPSs. 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

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

{{Note|You can 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}}

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

=== VE OS Templates ===

To install a VE, you need VE OS Template(s), precreated can be found [http://download.openvz.org/contrib/template/precreated/ here] or create it : [http://wiki.openvz.org/Debian_template_creation Debian] , [http://wiki.openvz.org/Ubuntu_Gutsy_template_creation ubuntu] and all infos about [http://wiki.openvz.org/Category:Templates Templates]

{{Note|Setup your prefered standard OS Template : edit the /etc/vz/vz.conf}}

# [sudo] apt-get install vzctl-ostmpl-debian

== Additial user tools ==

; vzprocps
: A set of utilities to provide system information (vzps and vztop)
:
; [http://wiki.openvz.org/Backup_of_a_running_VE_with_vzdump vzdump]
: A utility to backup and restore VE.

# [sudo] apt-get install vzprocps vzdump

== Use it! ==

After installing the OpenVZ kernel, user tools and a Minimal VE OS Template create a first VE and
do some [[Basic operations in OpenVZ environment]] and read the [[download:doc/OpenVZ-Users-Guide.pdf|doc/OpenVZ-Users-Guide.pdf]] and browse this wiki.

[[Category: HOWTO]]
[[Category: Installation]]

Download/live CD

2008-01-02T19:13:35Z

Curx: fix links to livecd

Here you can find OpenVZ Live CD images. Live CD is a great way to test drive the OpenVZ technology without a need to actually install it on your machine.

We offer two live CDs at the moment. The first one is based on Knoppix 5.1.1 and the second one is based on Centos 4.4.

== Download ==

The precreated ISO images are available directly from [http://download.openvz.org/livecd/ download.openvz.org/livecd/] or any of the [[download mirrors]].

=== CentOS ===
{{KernelDownloadTableHead}}
{{DownloadTableRow|path=livecd|file=CentOS-4.4-OpenVZ-i386-LiveCD.iso|size=684 MB}}
{{DownloadTableRow|path=livecd|file=CentOS-4.4-OpenVZ-i386-LiveCD.iso.md5|size=68 B}}
{{DownloadTableRow|path=livecd|file=CentOS-4.4-OpenVZ-i386-LiveCD.iso.asc|size=}}
{{KernelDownloadTableTail}}

=== Knoppix ===
{{KernelDownloadTableHead}}
{{DownloadTableRow|path=livecd|file=KNOPPIX_V5.1.1-OPENVZ-CD-2007-01-04-EN.iso|size=683 MB}}
{{DownloadTableRow|path=livecd|file=KNOPPIX_V5.1.1-OPENVZ-CD-2007-01-04-EN.iso.md5|size=77 B}}
{{DownloadTableRow|path=livecd|file=KNOPPIX_V5.1.1-OPENVZ-CD-2007-01-04-EN.iso.asc|size=189 B}}
{{KernelDownloadTableTail}}

Note that .md5 and .asc files does not need to be copied to the CD-R; they are here to check the authenticity of the iso file. [[Package_signatures#Checking_files|This page]] has some info on this topic.

== Burning ==

After downloading the image, you have to burn it to the actual media, i.e. a CD-R or CD-RW disk. The process depends on the actual OS and CD burning software that you have, and the exact details are out of scope of this article.

If you don't know how to burn the ISO image to CD-R, try [http://www.knoppix.net/wiki/Downloading_FAQ#Q:_I_have_downloaded_the_ISO_file._How_do_I_burn_the_ISO.3F_How_is_the_ISO_supposed_to_be_burned.3F this document].

== Booting ==
Just insert the fresh CD into your CD-ROM and reboot. In some cases you have to modify your BIOS settings in order to enable booting from a CD.
If you use CentOS-based CD you'll be able to choose the kernel to boot: <tt>ovz9rh</tt>, <tt>ovz18</tt>, <tt>ovz18rh</tt>, <tt>ovz20</tt> or <tt>linux</tt> (original CentOS kernel).

== Using ==
Upon the successful boot, a browser window with some helful hints will appear to help you start using OpenVZ. The latest version of that document is also available on this wiki: [[Getting started with OpenVZ live CD]].

== Limitations ==
Since this is a live CD, everything is created in RAM, i.e. is not persistent. If you will create a number of VEs, they will not be available after the reboot.

A number of [[VE]]s that you can create using this live CD greatly depends on the amount of RAM your machine has, since the system uses RAM instead of a hard disk. On a 1 gigabyte RAM machine you can create about 5 VEs. To work around this, you have to have a disk partition mounted to <tt>/vz/private/</tt> for CentOS-based CD and to <tt>/var/lib/vz/private</tt> for KNOPPIX-based CD.

OpenVZ disk quota does not work on LiveCD at the moment due to {{Bug|558}}, so <code>df</code> in [[VE]] shows ludicrous values if quota is on.
Because of it on CentOS 4.4 LiveCD disk quota is switched off by default.

Checkpointing (and consequently live migration) doesn't work on KNOPPIX LiveCD at the moment due to {{Bug|606}}.
You can work around it by mounting some filesystem (<tt>ext2</tt>, <tt>ext3</tt>, <tt>tmpfs</tt>) to <tt>/var/lib/vz/private</tt> directory.
On CentOS-based LiveCD <tt>tmpfs</tt> is mounted on this directory automatically during the booting.

== CD contents ==

=== CentOS CD contents ===
This CD is based on CentOS 4.4 Live CD and contains the following OpenVZ packages:
* '''kernels''':
** original CentOS 4.4 kernel without virtualization (2.6.9-42.livecd.c4)
** 2.6.9-023stab044.4
** 2.6.18-028stab035
** 2.6.18-028stab035-rhel5
** 2.6.20-ovz007.1
* '''tools''':
** vzctl 3.0.18
** vzquota 3.0.9
* '''template tools''':
** vzyum-2.4.0-11
** vzrpm44-4.4.1-22.5
** vzrpm43-4.3.3-7
** vzpkg-2.7.0-18
* '''template metadatas''':
** vztmpl-centos-4-2.0-2
** vztmpl-fedora-core-3-2.0-2
** vztmpl-fedora-core-4-2.0-2
** vztmpl-fedora-core-5-2.0-2
* '''precreated templates''':
** centos-4-i386-minimal
** fedora-core-5-i386-minimal
** debian-3.1-i386-minimal

The number of original CentOS packages were removed (<tt>openoffice</tt>, <tt>gimp</tt>, etc.) in order
to free disk space for OpenVZ packages and templates.

=== Knoppix CD contents ===
This CD contains the following OpenVZ packages:
* kernel 2.6.18-028stab027
* vzctl 3.0.16
* vzquota 3.0.9
plus the number of precreated templates:
* Debian 3.1 minimal
* CentOS 4 minimal
* Fedora Core 5 minimal

It also contains all the software from the original Knoppix 5.1.1 CD, excluding:
* OpenOffice
* GIMP
* Frozen Bubble
The above packages were taken out to make some room for OpenVZ packages.

== Changelog ==
* 7 May 2007, initial version based on Knoppix 5.1.1
* 5 July 2007, version based on Centos 4.4

== External links ==
* [http://knoppix.com/ knoppix.com], the home of Knoppix distribution
* [http://centos.org/ centos.org], the home of CentOS distribution

[[Category: Download]]
[[Category: Live CD]]

Ubuntu Gutsy template creation

2007-12-22T10:11:26Z

Curx: add note removing module-init-tools

[[Category: HOWTO]]
[[Category: Templates]]
[[Category: Ubuntu]]

This article summarizes the experience of creating Ubunty Gutsy Gibbon (a.k.a. 7.10) template for OpenVZ.

Template creation is based on debootstrap, and the procedure is similar to [[Debian template creation]], but it differs in some subtle details.

== Prerequisites ==

=== debootstrap ===
You have to have a debootstrap working for Gutsy, i.e. you should have
* debootstrap and its dependencies
* /usr/lib/debootstrap/scripts/gutsy file

The simplest way to have it all is to work on an Ubunty Gutsy system (be it on a real machine or inside a VE). If you don't have debootstrap installed, this is the command to install it:

# apt-get install debootstrap

On a Gentoo Linux, debootstrap is also available, this is how you can install it:

# emerge debootstrap

=== vzctl ===

You need vzctl-3.0.19 or later to work with Ubuntu Gutsy Gibbon. If vzctl-3.0.18 or earlier is used, you will not be able to run your VE. See {{bug|662}} for details.

Note: Older versions of vzctl have worked for me IF you install sysvinit (which will remove upstart). The only problem I had was the network did not start, so I added "/etc/init.d/networking restart" to /etc/re.local.

== Creating template ==

=== Running debootstrap ===

Create a working directory:

[HW]# mkdir gutsy-chroot

Run debootstrap to install a minimal Ubunty Gutsy system into that directory:

[HW]# debootstrap [--arch ''ARCH''] gutsy gutsy-chroot

If ARCH of VE0 is equal to VE, you can skip the --arch option, but if you need to build an OS template for another ''ARCH'', specify it explicitly:
* for AMD64/x86_64, use <code>amd64</code>
* for IA64, use <code>ia64</code>
* for i386 <code>i386</code>

=== Preparing/starting a VE ===

Now then you have an installation created by <code>debootstrap</code>, you can run it as a VE. In the example below VE ID of 777 is used; of course you can use any other non-allocated ID.

{{Note|an alternative way is using chroot instead of running a VE. This is not recommended because of security concerns.}}

==== Moving installation to VE private area ====

You should move the contents of gutsy-chroot directory into new VE private area, like this:

# mv gutsy-chroot /vz/private/777

==== Setting VE config ====
An initial config for the [[VE]] is needed:
# vzctl set 777 --applyconfig vps.basic --save

==== Setting VE OSTEMPLATE ====
Also, we need <code>OSTEMPLATE</code> to be set in VE configuration file, for the [[vzctl]] to work properly.

# echo "OSTEMPLATE=ubuntu-7.10" >> /etc/vz/conf/777.conf

==== Setting VE IP address ====
For the [[VE]] to be able to download updates from the Internet, we need a valid IP address for it:
# vzctl set 777 --ipadd x.x.x.x --save

{{Note|if you use private IP for the VE, you have to set up NAT as described in [[Using NAT for VE with private IPs]].}}

==== Setting DNS server for the VE ====
For the [[VE]] to be able to download updates from the Internet, we also need to specify a DNS for it:
# vzctl set 777 --nameserver x.x.x.x --save

Instead of <code>x.x.x.x</code>, specify the same IP that you have in your <code>/etc/resolv.conf</code>.

==== Starting VE ====
Now start the VE:
# vzctl start 777

=== Modify the installation ===

You have to do some things in order to modify the installation to better suit the environment it will be run in (i.e. a VE).

First, enter a VE:
# vzctl enter 777

{{Warning|Do not run the commands below on the hardware node, they are only to be run within the VE!}}

==== Remove unneeded packages ====

Some packages does not make sense in a VE, or are really optional. Remove those:

[VE]# dpkg -P ubuntu-minimal wpasupplicant wireless-tools \
udev pcmciautils initramfs-tools volumeid console-setup \
xkb-data usbutils mii-diag alsa-base alsa-utils ethtool \
module-init-tools linux-sound-base console-tools \
console-terminus busybox-initramfs libvolume-id0 \
ntpdate eject libasound2 pciutils tasksel tasksel-data \
laptop-detect

{{Note|On removing the deb-package "module-init-tools", a fake-modprobe is needed for IPv6 adresses, see below!}}

Note that the above list of packages may be too extensive. Say, if you want to use <code>tasksel</code> tool, do not remove it — but then you have to let laptop-detect stay.

Clean up after udev:

[VE]# rm -fr /lib/udev

==== Disable getty ====
On a usual Linux system, getty is running on a virtual terminals, which a VE does not have. So, having getty running doesn't make sense; more to say, it complains it can not open terminal device and this clutters the logs.

So, first of all we stop all getty processes:

[VE]# initctl stop tty{1,2,3,4,5,6}

Next, we disable running getty. This can be done in two ways:

First way:
[VE]# rm /etc/event.d/tty*

Second way:
[VE]# dpkg -P system-services

Second way can be dangerous for future versions of system-services, but it's OK for now since the only service they carry is running gettys.

==== Set sane permissions for /root directory ====

[VE]# chmod 700 /root

==== Disable root login ====

[VE]# usermod -L root

==== "fake-modprobe" needed for IPv6 adresses ====

[VE]# ln -s /bin/true /sbin/modprobe

On setup IPv6, the command "modprobe -Q IPv6" is called, which fails without the "fake-modprobe"

==== Get new security updates ====

[VE]# apt-get update && apt-get upgrade

This didn't show anything for me, but might do something in the future.

==== Install some more packages ====

[VE]# apt-get install ssh quota

Feel free to add packages which you want to have in a default template to this command.

==== Fix SSH host keys ====
This is only useful if you installed SSH above. Each individual [[VE]] should have its own pair of SSH host keys. The code below will wipe out the existing SSH keys and instruct the newly-created [[VE]] to create new SSH keys on first boot.


<pre>
rm -f /etc/ssh/ssh_host_*
cat << EOF > /etc/rc2.d/S15ssh_gen_host_keys
#!/bin/sh
ssh-keygen -f /etc/ssh/ssh_host_rsa_key -t rsa -N ''
ssh-keygen -f /etc/ssh/ssh_host_dsa_key -t dsa -N ''
rm -f \$0
EOF
chmod a+x /etc/rc2.d/S15ssh_gen_host_keys
</pre>

==== Disable <code>sync()</code> for syslog ====

Turn off doing <tt>sync()</tt> on every write for <code>syslog</code>'s log files, to improve overall I/O performance.
In Ubuntu this is already done for most log files and levels, so you can omit this step if you know what you are doing.


<pre>[VE]# sed -i -e 's@$[[:space:]]$$/var/log/$@\1-\2@' /etc/syslog.conf</pre>

==== Fix <code>/etc/mtab</code> ====
Link <code>/etc/mtab</code> to <code>/proc/mounts</code>, so <code>df</code> and friends will work:
[VE]# rm -f /etc/mtab
[VE]# ln -s /proc/mounts /etc/mtab

After that, it would make sense to disable <code>mtab.sh</code> script which messes with <code>/etc/mtab</code>:
[VE]# update-rc.d -f mtab.sh remove

==== Disable some services ====

In most of the cases you don't want klogd to run -- the only exception is if you configure iptables to log some events -- so you can disable it:

[VE]# update-rc.d -f klogd remove

==== Hostname ====
Set proper hostname:
[VE]# echo "localhost" > /etc/hostname

==== Set /etc/hosts ====

[VE]# echo "127.0.0.1 localhost.localdomain localhost" > /etc/hosts

==== Add ptys to /dev ====

This is needed in case /dev/pts will not me mounted after VE start. In case /dev/ttyp* and /dev/ptyp* files are present, and LEGACY_PTYS support is enabled in the kernel, vzctl will still be able to enter VE.

[VE]# cd /dev && /sbin/MAKEDEV ptyp

==== Remove nameserver(s) ====

Remove DNS entries:
[VE]# > /etc/resolv.conf

==== Clean packages ====
After installing packages, you'll have some junk packages laying around in your cache. Since you don't want your template to have those, this command will wipe them out.
[VE]# apt-get clean

==== Cleaning up log files ====

[VE]# cd /var/log
[VE]# > messages; > auth.log; > kern.log; > bootstrap.log
[VE]# > dpkg.log; > syslog; > daemon.log; > apt/term.log
[VE]# rm -f *.0 *.1

==== Anything else? ====

Think of what else could be done to better suit your needs.

==== Exit from the VE ====

Now everything is done. Exit from the template and go back to the hardware node.

[VE]# exit

== Preparing for and packing template cache ==

The following commands are to be run in the host system (i.e. not inside a VE).

We don't need an IP for the VE anymore, and we definitely do not need it in template cache, so remove it:
[HW]# vzctl set 777 --ipdel all --save

Stop the VE:
[HW]# vzctl stop 777

Change dir to the VE private:
[HW]# cd /vz/private/777

Now create a cached OS tarball. In the command below, you'll want to replace <arch> with your architecture (i386, amd64, ia64, etc). '''Note the space and the dot at the end of the command'''.
[HW]# tar czf /vz/template/cache/ubuntu-7.10-<arch>-minimal.tar.gz .

Look at the resulting tarball to see its size is sane:
# ls -lh /vz/template/cache
-rw-r--r-- 1 root root 53M Nov 15 12:40 ubuntu-7.10-i386-minimal.tar.gz

== Testing template cache ==
We can now create a VE based on the just-created template cache. Be sure to change <tt>i386</tt> to your architecture just like you did when you named the tarball above.
[HW]# vzctl create 123456 --ostemplate ubuntu-7.10-<arch>-minimal

Now make sure that your new VE it works:
[HW]# vzctl start 123456
[HW]# vzctl exec 123456 ps axf

You should see that a few processes are running.

Other tests that could be done are:
[HW]# vzctl enter 123456
[VE]# ps axf
[VE]# mount
[VE]# dpkg -l
[VE]# logout
[HW]#

Feel free to do more tests.

== Final cleanup ==
Stop and remove the test VE you just created:
[HW]# vzctl stop 123456
[HW]# vzctl destroy 123456
[HW]# rm -f /etc/vz/conf/123456.conf.destroyed

Finally, let's remove the VE we used for OS template cache creation:
[HW]# vzctl destroy 777
[HW]# rm -f /etc/vz/conf/777.conf.destroyed

== Updating the template cache ==

See [[Updating Ubuntu template]]

Ubuntu Gutsy template creation

2007-12-22T10:10:17Z

Curx: add note removing module-init-tools

[[Category: HOWTO]]
[[Category: Templates]]
[[Category: Ubuntu]]

This article summarizes the experience of creating Ubunty Gutsy Gibbon (a.k.a. 7.10) template for OpenVZ.

Template creation is based on debootstrap, and the procedure is similar to [[Debian template creation]], but it differs in some subtle details.

== Prerequisites ==

=== debootstrap ===
You have to have a debootstrap working for Gutsy, i.e. you should have
* debootstrap and its dependencies
* /usr/lib/debootstrap/scripts/gutsy file

The simplest way to have it all is to work on an Ubunty Gutsy system (be it on a real machine or inside a VE). If you don't have debootstrap installed, this is the command to install it:

# apt-get install debootstrap

On a Gentoo Linux, debootstrap is also available, this is how you can install it:

# emerge debootstrap

=== vzctl ===

You need vzctl-3.0.19 or later to work with Ubuntu Gutsy Gibbon. If vzctl-3.0.18 or earlier is used, you will not be able to run your VE. See {{bug|662}} for details.

Note: Older versions of vzctl have worked for me IF you install sysvinit (which will remove upstart). The only problem I had was the network did not start, so I added "/etc/init.d/networking restart" to /etc/re.local.

== Creating template ==

=== Running debootstrap ===

Create a working directory:

[HW]# mkdir gutsy-chroot

Run debootstrap to install a minimal Ubunty Gutsy system into that directory:

[HW]# debootstrap [--arch ''ARCH''] gutsy gutsy-chroot

If ARCH of VE0 is equal to VE, you can skip the --arch option, but if you need to build an OS template for another ''ARCH'', specify it explicitly:
* for AMD64/x86_64, use <code>amd64</code>
* for IA64, use <code>ia64</code>
* for i386 <code>i386</code>

=== Preparing/starting a VE ===

Now then you have an installation created by <code>debootstrap</code>, you can run it as a VE. In the example below VE ID of 777 is used; of course you can use any other non-allocated ID.

{{Note|an alternative way is using chroot instead of running a VE. This is not recommended because of security concerns.}}

==== Moving installation to VE private area ====

You should move the contents of gutsy-chroot directory into new VE private area, like this:

# mv gutsy-chroot /vz/private/777

==== Setting VE config ====
An initial config for the [[VE]] is needed:
# vzctl set 777 --applyconfig vps.basic --save

==== Setting VE OSTEMPLATE ====
Also, we need <code>OSTEMPLATE</code> to be set in VE configuration file, for the [[vzctl]] to work properly.

# echo "OSTEMPLATE=ubuntu-7.10" >> /etc/vz/conf/777.conf

==== Setting VE IP address ====
For the [[VE]] to be able to download updates from the Internet, we need a valid IP address for it:
# vzctl set 777 --ipadd x.x.x.x --save

{{Note|if you use private IP for the VE, you have to set up NAT as described in [[Using NAT for VE with private IPs]].}}

==== Setting DNS server for the VE ====
For the [[VE]] to be able to download updates from the Internet, we also need to specify a DNS for it:
# vzctl set 777 --nameserver x.x.x.x --save

Instead of <code>x.x.x.x</code>, specify the same IP that you have in your <code>/etc/resolv.conf</code>.

==== Starting VE ====
Now start the VE:
# vzctl start 777

=== Modify the installation ===

You have to do some things in order to modify the installation to better suit the environment it will be run in (i.e. a VE).

First, enter a VE:
# vzctl enter 777

{{Warning|Do not run the commands below on the hardware node, they are only to be run within the VE!}}

==== Remove unneeded packages ====

Some packages does not make sense in a VE, or are really optional. Remove those:

[VE]# dpkg -P ubuntu-minimal wpasupplicant wireless-tools \
udev pcmciautils initramfs-tools volumeid console-setup \
xkb-data usbutils mii-diag alsa-base alsa-utils ethtool \
module-init-tools linux-sound-base console-tools \
console-terminus busybox-initramfs libvolume-id0 \
ntpdate eject libasound2 pciutils tasksel tasksel-data \
laptop-detect

{{Note|on removing the imodule-init-tools, a fake-modprobe is needed for IPv6 adresses}}

Note that the above list of packages may be too extensive. Say, if you want to use <code>tasksel</code> tool, do not remove it — but then you have to let laptop-detect stay.

Clean up after udev:

[VE]# rm -fr /lib/udev

==== Disable getty ====
On a usual Linux system, getty is running on a virtual terminals, which a VE does not have. So, having getty running doesn't make sense; more to say, it complains it can not open terminal device and this clutters the logs.

So, first of all we stop all getty processes:

[VE]# initctl stop tty{1,2,3,4,5,6}

Next, we disable running getty. This can be done in two ways:

First way:
[VE]# rm /etc/event.d/tty*

Second way:
[VE]# dpkg -P system-services

Second way can be dangerous for future versions of system-services, but it's OK for now since the only service they carry is running gettys.

==== Set sane permissions for /root directory ====

[VE]# chmod 700 /root

==== Disable root login ====

[VE]# usermod -L root

==== "fake-modprobe" needed for IPv6 adresses ====

[VE]# ln -s /bin/true /sbin/modprobe

On setup IPv6, the command "modprobe -Q IPv6" is called, which fails without the "fake-modprobe"

==== Get new security updates ====

[VE]# apt-get update && apt-get upgrade

This didn't show anything for me, but might do something in the future.

==== Install some more packages ====

[VE]# apt-get install ssh quota

Feel free to add packages which you want to have in a default template to this command.

==== Fix SSH host keys ====
This is only useful if you installed SSH above. Each individual [[VE]] should have its own pair of SSH host keys. The code below will wipe out the existing SSH keys and instruct the newly-created [[VE]] to create new SSH keys on first boot.


<pre>
rm -f /etc/ssh/ssh_host_*
cat << EOF > /etc/rc2.d/S15ssh_gen_host_keys
#!/bin/sh
ssh-keygen -f /etc/ssh/ssh_host_rsa_key -t rsa -N ''
ssh-keygen -f /etc/ssh/ssh_host_dsa_key -t dsa -N ''
rm -f \$0
EOF
chmod a+x /etc/rc2.d/S15ssh_gen_host_keys
</pre>

==== Disable <code>sync()</code> for syslog ====

Turn off doing <tt>sync()</tt> on every write for <code>syslog</code>'s log files, to improve overall I/O performance.
In Ubuntu this is already done for most log files and levels, so you can omit this step if you know what you are doing.


<pre>[VE]# sed -i -e 's@$[[:space:]]$$/var/log/$@\1-\2@' /etc/syslog.conf</pre>

==== Fix <code>/etc/mtab</code> ====
Link <code>/etc/mtab</code> to <code>/proc/mounts</code>, so <code>df</code> and friends will work:
[VE]# rm -f /etc/mtab
[VE]# ln -s /proc/mounts /etc/mtab

After that, it would make sense to disable <code>mtab.sh</code> script which messes with <code>/etc/mtab</code>:
[VE]# update-rc.d -f mtab.sh remove

==== Disable some services ====

In most of the cases you don't want klogd to run -- the only exception is if you configure iptables to log some events -- so you can disable it:

[VE]# update-rc.d -f klogd remove

==== Hostname ====
Set proper hostname:
[VE]# echo "localhost" > /etc/hostname

==== Set /etc/hosts ====

[VE]# echo "127.0.0.1 localhost.localdomain localhost" > /etc/hosts

==== Add ptys to /dev ====

This is needed in case /dev/pts will not me mounted after VE start. In case /dev/ttyp* and /dev/ptyp* files are present, and LEGACY_PTYS support is enabled in the kernel, vzctl will still be able to enter VE.

[VE]# cd /dev && /sbin/MAKEDEV ptyp

==== Remove nameserver(s) ====

Remove DNS entries:
[VE]# > /etc/resolv.conf

==== Clean packages ====
After installing packages, you'll have some junk packages laying around in your cache. Since you don't want your template to have those, this command will wipe them out.
[VE]# apt-get clean

==== Cleaning up log files ====

[VE]# cd /var/log
[VE]# > messages; > auth.log; > kern.log; > bootstrap.log
[VE]# > dpkg.log; > syslog; > daemon.log; > apt/term.log
[VE]# rm -f *.0 *.1

==== Anything else? ====

Think of what else could be done to better suit your needs.

==== Exit from the VE ====

Now everything is done. Exit from the template and go back to the hardware node.

[VE]# exit

== Preparing for and packing template cache ==

The following commands are to be run in the host system (i.e. not inside a VE).

We don't need an IP for the VE anymore, and we definitely do not need it in template cache, so remove it:
[HW]# vzctl set 777 --ipdel all --save

Stop the VE:
[HW]# vzctl stop 777

Change dir to the VE private:
[HW]# cd /vz/private/777

Now create a cached OS tarball. In the command below, you'll want to replace <arch> with your architecture (i386, amd64, ia64, etc). '''Note the space and the dot at the end of the command'''.
[HW]# tar czf /vz/template/cache/ubuntu-7.10-<arch>-minimal.tar.gz .

Look at the resulting tarball to see its size is sane:
# ls -lh /vz/template/cache
-rw-r--r-- 1 root root 53M Nov 15 12:40 ubuntu-7.10-i386-minimal.tar.gz

== Testing template cache ==
We can now create a VE based on the just-created template cache. Be sure to change <tt>i386</tt> to your architecture just like you did when you named the tarball above.
[HW]# vzctl create 123456 --ostemplate ubuntu-7.10-<arch>-minimal

Now make sure that your new VE it works:
[HW]# vzctl start 123456
[HW]# vzctl exec 123456 ps axf

You should see that a few processes are running.

Other tests that could be done are:
[HW]# vzctl enter 123456
[VE]# ps axf
[VE]# mount
[VE]# dpkg -l
[VE]# logout
[HW]#

Feel free to do more tests.

== Final cleanup ==
Stop and remove the test VE you just created:
[HW]# vzctl stop 123456
[HW]# vzctl destroy 123456
[HW]# rm -f /etc/vz/conf/123456.conf.destroyed

Finally, let's remove the VE we used for OS template cache creation:
[HW]# vzctl destroy 777
[HW]# rm -f /etc/vz/conf/777.conf.destroyed

== Updating the template cache ==

See [[Updating Ubuntu template]]

Ubuntu Gutsy template creation

2007-12-22T10:05:47Z

Curx: typo removed

[[Category: HOWTO]]
[[Category: Templates]]
[[Category: Ubuntu]]

This article summarizes the experience of creating Ubunty Gutsy Gibbon (a.k.a. 7.10) template for OpenVZ.

Template creation is based on debootstrap, and the procedure is similar to [[Debian template creation]], but it differs in some subtle details.

== Prerequisites ==

=== debootstrap ===
You have to have a debootstrap working for Gutsy, i.e. you should have
* debootstrap and its dependencies
* /usr/lib/debootstrap/scripts/gutsy file

The simplest way to have it all is to work on an Ubunty Gutsy system (be it on a real machine or inside a VE). If you don't have debootstrap installed, this is the command to install it:

# apt-get install debootstrap

On a Gentoo Linux, debootstrap is also available, this is how you can install it:

# emerge debootstrap

=== vzctl ===

You need vzctl-3.0.19 or later to work with Ubuntu Gutsy Gibbon. If vzctl-3.0.18 or earlier is used, you will not be able to run your VE. See {{bug|662}} for details.

Note: Older versions of vzctl have worked for me IF you install sysvinit (which will remove upstart). The only problem I had was the network did not start, so I added "/etc/init.d/networking restart" to /etc/re.local.

== Creating template ==

=== Running debootstrap ===

Create a working directory:

[HW]# mkdir gutsy-chroot

Run debootstrap to install a minimal Ubunty Gutsy system into that directory:

[HW]# debootstrap [--arch ''ARCH''] gutsy gutsy-chroot

If ARCH of VE0 is equal to VE, you can skip the --arch option, but if you need to build an OS template for another ''ARCH'', specify it explicitly:
* for AMD64/x86_64, use <code>amd64</code>
* for IA64, use <code>ia64</code>
* for i386 <code>i386</code>

=== Preparing/starting a VE ===

Now then you have an installation created by <code>debootstrap</code>, you can run it as a VE. In the example below VE ID of 777 is used; of course you can use any other non-allocated ID.

{{Note|an alternative way is using chroot instead of running a VE. This is not recommended because of security concerns.}}

==== Moving installation to VE private area ====

You should move the contents of gutsy-chroot directory into new VE private area, like this:

# mv gutsy-chroot /vz/private/777

==== Setting VE config ====
An initial config for the [[VE]] is needed:
# vzctl set 777 --applyconfig vps.basic --save

==== Setting VE OSTEMPLATE ====
Also, we need <code>OSTEMPLATE</code> to be set in VE configuration file, for the [[vzctl]] to work properly.

# echo "OSTEMPLATE=ubuntu-7.10" >> /etc/vz/conf/777.conf

==== Setting VE IP address ====
For the [[VE]] to be able to download updates from the Internet, we need a valid IP address for it:
# vzctl set 777 --ipadd x.x.x.x --save

{{Note|if you use private IP for the VE, you have to set up NAT as described in [[Using NAT for VE with private IPs]].}}

==== Setting DNS server for the VE ====
For the [[VE]] to be able to download updates from the Internet, we also need to specify a DNS for it:
# vzctl set 777 --nameserver x.x.x.x --save

Instead of <code>x.x.x.x</code>, specify the same IP that you have in your <code>/etc/resolv.conf</code>.

==== Starting VE ====
Now start the VE:
# vzctl start 777

=== Modify the installation ===

You have to do some things in order to modify the installation to better suit the environment it will be run in (i.e. a VE).

First, enter a VE:
# vzctl enter 777

{{Warning|Do not run the commands below on the hardware node, they are only to be run within the VE!}}

==== Remove unneeded packages ====

Some packages does not make sense in a VE, or are really optional. Remove those:

[VE]# dpkg -P ubuntu-minimal wpasupplicant wireless-tools \
udev pcmciautils initramfs-tools volumeid console-setup \
xkb-data usbutils mii-diag alsa-base alsa-utils ethtool \
module-init-tools linux-sound-base console-tools \
console-terminus busybox-initramfs libvolume-id0 \
ntpdate eject libasound2 pciutils tasksel tasksel-data \
laptop-detect

Note that the above list of packages may be too extensive. Say, if you want to use <code>tasksel</code> tool, do not remove it — but then you have to let laptop-detect stay.

Clean up after udev:

[VE]# rm -fr /lib/udev

==== Disable getty ====
On a usual Linux system, getty is running on a virtual terminals, which a VE does not have. So, having getty running doesn't make sense; more to say, it complains it can not open terminal device and this clutters the logs.

So, first of all we stop all getty processes:

[VE]# initctl stop tty{1,2,3,4,5,6}

Next, we disable running getty. This can be done in two ways:

First way:
[VE]# rm /etc/event.d/tty*

Second way:
[VE]# dpkg -P system-services

Second way can be dangerous for future versions of system-services, but it's OK for now since the only service they carry is running gettys.

==== Set sane permissions for /root directory ====

[VE]# chmod 700 /root

==== Disable root login ====

[VE]# usermod -L root

==== "fake-modprobe" needed for IPv6 adresses ====

[VE]# ln -s /bin/true /sbin/modprobe

On setup IPv6, the command "modprobe -Q IPv6" is called, which fails without the "fake-modprobe"

==== Get new security updates ====

[VE]# apt-get update && apt-get upgrade

This didn't show anything for me, but might do something in the future.

==== Install some more packages ====

[VE]# apt-get install ssh quota

Feel free to add packages which you want to have in a default template to this command.

==== Fix SSH host keys ====
This is only useful if you installed SSH above. Each individual [[VE]] should have its own pair of SSH host keys. The code below will wipe out the existing SSH keys and instruct the newly-created [[VE]] to create new SSH keys on first boot.


<pre>
rm -f /etc/ssh/ssh_host_*
cat << EOF > /etc/rc2.d/S15ssh_gen_host_keys
#!/bin/sh
ssh-keygen -f /etc/ssh/ssh_host_rsa_key -t rsa -N ''
ssh-keygen -f /etc/ssh/ssh_host_dsa_key -t dsa -N ''
rm -f \$0
EOF
chmod a+x /etc/rc2.d/S15ssh_gen_host_keys
</pre>

==== Disable <code>sync()</code> for syslog ====

Turn off doing <tt>sync()</tt> on every write for <code>syslog</code>'s log files, to improve overall I/O performance.
In Ubuntu this is already done for most log files and levels, so you can omit this step if you know what you are doing.


<pre>[VE]# sed -i -e 's@$[[:space:]]$$/var/log/$@\1-\2@' /etc/syslog.conf</pre>

==== Fix <code>/etc/mtab</code> ====
Link <code>/etc/mtab</code> to <code>/proc/mounts</code>, so <code>df</code> and friends will work:
[VE]# rm -f /etc/mtab
[VE]# ln -s /proc/mounts /etc/mtab

After that, it would make sense to disable <code>mtab.sh</code> script which messes with <code>/etc/mtab</code>:
[VE]# update-rc.d -f mtab.sh remove

==== Disable some services ====

In most of the cases you don't want klogd to run -- the only exception is if you configure iptables to log some events -- so you can disable it:

[VE]# update-rc.d -f klogd remove

==== Hostname ====
Set proper hostname:
[VE]# echo "localhost" > /etc/hostname

==== Set /etc/hosts ====

[VE]# echo "127.0.0.1 localhost.localdomain localhost" > /etc/hosts

==== Add ptys to /dev ====

This is needed in case /dev/pts will not me mounted after VE start. In case /dev/ttyp* and /dev/ptyp* files are present, and LEGACY_PTYS support is enabled in the kernel, vzctl will still be able to enter VE.

[VE]# cd /dev && /sbin/MAKEDEV ptyp

==== Remove nameserver(s) ====

Remove DNS entries:
[VE]# > /etc/resolv.conf

==== Clean packages ====
After installing packages, you'll have some junk packages laying around in your cache. Since you don't want your template to have those, this command will wipe them out.
[VE]# apt-get clean

==== Cleaning up log files ====

[VE]# cd /var/log
[VE]# > messages; > auth.log; > kern.log; > bootstrap.log
[VE]# > dpkg.log; > syslog; > daemon.log; > apt/term.log
[VE]# rm -f *.0 *.1

==== Anything else? ====

Think of what else could be done to better suit your needs.

==== Exit from the VE ====

Now everything is done. Exit from the template and go back to the hardware node.

[VE]# exit

== Preparing for and packing template cache ==

The following commands are to be run in the host system (i.e. not inside a VE).

We don't need an IP for the VE anymore, and we definitely do not need it in template cache, so remove it:
[HW]# vzctl set 777 --ipdel all --save

Stop the VE:
[HW]# vzctl stop 777

Change dir to the VE private:
[HW]# cd /vz/private/777

Now create a cached OS tarball. In the command below, you'll want to replace <arch> with your architecture (i386, amd64, ia64, etc). '''Note the space and the dot at the end of the command'''.
[HW]# tar czf /vz/template/cache/ubuntu-7.10-<arch>-minimal.tar.gz .

Look at the resulting tarball to see its size is sane:
# ls -lh /vz/template/cache
-rw-r--r-- 1 root root 53M Nov 15 12:40 ubuntu-7.10-i386-minimal.tar.gz

== Testing template cache ==
We can now create a VE based on the just-created template cache. Be sure to change <tt>i386</tt> to your architecture just like you did when you named the tarball above.
[HW]# vzctl create 123456 --ostemplate ubuntu-7.10-<arch>-minimal

Now make sure that your new VE it works:
[HW]# vzctl start 123456
[HW]# vzctl exec 123456 ps axf

You should see that a few processes are running.

Other tests that could be done are:
[HW]# vzctl enter 123456
[VE]# ps axf
[VE]# mount
[VE]# dpkg -l
[VE]# logout
[HW]#

Feel free to do more tests.

== Final cleanup ==
Stop and remove the test VE you just created:
[HW]# vzctl stop 123456
[HW]# vzctl destroy 123456
[HW]# rm -f /etc/vz/conf/123456.conf.destroyed

Finally, let's remove the VE we used for OS template cache creation:
[HW]# vzctl destroy 777
[HW]# rm -f /etc/vz/conf/777.conf.destroyed

== Updating the template cache ==

See [[Updating Ubuntu template]]

Ubuntu Gutsy template creation

2007-12-22T10:04:46Z

Curx: add fake-modprobe, needed for IPv6 adresses in VE

[[Category: HOWTO]]
[[Category: Templates]]
[[Category: Ubuntu]]

This article summarizes the experience of creating Ubunty Gutsy Gibbon (a.k.a. 7.10) template for OpenVZ.

Template creation is based on debootstrap, and the procedure is similar to [[Debian template creation]], but it differs in some subtle details.

== Prerequisites ==

=== debootstrap ===
You have to have a debootstrap working for Gutsy, i.e. you should have
* debootstrap and its dependencies
* /usr/lib/debootstrap/scripts/gutsy file

The simplest way to have it all is to work on an Ubunty Gutsy system (be it on a real machine or inside a VE). If you don't have debootstrap installed, this is the command to install it:

# apt-get install debootstrap

On a Gentoo Linux, debootstrap is also available, this is how you can install it:

# emerge debootstrap

=== vzctl ===

You need vzctl-3.0.19 or later to work with Ubuntu Gutsy Gibbon. If vzctl-3.0.18 or earlier is used, you will not be able to run your VE. See {{bug|662}} for details.

Note: Older versions of vzctl have worked for me IF you install sysvinit (which will remove upstart). The only problem I had was the network did not start, so I added "/etc/init.d/networking restart" to /etc/re.local.

== Creating template ==

=== Running debootstrap ===

Create a working directory:

[HW]# mkdir gutsy-chroot

Run debootstrap to install a minimal Ubunty Gutsy system into that directory:

[HW]# debootstrap [--arch ''ARCH''] gutsy gutsy-chroot

If ARCH of VE0 is equal to VE, you can skip the --arch option, but if you need to build an OS template for another ''ARCH'', specify it explicitly:
* for AMD64/x86_64, use <code>amd64</code>
* for IA64, use <code>ia64</code>
* for i386 <code>i386</code>

=== Preparing/starting a VE ===

Now then you have an installation created by <code>debootstrap</code>, you can run it as a VE. In the example below VE ID of 777 is used; of course you can use any other non-allocated ID.

{{Note|an alternative way is using chroot instead of running a VE. This is not recommended because of security concerns.}}

==== Moving installation to VE private area ====

You should move the contents of gutsy-chroot directory into new VE private area, like this:

# mv gutsy-chroot /vz/private/777

==== Setting VE config ====
An initial config for the [[VE]] is needed:
# vzctl set 777 --applyconfig vps.basic --save

==== Setting VE OSTEMPLATE ====
Also, we need <code>OSTEMPLATE</code> to be set in VE configuration file, for the [[vzctl]] to work properly.

# echo "OSTEMPLATE=ubuntu-7.10" >> /etc/vz/conf/777.conf

==== Setting VE IP address ====
For the [[VE]] to be able to download updates from the Internet, we need a valid IP address for it:
# vzctl set 777 --ipadd x.x.x.x --save

{{Note|if you use private IP for the VE, you have to set up NAT as described in [[Using NAT for VE with private IPs]].}}

==== Setting DNS server for the VE ====
For the [[VE]] to be able to download updates from the Internet, we also need to specify a DNS for it:
# vzctl set 777 --nameserver x.x.x.x --save

Instead of <code>x.x.x.x</code>, specify the same IP that you have in your <code>/etc/resolv.conf</code>.

==== Starting VE ====
Now start the VE:
# vzctl start 777

=== Modify the installation ===

You have to do some things in order to modify the installation to better suit the environment it will be run in (i.e. a VE).

First, enter a VE:
# vzctl enter 777

{{Warning|Do not run the commands below on the hardware node, they are only to be run within the VE!}}

==== Remove unneeded packages ====

Some packages does not make sense in a VE, or are really optional. Remove those:

[VE]# dpkg -P ubuntu-minimal wpasupplicant wireless-tools \
udev pcmciautils initramfs-tools volumeid console-setup \
xkb-data usbutils mii-diag alsa-base alsa-utils ethtool \
module-init-tools linux-sound-base console-tools \
console-terminus busybox-initramfs libvolume-id0 \
ntpdate eject libasound2 pciutils tasksel tasksel-data \
laptop-detect

Note that the above list of packages may be too extensive. Say, if you want to use <code>tasksel</code> tool, do not remove it — but then you have to let laptop-detect stay.

Clean up after udev:

[VE]# rm -fr /lib/udev

==== Disable getty ====
On a usual Linux system, getty is running on a virtual terminals, which a VE does not have. So, having getty running doesn't make sense; more to say, it complains it can not open terminal device and this clutters the logs.

So, first of all we stop all getty processes:

[VE]# initctl stop tty{1,2,3,4,5,6}

Next, we disable running getty. This can be done in two ways:

First way:
[VE]# rm /etc/event.d/tty*

Second way:
[VE]# dpkg -P system-services

Second way can be dangerous for future versions of system-services, but it's OK for now since the only service they carry is running gettys.

==== Set sane permissions for /root directory ====

[VE]# chmod 700 /root

==== Disable root login ====

[VE]# usermod -L root

==== "fake-modprobe" needed for IPv6 a====

[VE]# ln -s /bin/true /sbin/modprobe

On setup IPv6, the command "modprobe -Q IPv6" is called, which fails without the "fake-modprobe"

==== Get new security updates ====

[VE]# apt-get update && apt-get upgrade

This didn't show anything for me, but might do something in the future.

==== Install some more packages ====

[VE]# apt-get install ssh quota

Feel free to add packages which you want to have in a default template to this command.

==== Fix SSH host keys ====
This is only useful if you installed SSH above. Each individual [[VE]] should have its own pair of SSH host keys. The code below will wipe out the existing SSH keys and instruct the newly-created [[VE]] to create new SSH keys on first boot.


<pre>
rm -f /etc/ssh/ssh_host_*
cat << EOF > /etc/rc2.d/S15ssh_gen_host_keys
#!/bin/sh
ssh-keygen -f /etc/ssh/ssh_host_rsa_key -t rsa -N ''
ssh-keygen -f /etc/ssh/ssh_host_dsa_key -t dsa -N ''
rm -f \$0
EOF
chmod a+x /etc/rc2.d/S15ssh_gen_host_keys
</pre>

==== Disable <code>sync()</code> for syslog ====

Turn off doing <tt>sync()</tt> on every write for <code>syslog</code>'s log files, to improve overall I/O performance.
In Ubuntu this is already done for most log files and levels, so you can omit this step if you know what you are doing.


<pre>[VE]# sed -i -e 's@$[[:space:]]$$/var/log/$@\1-\2@' /etc/syslog.conf</pre>

==== Fix <code>/etc/mtab</code> ====
Link <code>/etc/mtab</code> to <code>/proc/mounts</code>, so <code>df</code> and friends will work:
[VE]# rm -f /etc/mtab
[VE]# ln -s /proc/mounts /etc/mtab

After that, it would make sense to disable <code>mtab.sh</code> script which messes with <code>/etc/mtab</code>:
[VE]# update-rc.d -f mtab.sh remove

==== Disable some services ====

In most of the cases you don't want klogd to run -- the only exception is if you configure iptables to log some events -- so you can disable it:

[VE]# update-rc.d -f klogd remove

==== Hostname ====
Set proper hostname:
[VE]# echo "localhost" > /etc/hostname

==== Set /etc/hosts ====

[VE]# echo "127.0.0.1 localhost.localdomain localhost" > /etc/hosts

==== Add ptys to /dev ====

This is needed in case /dev/pts will not me mounted after VE start. In case /dev/ttyp* and /dev/ptyp* files are present, and LEGACY_PTYS support is enabled in the kernel, vzctl will still be able to enter VE.

[VE]# cd /dev && /sbin/MAKEDEV ptyp

==== Remove nameserver(s) ====

Remove DNS entries:
[VE]# > /etc/resolv.conf

==== Clean packages ====
After installing packages, you'll have some junk packages laying around in your cache. Since you don't want your template to have those, this command will wipe them out.
[VE]# apt-get clean

==== Cleaning up log files ====

[VE]# cd /var/log
[VE]# > messages; > auth.log; > kern.log; > bootstrap.log
[VE]# > dpkg.log; > syslog; > daemon.log; > apt/term.log
[VE]# rm -f *.0 *.1

==== Anything else? ====

Think of what else could be done to better suit your needs.

==== Exit from the VE ====

Now everything is done. Exit from the template and go back to the hardware node.

[VE]# exit

== Preparing for and packing template cache ==

The following commands are to be run in the host system (i.e. not inside a VE).

We don't need an IP for the VE anymore, and we definitely do not need it in template cache, so remove it:
[HW]# vzctl set 777 --ipdel all --save

Stop the VE:
[HW]# vzctl stop 777

Change dir to the VE private:
[HW]# cd /vz/private/777

Now create a cached OS tarball. In the command below, you'll want to replace <arch> with your architecture (i386, amd64, ia64, etc). '''Note the space and the dot at the end of the command'''.
[HW]# tar czf /vz/template/cache/ubuntu-7.10-<arch>-minimal.tar.gz .

Look at the resulting tarball to see its size is sane:
# ls -lh /vz/template/cache
-rw-r--r-- 1 root root 53M Nov 15 12:40 ubuntu-7.10-i386-minimal.tar.gz

== Testing template cache ==
We can now create a VE based on the just-created template cache. Be sure to change <tt>i386</tt> to your architecture just like you did when you named the tarball above.
[HW]# vzctl create 123456 --ostemplate ubuntu-7.10-<arch>-minimal

Now make sure that your new VE it works:
[HW]# vzctl start 123456
[HW]# vzctl exec 123456 ps axf

You should see that a few processes are running.

Other tests that could be done are:
[HW]# vzctl enter 123456
[VE]# ps axf
[VE]# mount
[VE]# dpkg -l
[VE]# logout
[HW]#

Feel free to do more tests.

== Final cleanup ==
Stop and remove the test VE you just created:
[HW]# vzctl stop 123456
[HW]# vzctl destroy 123456
[HW]# rm -f /etc/vz/conf/123456.conf.destroyed

Finally, let's remove the VE we used for OS template cache creation:
[HW]# vzctl destroy 777
[HW]# rm -f /etc/vz/conf/777.conf.destroyed

== Updating the template cache ==

See [[Updating Ubuntu template]]

Package managers

2007-12-16T15:08:08Z

Curx: add : see changelog in Deb packages

With OpenVZ, you can run many different Linux distributions on a single box. One particular thing in which distributions differ is package management. This article summarizes how to perform various common package management tasks on a different distributions.

{| class="wikitable"
! align="center" | Action
! RPM RHEL, Fedora, CentOS, Mandrake, SUSE, ...
! DEB Debian, Ubuntu
! Ebuild Gentoo, Sabayon
|-
| colspan="4" align="center" | '''Basic queries'''
|-
! List of all installed packages
|| <code>rpm -qa</code>
|| <code>dpkg -l</code>
|| <code>equery list</code>
|-
! List of installing packages matching ''substr''
|| <code>rpm -qa ''\*substr\*''</code>
|| <code>dpkg -l ''\*substr\*''</code>
|| <code>equery list ''substr''</code>
|-
! Basic information about an installed ''package''
|| <code>rpm -qi ''package''</code>
|| <code>dpkg -p ''package''</code>
|| <code>-???-</code>
|-
! List of files in a given ''package''
|| <code>rpm -ql ''package''</code>
|| <code>dpkg -L ''package''</code>
|| <code>equery files ''package''</code>
|-
| colspan="4" align="center" | '''Advanced queries'''
|-
! Which package a ''file'' belongs to?
|| <code>rpm -qf ''file''</code>
|| <code>dpkg -S ''file''</code>
|| <code>equery belongs ''file''</code>
|-
! Check the hash (i.e. MD5 etc.) sums of an installed package
|| <code>rpm -V ''package''</code>
|| <code>debsums -ca ''package''</code>
|| <code>equery check ''package''</code>
|-
! Show pre/post install/uninstall scripts from a ''package''
|| <code>rpm -q --scripts ''package''</code>
|| <code>less /var/lib/dpkg/info/''package''.{pre,post,config}*</code>
|| <code>-???-</code>
|-
! Show change log for a ''package''
|| <code>rpm -q --changelog ''package''</code>
|| <code>zcat /usr/share/doc/package/changelog.Debian.gz</code>
|| <code>-???-</code>
|-
| colspan="4" align="center" | '''Local package installation/upgrade/removal'''
|-
! Install a package from local ''package_file''
|| <code>rpm -ihv ''package_file*.rpm'' yum localinstall ''package_file*.rpm''<ref name="localinstall">In case there are unsatisfied dependencies for ''package_file'', yum will try to get and install it from known repositores.</ref></code>
|| <code>dpkg -i ''package_file*.deb'' <ref name="apt">Usually it is not necessary to download packages manually and install them. Use apt-cache search ''name'' to search for package in configured repositories and apt-get install ''package'' to install package and all it's dependencies</ref></code>
|| <code>-???-</code>
|-
! Upgrade a package from local ''package_file''
|| <code>rpm -Uhv ''package_file*.rpm''</code>
|| <code>dpkg -i ''package_file*.deb'' <ref name="apt"/></code>
|| <code>-???-</code>
|-
! Remove an installed ''package''
|| <code>rpm -e ''package''</code>
|| <code>dpkg -r ''package''</code> 
<code>dpkg -P ''package''</code>
|| <code>emerge --unmerge ''package''</code> 
<code>emerge --prune ''package''</code>
|-
| colspan="4" align="center" | '''Package installation from repositories'''
|-
! Install a ''package''
|| <code>yum install ''package''</code> 
<code>urpmi ''package''</code>
|| <code>apt-get install ''package''</code> 
<code>aptitude install ''package''</code>
|| <code>emerge -av ''package''</code>
|-
! Only download a ''package'' from repository, do not install
|| <code>-???-</code>
|| <code>apt-get install --download-only --reinstall ''package''</code><ref name="dpkgdir">Package will reside in /var/cache/apt/archives.</ref>
|| <code>emerge -avf ''package''</code><ref name="distfiles">Package sources will reside in /usr/portage/distfiles.</ref>
|-
| colspan="4" align="center" | '''Get information about package interdependencies'''
|-
! What a given ''package'' provides?
|| <code>rpm -q --provides ''package''</code>
|| <code>dpkg-query -W -f='${Provides}\n' ''package''</code>
|| <code>-???-</code>
|-
! What a given ''package'' requires?
|| <code>rpm -q --requires ''package''</code>
|| <code>dpkg-query -W -f='${Depends}\n' ''package''</code>
|| <code>-???-</code>
|-
! Which installed package(s) provide a given ''dependency''<ref name="dep">In rpm world, a ''dependency'' can be a package name, a file, or a special atom like <code>perl(IO::Zlib)</code> for a perl module. In deb world, this can be either real or virtual package name.</ref>?
|| <code>rpm -q --whatprovides ''dependency''</code>
|| <code>-???-</code>
|| <code>-???-</code>
|-
! Which installed package(s) require a given ''dependency''<ref name="dep"/>?
|| <code>rpm -q --whatrequires ''dependency''</code>
|| <code>-???-</code>
|| <code>-???-</code>
|-
| colspan="4" align="center" | '''Working with package files'''
|-
! Unpack a package ''file'' to local directory
|| <code>rpm2cpio ''file.rpm'' | cpio -id</code>
|| <code>dpkg -x ''file.deb'' .</code>
|| N/A
|-
! Check package file integrity (checksums, signatures...)
|| <code>rpm -K ''file.rpm''</code>
|| -???-
|| N/A
|}

== Notes==
<references/>

[[Category: HOWTO]]
[[Category: Templates]
[[Category: Debian]]
[[Category: Ubuntu]]
[[Category: Gentoo]]

User:Curx

2007-12-16T14:55:51Z

Curx:

"curx" aka Thorsten Schifferdecker

--//--

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

This guide tells how to install the kernel and the tools on [http://www.debian.org Debian] and related Distribution like [http://www.ubuntu.com/ Ubuntu].

== Requirements ==

=== Filesystems ===
It is recommended to use a separate partition for VEs private directories (by default /var/lib/vz/private/<veid>). The reason why you should do so is that if you wish to use OpenVZ per-VE disk quota, you won't be able to use usual Linux disk quotas on the same partition. Bear in mind, that per-VE quota in this context includes not only pure per-VE quota, but also usual Linux disk quota used in VE, not on [[HN]].

At least try to avoid using root partition for VEs, because the root user of VE will be able to overcome 5% disk space barrier in some situations. This way HN root partition can be completely filled and it will break the system.

OpenVZ per-VE disk quota is supported only for ext2/ext3 filesystems. So use one of these filesystems (ext3 is recommended) if you need per-VE disk quota.

=== Repository setup ===

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

Ola Lundqvist <opal@debian.org> --> apt-uri [http://download.openvz.org/debian http://download.openvz.org/debian]

Thorsten Schiffedecker <tsd@debian.systs.org> --> apt-uri [http://download.openvz.org/debian-systs http://download.openvz.org/debian-systs] (Mirror of OpenVZ Repository from http://debian.systs.org)

{{Note|The next steps used the Repository http://download.openvz.org/debian-systs}}

{{Note|per default on ubuntu system, root task are done with [https://help.ubuntu.com/community/RootSudo sudo]}}

This can be achieved by the following commands, as root or as privileged "sudo" user

<pre>
# [sudo] echo "deb http://download.openvz.org/debian-systs etch openvz" >> /etc/apt/sources.list
# wget http://download.openvz.org/debian-systs/dso_archiv_signing_key.asc
# [sudo] apt-key add dso_archiv_signing_key.asc
# [sudo] apt-get update
</pre>

== Kernel installation ==

{{Note|In case you want to recompile the OpenVZ kernel yourself on Debian, see [[kernel build debian]].}}

First, you need to choose what “flavor” of the kernel you want to install.

<pre>
# apt-get install <flavour>
</pre>

=== Configuring the bootloader ===

In case GRUB is used as the boot loader, it will be configured automatically: 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 VPSs (create, destroy, start, stop, set parameters etc.)
; vzquota
: A utility to manage quotas for VPSs. 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

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

{{Note|You can 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}}

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

=== VE OS Templates ===

To install a VE, you need VE OS Template(s), precreated can be found [http://download.openvz.org/contrib/template/precreated/ here] or create it : [http://wiki.openvz.org/Debian_template_creation Debian] , [http://wiki.openvz.org/Ubuntu_Gutsy_template_creation ubuntu] and all about [http://wiki.openvz.org/Category:Templates Templates]

{{Note|Setup your prefered standard OS Template : edit the /etc/vz/vz.conf}}

{{Note|Debian Packages of a precreate Debian 4.0 can be fetch from Repository at http://download.openvz.org/debian-systs }}

# [sudo] apt-get install vzctl-ostmpl-debian

== Additial user tools ==

; vzprocps
: A set of utilities to provide system information (vzps and vztop)
; [http://wiki.openvz.org/Backup_of_a_running_VE_with_vzdump vzdump]
: A utility to backup and restore VE.

{{Note|Debian Packages can be fetch from Repository at http://download.openvz.org/debian-systs }}

# [sudo] apt-get install vzprocps vzdump

[[Category: HOWTO]]
[[Category: Installation]]

User:Curx

2007-12-16T14:54:40Z

Curx:

"curx" aka Thorsten Schifferdecker

--//--

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

This guide tells how to install the kernel and the tools on [http://www.debian.org Debian] and related Distribution like [http://www.ubuntu.com/ Ubuntu].

== Requirements ==

=== Filesystems ===
It is recommended to use a separate partition for VEs private directories (by default /var/lib/vz/private/<veid>). The reason why you should do so is that if you wish to use OpenVZ per-VE disk quota, you won't be able to use usual Linux disk quotas on the same partition. Bear in mind, that per-VE quota in this context includes not only pure per-VE quota, but also usual Linux disk quota used in VE, not on [[HN]].

At least try to avoid using root partition for VEs, because the root user of VE will be able to overcome 5% disk space barrier in some situations. This way HN root partition can be completely filled and it will break the system.

OpenVZ per-VE disk quota is supported only for ext2/ext3 filesystems. So use one of these filesystems (ext3 is recommended) if you need per-VE disk quota.

=== Repository setup ===

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

Ola Lundqvist <opal@debian.org> --> apt-uri [http://download.openvz.org/debian http://download.openvz.org/debian]

Thorsten Schiffedecker <tsd@debian.systs.org> --> apt-uri [http://download.openvz.org/debian-systs http://download.openvz.org/debian-systs] (Mirror of OpenVZ Repository from http://debian.systs.org)

{{Note|The next steps used the Repository http://download.openvz.org/debian-systs}}

{{Note|per default on ubuntu system, root task are done with [https://help.ubuntu.com/community/RootSudo sudo]}}

This can be achieved by the following commands, as root or as privileged "sudo" user

<pre>
# [sudo] echo "deb http://download.openvz.org/debian-systs etch openvz" >> /etc/apt/sources.list
# wget http://download.openvz.org/debian-systs/dso_archiv_signing_key.asc
# [sudo] apt-key add dso_archiv_signing_key.asc
# [sudo] apt-get update
</pre>

== Kernel installation ==

{{Note|In case you want to recompile the OpenVZ kernel yourself on Debian, see [[kernel build debian]].}}

First, you need to choose what “flavor” of the kernel you want to install.

<pre>
# apt-get install <flavour>
</pre>

=== Configuring the bootloader ===

In case GRUB is used as the boot loader, it will be configured automatically: 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 VPSs (create, destroy, start, stop, set parameters etc.)
; vzquota
: A utility to manage quotas for VPSs. 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

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

{{Note|You can 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}}

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

=== VE OS Templates ===

To install a VE, you need VE OS Template(s), precreated can be found at [http://download.openvz.org/contrib/template/precreated/ here] or create it : [http://wiki.openvz.org/Debian_template_creation Debian] , [http://wiki.openvz.org/Ubuntu_Gutsy_template_creation ubuntu] and all about [http://wiki.openvz.org/Category:Templates Templates]

{{Note|Setup your prefered standard OS Template : edit the /etc/vz/vz.conf}}

{{Note|Debian Packages of a precreate Debian 4.0 can be fetch from Repository at http://download.openvz.org/debian-systs }}

# [sudo] apt-get install vzctl-ostmpl-debian

== Additial user tools ==

; vzprocps
: A set of utilities to provide system information (vzps and vztop)
; [http://wiki.openvz.org/Backup_of_a_running_VE_with_vzdump vzdump]
: A utility to backup and restore VE.

{{Note|Debian Packages can be fetch from Repository at http://download.openvz.org/debian-systs }}

# [sudo] apt-get install vzprocps vzdump

[[Category: HOWTO]]
[[Category: Installation]]

Installation on Debian/old

2007-11-14T21:15:34Z

Curx: update dso kernel packages to 048.1

= Sarge-Dapper (OldStable) =
The OpenVZ packages at http://debian.systs.org/ aimed to install OpenVZ in a easy way, some tasks are even completed during the install process!

== edit apt source settings ==
Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/debian sarge openvz
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

== precompiled kernel images at debian.systs.org (dso) ==
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 deb.
If there is more than 4 Gb of RAM available, use the kernel-enterprise deb.
Otherwise, use the plain kernel deb (kernel).

{| class="wikitable"
|+'''Kernel flavors list'''
! Kernel type !! Description !! Hardware !! Use case
|-
! -
| 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-image: i368 and amd64
<pre>
ovzkernel-2.6.9
ovzkernel-2.6.9-smp
</pre>

kernel-image: i386 only:
<pre>
ovzkernel-2.6.9-enterprise
ovzkernel-2.6.9-entnosplit
</pre>

OpenVZ tool(s) for i386 and amd64
<pre>
vzctl
vzquota
vzprocps
vzdump
</pre>

template(s) for i368 and amd64 : Debian 3.1 Minimal
<pre>
vzctl-ostmpl-debian
</pre>

== installing the kernel-images, toolset and debian-os-template ==
Example: install the stable OpenVZ kernel, tools and Debian OS Template

# aptitude install ovzkernel-2.6.9 vzctl vzquota vzdump vzctl-ostmpl-debian

If you are using GRUB, maybe you need to update the /boot/grub/menu.lst file
(can be configured at /etc/kernel-img.conf):

# /sbin/grub-update

Reboot in your new Debian Sarge OpenVZ System

# reboot

That's all :-)

Now it's time to setup your VEs with the minimal Debian-3.1 Template, create new one or download another precreated OS-Template.

= Etch (Stable) =
OpenVZ is now a part of Debian Etch repository. The packages are 'vzctl' and 'vzquota'.

== install the kernel-image ==

=== precompiled kernel images at download.openvz.org ===

A Debian OpenVZ kernel repository is online, for direct access http://download.openvz.org/kernel/debian/etch/

add to your "/etc/apt/sources.list"
<pre>
deb http://download.openvz.org/debian etch main
</pre>

Update package lists
<pre>
# apt-get update
</pre>

List downloadable OpenVZ linux-images
<pre>
# apt-cache search linux-image-2.6.18-openvz
</pre>

Install a kernel
<pre>
# apt-get install <linux-image>
</pre>

=== precompiled kernel images at debian.systs.org ===

Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ etch openvz
</pre>

Add the signing key of debian.systs.org (dso) apt-keyring, (need root permissions)
<pre>
# wget http://debian.systs.org/dso_archiv_signing_key.asc -q -O - | apt-key add -
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

Choose a linux image (version 028stab048.1) :
<pre>
ovzkernel-2.6.18 (i386 and amd64)
ovzkernel-2.6.18-smp (i386 and amd64)
ovzkernel-2.6.18-enterprise only (i386)
</pre>

# apt-get install <linux-image>

=== Build your own kernel-image (debian way) ===

==== Installing sources ====

To install the kernel-source and the OpenVZ kernel patch, run:
# apt-get install kernel-package linux-source-2.6.18 kernel-patch-openvz libncurses5-dev

==== Unpacking ====

Unpack the kernel source:
<pre>
# cd /usr/src
# tar xjf linux-source-2.6.18.tar.bz2
# cd linux-source-2.6.18
</pre>

==== Kernel config ====

You need a kernel config.
You can use the config of the debian-kernel:
# cp /boot/config-2.6.18-5-686 .config

'''Or''' get a 2.6.18 kernel configuration from http://download.openvz.org/kernel/branches/2.6.18/current/configs/ (depending on your architecture; the below example is for i686):
# wget http://download.openvz.org/kernel/branches/2.6.18/current/configs/kernel-2.6.18-i686.config.ovz -O .config

==== Patching and configuring ====

Now you can apply the openvz kernel patch and modify your kernel-config:
# ../kernel-patches/all/apply/openvz
# make menuconfig

You need the following OpenVZ kernel config settings:
<pre>
(taken from OpenVZ Kernel 2.6.18-028test010.1 on 686)

Filesystem
\_ [*] Second extended fs support (CONFIG_EXT2_FS)
\_ [*] Ext3 journalling file system support (CONFIG_EXT3_FS)
\_ [M] Quota Support (CONFIG_QUOTA)
\_ [*] Compatibility with older quotactl interface (CONFIG_QUOTA_COMPAT)
\_ [*]Quota format v2 support (CONFIG_QFMT_V2)
\_ [*] VPS filesystem (CONFIG_SIM_FS)
\_ [M] Virtuozzo Disk Quota support (CONFIG_VZ_QUOTA)
\-> [*] Per-user and per-group quota in Virtuozzo quota partitions (VZ_QUOTA_UGID)

Security
\->[ ] Enable different security models

OpenVZ ... (what else :-)
\_[*] 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)
\_ [*] 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|better to build the kernel-headers as well, so afterward other kernel-modules can
be built without whole kernel tree (e.g. drbd -> drbd0.7-module-source)}}

See also : "make-kpkg --targets"

==== Compiling ====

Compile your kernel (as user root, or you need the --rootcmd!)
# 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

==== Installing ====
Install the kernel and update initramfs:

# dpkg -i ../linux-image-2.6.18-1-openvz_1_i386.deb
# update-initramfs -c -k 2.6.18-1-openvz

{{Note|update-initramfs is done, when make-kpkg is use with --initrd option}}

{{Note|update-grub can be configured by /etc/kernel-img.conf}}

==== Bootloader ====

Update the bootloader (if not done before)

GRUB :

# /usr/sbin/update-grub

{{Note|since the Debian Etch release the location of update-grub is moved from /sbin/update-grub to /usr/sbin/update-grub}}

== Install the toolset ==

You need the toolset for managing OpenVZ Virtual Environments (VE)

<pre>
# apt-get install vzctl vzquota vzdump vzctl-ostmpl-debian
</pre>

= modify needed settings =

If you want network access for the virtual server then you need to enable IP forwarding.

An old (before Etch) Debian Way: set "ip_forward" to yes in /etc/network/option.

# editor /etc/network/options

The new (from Etch) standard way is to use sysctl for this (see below).

In some cases you may need to enable proxy_arp for the network devices that you want your virtual hosts to be accessible on.
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>
[...]
# 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=100
pre-down sysctl -w net.ipv4.conf.%DEV%.proxy_arp=0
[...]
</pre>

or use the /etc/network/if-up/ and /etc/network/if-down.d/ directories.

<pre>
INFO: # man 5 interfaces (to read more about debian's network interface configuration for ifup and ifdown)
INFO: It is recommanded to add the magic-sysrq key, to your /etc/sysctl.conf
</pre>

a (plain) OpenVZ Linux Way:

Add settings to "/etc/sysctl.conf"

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

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

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

# reboot

That's all!

Now it's time to create a OS Template or download another precreated OS-Template.

INFO: Suggestions: Setup your default OS Template in /etc/vz/vz.conf

[[Category: HOWTO]]
[[Category: Installation]]

Package managers

2007-11-14T21:08:09Z

Curx: add debian cmds for dependence

Ubuntu Gutsy template creation

2007-11-14T20:49:28Z

Curx: upgrade to an easier install process with chroot

Ubuntu Gutsy template creation

2007-11-14T19:53:28Z

Curx: /* Clean packages */

Ubuntu Gutsy template creation

2007-11-14T19:52:54Z

Curx: /* Clean packages */ add hostname settings and resolv.conf

Ubuntu Gutsy template creation

2007-11-14T19:48:48Z

Curx: /* Remove unneeded packages */ add ntpdate for purging

Installation on Debian/old

2007-09-27T17:52:59Z

Curx:

= Sarge-Dapper (OldStable) =
The OpenVZ packages at http://debian.systs.org/ aimed to install OpenVZ in a easy way, some tasks are even completed during the install process!

== edit apt source settings ==
Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/debian sarge openvz
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

== precompiled kernel images at debian.systs.org (dso) ==
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 deb.
If there is more than 4 Gb of RAM available, use the kernel-enterprise deb.
Otherwise, use the plain kernel deb (kernel).

{| class="wikitable"
|+'''Kernel flavors list'''
! Kernel type !! Description !! Hardware !! Use case
|-
! -
| 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-image: i368 and amd64
<pre>
ovzkernel-2.6.9
ovzkernel-2.6.9-smp
</pre>

kernel-image: i386 only:
<pre>
ovzkernel-2.6.9-enterprise
ovzkernel-2.6.9-entnosplit
</pre>

OpenVZ tool(s) for i386 and amd64
<pre>
vzctl
vzquota
vzprocps
vzdump
</pre>

template(s) for i368 and amd64 : Debian 3.1 Minimal
<pre>
vzctl-ostmpl-debian
</pre>

== installing the kernel-images, toolset and debian-os-template ==
Example: install the stable OpenVZ kernel, tools and Debian OS Template

# aptitude install ovzkernel-2.6.9 vzctl vzquota vzdump vzctl-ostmpl-debian

If you are using GRUB, maybe you need to update the /boot/grub/menu.lst file
(can be configured at /etc/kernel-img.conf):

# /sbin/grub-update

Reboot in your new Debian Sarge OpenVZ System

# reboot

That's all :-)

Now it's time to setup your VEs with the minimal Debian-3.1 Template, create new one or download another precreated OS-Template.

= Etch (Stable) =
OpenVZ is now a part of Debian Etch repository. The packages are 'vzctl' and 'vzquota'.

== install the kernel-image ==

=== precompiled kernel images at download.openvz.org ===

A Debian OpenVZ kernel repository is online, for direct access http://download.openvz.org/kernel/debian/etch/

add to your "/etc/apt/sources.list"
<pre>
deb http://download.openvz.org/debian etch main
</pre>

Update package lists
<pre>
# apt-get update
</pre>

List downloadable OpenVZ linux-images
<pre>
# apt-cache search linux-image-2.6.18-openvz
</pre>

Install a kernel
<pre>
# apt-get install <linux-image>
</pre>

=== precompiled kernel images at debian.systs.org ===

Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ etch openvz
</pre>

Add the signing key of debian.systs.org (dso) apt-keyring, (need root permissions)
<pre>
# wget http://debian.systs.org/dso_archiv_signing_key.asc -q -O - | apt-key add -
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

Choose a linux image (version 028stab039.1) :
<pre>
ovzkernel-2.6.18 (i386 and amd64)
ovzkernel-2.6.18-smp (i386 and amd64)
ovzkernel-2.6.18-enterprise only (i386)
</pre>

# apt-get install <linux-image>

=== or build your own kernel-image (debian way) ===

To install the kernel-source and the OpenVZ kernel patch, run:
<pre>
# apt-get install kernel-package linux-source-2.6.18 kernel-patch-openvz libncurses5-dev
</pre>

Unpack the kernel source:
<pre>
# cd /usr/src
# tar xjf linux-source-2.6.18.tar.bz2
# cd linux-source-2.6.18
</pre>

You need a kernel config.
You can use the config of the debian-kernel:
<pre>
# cp /boot/config-2.6.18-5-686 .config
</pre>

Or get a 2.6.18 kernel config from http://download.openvz.org/kernel/devel/current/configs/
<pre>
# wget http://download.openvz.org/kernel/devel/current/configs/kernel-2.6.18-028test010-i686.config.ovz -O .config
</pre>

Now you can apply the openvz kernel patch and modify your kernel-config:
<pre>
# ../kernel-patches/all/apply/openvz
# make menuconfig
</pre>

You need the following OpenVZ kernel config settings:
<pre>
(taken from OpenVZ Kernel 2.6.18-028test010.1 on 686)

Filesystem
\_ [*] Second extended fs support (CONFIG_EXT2_FS)
\_ [*] Ext3 journalling file system support (CONFIG_EXT3_FS)
\_ [M] 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)

Security
\->[ ] Enable different security models

OpenVZ ... (what else :-)
\_[*] 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)
\_ [*] 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>

INFO: Better to build the kernel-headers as well, so afterward other kernel-modules can
be built without whole kernel tree (e.g. drbd -> drbd0.7-module-source)
See also : "make-kpkg --targets"

Compile your Kernel (as user root, or you need the --rootcmd!)
<pre>
# 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
</pre>

Install the kernel and update initramfs:
<pre>
# dpkg -i ../linux-image-2.6.18-1-openvz_1_i386.deb
# update-initramfs -c -k 2.6.18-1-openvz
</pre>

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

Update the bootloader (when not done above)

GRUB :

# /usr/sbin/update-grub

INFO: since the Debian ETCH-release the location of update-grub is moved from /sbin/update-grub to /usr/sbin/update-grub !

== Install the toolset ==

You need the toolset for managing OpenVZ Virtual Environments (VE)

<pre>
# apt-get install vzctl vzquota
</pre>

= modify needed settings =

If you want network access for the virtual server then you need to enable IP forwarding.

An old (before Etch) Debian Way: set "ip_forward" to yes in /etc/network/option.

# editor /etc/network/options

The new (from Etch) standard way is to use sysctl for this (see below).

In some cases you may need to enable proxy_arp for the network devices that you want your virtual hosts to be accessible on.
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>
[...]
# 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=100
pre-down sysctl -w net.ipv4.conf.%DEV%.proxy_arp=0
[...]
</pre>

or use the /etc/network/if-up/ and /etc/network/if-down.d/ directories.

<pre>
INFO: # man 5 interfaces (to read more about debian's network interface configuration for ifup and ifdown)
INFO: It is recommanded to add the magic-sysrq key, to your /etc/sysctl.conf
</pre>

a (plain) OpenVZ Linux Way:

Add settings to "/etc/sysctl.conf"

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

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

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

# reboot

That's all!

Now it's time to create a OS Template or download another precreated OS-Template.

INFO: Suggestions: Setup your default OS Template in /etc/vz/vz.conf

[[Category: HOWTO]]
[[Category: Installation]]

Talk:Monitoring openvz resources using nagios and snmp

2007-09-27T17:51:25Z

Curx:

Very cool, thanks for the nagios plugin!

-mike

Is there a nagios script to do the same monitoring without snmp? Seems like an unnecessary additional service to me.

--
degradas

Remove the relevant snmp entries, and use the script with nagios-nrpe or with the nagios ssh plugin ...

--
Thorsten "curx" Schifferdecker

Talk:Monitoring openvz resources using nagios and snmp

2007-09-27T17:50:58Z

Curx:

Installation on Debian/old

2007-06-14T13:35:30Z

Curx: update version dso linux-image to 028stab035.1 and remove double entry about self compiling a kernel (debian way)

= Sarge-Dapper (OldStable) =
The OpenVZ packages at http://debian.systs.org/ aimed to install OpenVZ in a easy way, some tasks are even completed during the install process!

== edit apt source settings ==
Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ sarge openvz
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

== precompiled kernel images at debian.systs.org (dso) ==
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 deb.
If there is more than 4 Gb of RAM available, use the kernel-enterprise deb.
Otherwise, use the plain kernel deb (kernel).

{| class="wikitable"
|+'''Kernel flavors list'''
! Kernel type !! Description !! Hardware !! Use case
|-
! -
| 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-image: i368 and amd64
<pre>
ovzkernel-2.6.9
ovzkernel-2.6.9-smp
</pre>

kernel-image: i386 only:
<pre>
ovzkernel-2.6.9-enterprise
ovzkernel-2.6.9-entnosplit
</pre>

OpenVZ tool(s) for i386 and amd64
<pre>
vzctl
vzquota
vzprocps
vzdump
</pre>

template(s) for i368 and amd64 : Debian 3.1 Minimal
<pre>
vzctl-ostmpl-debian
</pre>

== installing the kernel-images, toolset and debian-os-template ==
Example: install the stable OpenVZ kernel, tools and Debian OS Template

# aptitude install ovzkernel-2.6.9 vzctl vzquota vzdump vzctl-ostmpl-debian

Maybe you need to update your "linux-loader" (can be configured at /etc/kernel-img.conf)

for the "GRUB":

# /sbin/grub-update

Reboot in your new Debian Stable OpenVZ System

# reboot

That's all :-)

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.

= Etch (Stable) =
OpenVZ is now a part of Debian Etch repository.

== install the kernel-image ==

=== precompiled kernel images at download.openvz.org ===

a Debian OpenVZ kernel repository is online, for direct access http://download.openvz.org/kernel/debian/etch/

add to your "/etc/apt/sources.list"
<pre>
deb http://download.openvz.org/debian etch main
</pre>

update package lists
<pre>
# apt-get update
</pre>

list downloadable OpenVZ linux-images
<pre>
# apt-cache search linux-image-2.6.18-openvz
</pre>

install a kernel
<pre>
# apt-get install <linux-image>
</pre>

=== precompiled kernel images at debian.systs.org ===

Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ etch openvz
</pre>

Add the signing key of debian.systs.org (dso) apt-keyring, (need root permissions)
<pre>
# wget http://debian.systs.org/dso_archiv_signing_key.asc -q -O - | apt-key add -
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

linux-image (version 028stab035.1) :
<pre>
ovzkernel-2.6.18 (i386 and amd64)
ovzkernel-2.6.18-smp (i386 and amd64)
ovzkernel-2.6.18-enterprise only (i386)
</pre>

# apt-get install <linux-image>

=== or build your own kernel-image (debian way) ===

To install the kernel-source and the OpenVZ kernel patch, run:
<pre>
# apt-get install kernel-package linux-source-2.6.18 kernel-patch-openvz libncurses5-dev
</pre>

Unpack the kernel-source:
<pre>
# cd /usr/src
# tar xjf linux-source-2.6.18.tar.bz2
# cd linux-source-2.6.18
</pre>

You need a kernel config.
You can use the config of the debian-kernel:
<pre>
# cp /boot/config-2.6.18-4-686 .config
</pre>

Or get a 2.6.18 kernel config from http://download.openvz.org/kernel/devel/current/configs/
<pre>
# wget http://download.openvz.org/kernel/devel/current/configs/kernel-2.6.18-028test010-i686.config.ovz -O .config
</pre>

Now you can apply openvz kernel patch and modify your kernel-config:
<pre>
# ../kernel-patches/all/apply/openvz
# make menuconfig
</pre>

You need following OpenVZ kernel config settings:
<pre>
(taken from a OpenVZ Kernel 2.6.18-028test010.1 on 686)

Filesystem
\_ [*] Second extended fs support (CONFIG_EXT2_FS)
\_ [*] Ext3 journalling file system support (CONFIG_EXT3_FS)
\_ [M] 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)

Security
\->[ ] Enable different security models

OpenVZ ... (what else :-)
\_[*] 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)
\_ [*] 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>

<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 :
# make-kpkg --targets
</pre>

Compile your Kernel (as user root, or you need the --rootcmd!)
<pre>
# 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
</pre>

Install the kernel and update initramfs:
<pre>
# dpkg -i ../linux-image-2.6.18-1-openvz_1_i386.deb
# update-initramfs -c -k 2.6.18-1-openvz
</pre>

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

Update the bootloader (when not done above)

GRUB :

# /usr/sbin/update-grub

INFO: since the Debian ETCH-release the location of update-grub is moved from /sbin/update-grub to /usr/sbin/update-grub !

== install the toolset ==

You need the toolset for manage-ing OpenVZ Virtual Enviromennt (VE)

<pre>
# apt-get install vzctl vzquota
</pre>

= modify needed settings =

If you want network access for the virtual server then you need to enable IP forwarding.

An old (before Etch) Debian Way: set "ip_forward" to yes in /etc/network/option.

# editor /etc/network/options

The new (from Etch) standard way is to use sysctl for this (see below).

In some cases you may need to enable proxy_arp for the network devices that you want your virtual hosts to be accessible on.
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>
[...]
# 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=100
pre-down sysctl -w net.ipv4.conf.%DEV%.proxy_arp=0
[...]
</pre>

or use the /etc/network/if-up/ and /etc/network/if-down.d/ directories.

<pre>
INFO: # man 5 interfaces (to read more about debian's network interface configuration for ifup and ifdown)
INFO: It is recommanded to add the magic-sysrq key, to your /etc/sysctl.conf
</pre>

a (plain) OpenVZ Linux Way:

Add settings to "/etc/sysctl.conf"

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

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

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

# reboot

That's all!

Now it's time to create a OS Template or download another precreated OS-Template.

INFO: Suggestions: Setup your default OS Template in /etc/vz/vz.conf

[[Category: HOWTO]]
[[Category: Installation]]

Installation on Debian/old

2007-05-31T14:20:44Z

Curx: update dso kernel images to 028stab033.1

= Sarge-Dapper (OldStable) =
The OpenVZ packages at http://debian.systs.org/ aimed to install OpenVZ in a easy way, some task are done on install process!

== edit apt source settings ==
Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ sarge openvz
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

== precompiled kernel images at debian.systs.org (dso) ==
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 deb.
If there is more than 4 Gb of RAM available, use the kernel-enterprise deb.
Otherwise, use the plain kernel deb (kernel).

{| class="wikitable"
|+'''Kernel flavors list'''
! Kernel type !! Description !! Hardware !! Use case
|-
! -
| 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-image: i368 and amd64
<pre>
ovzkernel-2.6.9
ovzkernel-2.6.9-smp
</pre>

kernel-image: i386 only:
<pre>
ovzkernel-2.6.9-enterprise
ovzkernel-2.6.9-entnosplit
</pre>

OpenVZ tool(s) for i386 and amd64
<pre>
vzctl
vzquota
vzprocps
vzdump
</pre>

template(s) for i368 and amd64 : Debian 3.1 Minimal
<pre>
vzctl-ostmpl-debian
</pre>

== installing the kernel-images, toolset and debian-os-template ==
Example: install the stable OpenVZ kernel, tools and Debian OS Template

# aptitude install ovzkernel-2.6.9 vzctl vzquota vzdump vzctl-ostmpl-debian

Maybe you need to update your "linux-loader" (can be configured at /etc/kernel-img.conf)

for the "GRUB":

# /sbin/grub-update

Reboot in your new Debian Stable OpenVZ System

# reboot

That's all :-)

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.

= Etch (Stable) =
OpenVZ is now a part of Debian Etch repository.

== install the kernel-image ==

=== precompiled kernel images at download.openvz.org ===

a Debian OpenVZ kernel repository is online, for direct access http://download.openvz.org/kernel/debian/etch/

add to your "/etc/apt/sources.list"
<pre>
deb http://download.openvz.org/debian etch main
</pre>

update package lists
<pre>
# apt-get update
</pre>

list downloadable OpenVZ linux-images
<pre>
# apt-cache search linux-image-2.6.18-openvz
</pre>

install a kernel
<pre>
# apt-get install <linux-image>
</pre>

=== using the OpenVZ kernel-patch from Debian ===

install the kernel-patch, kernel-source and the vz-tools:
<pre>
# apt-get install linux-source kernel-patch-openvz vzctl vzquota
</pre>

unpack the kernel:
<pre>
# cd /usr/src
# tar xjf linux-source-2.6.18.tar.bz2
</pre>

copy the config of you "normal" kernel:
<pre>
# cd linux-source-2.6.18
# cp /boot/config
# cp /boot/config-2.6.18-4-686 .config
</pre>

build the kernel packages:
<pre>
# make-kpkg --append_to_version -1-openvz --added_patches=openvz --revision=1 buildpackage --initrd
</pre>

install the packages:
<pre>
# dpkg -i *.deb
</pre>

Now you can reboot into the new kernel, ejoy.

=== precompiled kernel images at debian.systs.org ===

Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ etch openvz
</pre>

Add the signing key of debian.systs.org (dso) apt-keyring, (need root permissions)
<pre>
# wget http://debian.systs.org/dso_archiv_signing_key.asc -q -O - | apt-key add -
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

linux-image (version 028stab033.1):
<pre>
ovzkernel-2.6.18 (i386 and amd64)
ovzkernel-2.6.18-smp (i386 and amd64)
ovzkernel-2.6.18-enterprise only (i386)
</pre>

# apt-get install <linux-image>

=== or build your own kernel-image (debian way) ===

To install the kernel-source and the OpenVZ kernel patch, run:
<pre>
# apt-get install kernel-package linux-source-2.6.18 kernel-patch-openvz libncurses5-dev
</pre>

Unpack the kernel-source:
<pre>
# cd /usr/src
# tar xjf linux-source-2.6.18.tar.bz2
# cd linux-source-2.6.18
</pre>

You need a kernel config.
You can use the config of the debian-kernel:
<pre>
# cp /boot/config-2.6.18-3-686 .config
</pre>

Or get a 2.6.18 kernel config from http://download.openvz.org/kernel/devel/current/configs/
<pre>
# wget http://download.openvz.org/kernel/devel/current/configs/kernel-2.6.18-028test010-i686.config.ovz -O .config
</pre>

Now you can apply openvz kernel patch and modify your kernel-config:
<pre>
# ../kernel-patches/all/apply/openvz
# make menuconfig
</pre>

You need following OpenVZ kernel config settings:
<pre>
(taken from a OpenVZ Kernel 2.6.18-028test010.1 on 686)

Filesystem
\_ [*] Second extended fs support (CONFIG_EXT2_FS)
\_ [*] Ext3 journalling file system support (CONFIG_EXT3_FS)
\_ [M] 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)

Security
\->[ ] Enable different security models

OpenVZ ... (what else :-)
\_[*] 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)
\_ [*] 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>

<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 :
# make-kpkg --targets
</pre>

Compile your Kernel (as user root, or you need the --rootcmd!)
<pre>
# 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
</pre>

Install the kernel and update initramfs:
<pre>
# dpkg -i ../linux-image-2.6.18-1-openvz_1_i386.deb
# update-initramfs -c -k 2.6.18-1-openvz
</pre>

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

Update the bootloader (when not done above)

GRUB :

# /usr/sbin/update-grub

INFO: since the Debian ETCH-release the location of update-grub is moved from /sbin/update-grub to /usr/sbin/update-grub !

== install the toolset ==

You need the toolset for manage-ing OpenVZ Virtual Enviromennt (VE)

<pre>
# apt-get install vzctl vzquota
</pre>

= modify needed settings =

If you want network access for the virtual server then you need to enable IP forwarding.

An old (before Etch) Debian Way: set "ip_forward" to yes in /etc/network/option.

# editor /etc/network/options

The new (from Etch) standard way is to use sysctl for this (see below).

In some cases you may need to enable proxy_arp for the network devices that you want your virtual hosts to be accessible on.
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>
[...]
# 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=100
pre-down sysctl -w net.ipv4.conf.%DEV%.proxy_arp=0
[...]
</pre>

or use the /etc/network/if-up/ and /etc/network/if-down.d/ directories.

<pre>
INFO: # man 5 interfaces (to read more about debian's network interface configuration for ifup and ifdown)
INFO: It is recommanded to add the magic-sysrq key, to your /etc/sysctl.conf
</pre>

a (plain) OpenVZ Linux Way:

Add settings to "/etc/sysctl.conf"

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

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

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

# reboot

That's all!

Now it's time to create a OS Template or download another precreated OS-Template.

INFO: Suggestions: Setup your default OS Template in /etc/vz/vz.conf

[[Category: HOWTO]]
[[Category: Installation]]

Talk:Installation on Debian/old

2007-05-30T01:35:34Z

Curx: network/interface settings

info about needed modules in kernel-config

info about "Yet Another mkInitRD" yaid tools creating initrd-files

== ip_forward setup ==

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.
# editor /etc/network/options

: /etc/network/options is deprecated. ip_forward may be enabled in /etc/sysctl.conf by adding the line "net.ipv4.ip_forward=1"

== Debian Etch has been released ==

Sarge is no longer stable and has been replaced by Etch. This document needs to be updated for Etch

* References to Sarge need to be updated to use Etch instead.
* Lenny is the new Debian testing. If you wish to continue to have a testing section listed, update it for Lenny. Otherwise remove the testing section.
* Use the official Debian mirrors to get the OpenVZ packages.

--[[User:Dusty|Dusty]] 19:26, 9 April 2007 (EDT)

== Interface settings still give me an error. ==

I did an update on:

[...]
# 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=100'''
'''pre-down sysctl -w net.ipv4.conf.%DEV%.proxy_arp=0'''
[...]

since the debian docs (/usr/share/doc/vzctl/README.Debian) told me this were the right values, but now I get on starting/stopping a VE:
vps-net_del WARNING: Function proxy_arp for eth0 is set to 0. Enable with 'sysctl -w net.ipv4.conf.eth0.proxy_arp=1'. See /usr/share/doc/vzctl/README.Debian.

The previous settings (see history) also gave me errors:
[...]
# 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'''
'''pre-down sysctl -w net.ipv4.conf.%DEV%.proxy_arp=1'''
[...]

Anybody got a clue what the right values are?

--[[User:Vipz|Vipz]] 16:27, 29 May 2007 (EDT)

See http://wiki.openvz.org/w/index.php?title=Installation_on_Debian&oldid=2629, forum entry http://forum.openvz.org/index.php?t=msg&goto=10089 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=387762

@vips: btw why have you change the settings to the buggy version of /usr/share/doc/vzctl/README.debian ?

So try a up sysctl -w net.ipv4.conf.%DEV%.proxy_arp=1, not 100!

--[[User:Curx|Curx]] 21:35, 29 May 2007 (EDT)

Installation on Debian/old

2007-05-10T05:48:05Z

Curx: /* precompiled kernel images at debian.systs.org */ update 028stab031.1

= Sarge-Dapper (OldStable) =
The OpenVZ packages at http://debian.systs.org/ aimed to install OpenVZ in a easy way, some task are done on install process!

== edit apt source settings ==
Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ sarge openvz
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

== precompiled kernel images at debian.systs.org (dso) ==
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 deb.
If there is more than 4 Gb of RAM available, use the kernel-enterprise deb.
Otherwise, use the plain kernel deb (kernel).

{| class="wikitable"
|+'''Kernel flavors list'''
! Kernel type !! Description !! Hardware !! Use case
|-
! -
| 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-image: i368 and amd64
<pre>
ovzkernel-2.6.9
ovzkernel-2.6.9-smp
</pre>

kernel-image: i386 only:
<pre>
ovzkernel-2.6.9-enterprise
ovzkernel-2.6.9-entnosplit
</pre>

OpenVZ tool(s) for i386 and amd64
<pre>
vzctl
vzquota
vzprocps
vzdump
</pre>

template(s) for i368 and amd64 : Debian 3.1 Minimal
<pre>
vzctl-ostmpl-debian
</pre>

== installing the kernel-images, toolset and debian-os-template ==
Example: install the stable OpenVZ kernel, tools and Debian OS Template

# aptitude install ovzkernel-2.6.9 vzctl vzquota vzdump vzctl-ostmpl-debian

Maybe you need to update your "linux-loader" (can be configured at /etc/kernel-img.conf)

for the "GRUB":

# /sbin/grub-update

Reboot in your new Debian Stable OpenVZ System

# reboot

That's all :-)

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.

= Etch (Stable) =
OpenVZ is now a part of Debian Etch repository.

== install the kernel-image ==

=== precompiled kernel images at download.openvz.org ===

a Debian OpenVZ kernel repository is online, for direct access http://download.openvz.org/kernel/debian/etch/

add to your "/etc/apt/sources.list"
<pre>
deb http://download.openvz.org/debian etch main
</pre>

update package lists
<pre>
# apt-get update
</pre>

list downloadable OpenVZ linux-images
<pre>
# apt-cache search linux-image-2.6.18-openvz
</pre>

install a kernel
<pre>
# apt-get install <linux-image>
</pre>

=== precompiled kernel images at debian.systs.org ===

Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ etch openvz
</pre>

Add the signing key of debian.systs.org (dso) apt-keyring, (need root permissions)
<pre>
# wget http://debian.systs.org/dso_archiv_signing_key.asc -q -O - | apt-key add -
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

linux-image (version 028stab031.1):
<pre>
ovzkernel-2.6.18 (i386 and amd64)
ovzkernel-2.6.18-smp (i386 and amd64)
ovzkernel-2.6.18-enterprise only (i386)
</pre>

# apt-get install <linux-image>

=== or build your own kernel-image (debian way) ===

To install the kernel-source and the OpenVZ kernel patch, run:
<pre>
# apt-get install kernel-package linux-source-2.6.18 kernel-patch-openvz libncurses5-dev
</pre>

Unpack the kernel-source:
<pre>
# cd /usr/src
# tar xjf linux-source-2.6.18.tar.bz2
# cd linux-source-2.6.18
</pre>

You need a kernel config.
You can use the config of the debian-kernel:
<pre>
# cp /boot/config-2.6.18-3-686 .config
</pre>

Or get a 2.6.18 kernel config from http://download.openvz.org/kernel/devel/current/configs/
<pre>
# wget http://download.openvz.org/kernel/devel/current/configs/kernel-2.6.18-028test010-i686.config.ovz -O .config
</pre>

Now you can apply openvz kernel patch and modify your kernel-config:
<pre>
# ../kernel-patches/all/apply/openvz
# make menuconfig
</pre>

You need following OpenVZ kernel config settings:
<pre>
(taken from a OpenVZ Kernel 2.6.18-028test010.1 on 686)

Filesystem
\_ [*] 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)

Security
\->[ ] Enable different security models

OpenVZ ... (what else :-)
\_[*] 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)
\_ [*] 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>

<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 :
# make-kpkg --targets
</pre>

Compile your Kernel (as user root, or you need the --rootcmd!)
<pre>
# 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
</pre>

Install the kernel and update initramfs:
<pre>
# dpkg -i ../linux-image-2.6.18-1-openvz_1_i386.deb
# update-initramfs -c -k 2.6.18-1-openvz
</pre>

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

Update the bootloader (when not done above)

GRUB :

# /usr/sbin/update-grub

INFO: since the Debian ETCH-release the location of update-grub is moved from /sbin/update-grub to /usr/sbin/update-grub !

== install the toolset ==

You need the toolset for manage-ing OpenVZ Virtual Enviromennt (VE)

<pre>
# apt-get install vzctl vzquota
</pre>

= modify needed settings =

If you want network access for the virtual server then you need to enable IP forwarding.

An old (before Etch) Debian Way: set "ip_forward" to yes in /etc/network/option.

# editor /etc/network/options

The new (from Etch) standard way is to use sysctl for this (see below).

In some cases you may need to enable proxy_arp for the network devices that you want your virtual hosts to be accessible on.
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>
[...]
# 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
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.

<pre>
INFO: # man 5 interfaces (to read more about debian's network interface configuration for ifup and ifdown)
INFO: It is recommanded to add the magic-sysrq key, to your /etc/sysctl.conf
</pre>

a (plain) OpenVZ Linux Way:

Add settings to "/etc/sysctl.conf"

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

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

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

# reboot

That's all!

Now it's time to create a OS Template or download another precreated OS-Template.

INFO: Suggestions: Setup your default OS Template in /etc/vz/vz.conf

[[Category: HOWTO]]
[[Category: Installation]]

Installation on Debian/old

2007-05-10T05:31:27Z

Curx: /* precompiled kernel images at download.openvz.org */ a debian repro is online, add info

= Sarge-Dapper (OldStable) =
The OpenVZ packages at http://debian.systs.org/ aimed to install OpenVZ in a easy way, some task are done on install process!

== edit apt source settings ==
Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ sarge openvz
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

== precompiled kernel images at debian.systs.org (dso) ==
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 deb.
If there is more than 4 Gb of RAM available, use the kernel-enterprise deb.
Otherwise, use the plain kernel deb (kernel).

{| class="wikitable"
|+'''Kernel flavors list'''
! Kernel type !! Description !! Hardware !! Use case
|-
! -
| 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-image: i368 and amd64
<pre>
ovzkernel-2.6.9
ovzkernel-2.6.9-smp
</pre>

kernel-image: i386 only:
<pre>
ovzkernel-2.6.9-enterprise
ovzkernel-2.6.9-entnosplit
</pre>

OpenVZ tool(s) for i386 and amd64
<pre>
vzctl
vzquota
vzprocps
vzdump
</pre>

template(s) for i368 and amd64 : Debian 3.1 Minimal
<pre>
vzctl-ostmpl-debian
</pre>

== installing the kernel-images, toolset and debian-os-template ==
Example: install the stable OpenVZ kernel, tools and Debian OS Template

# aptitude install ovzkernel-2.6.9 vzctl vzquota vzdump vzctl-ostmpl-debian

Maybe you need to update your "linux-loader" (can be configured at /etc/kernel-img.conf)

for the "GRUB":

# /sbin/grub-update

Reboot in your new Debian Stable OpenVZ System

# reboot

That's all :-)

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.

= Etch (Stable) =
OpenVZ is now a part of Debian Etch repository.

== install the kernel-image ==

=== precompiled kernel images at download.openvz.org ===

a Debian OpenVZ kernel repository is online, for direct access http://download.openvz.org/kernel/debian/etch/

add to your "/etc/apt/sources.list"
<pre>
deb http://download.openvz.org/debian etch main
</pre>

update package lists
<pre>
# apt-get update
</pre>

list downloadable OpenVZ linux-images
<pre>
# apt-cache search linux-image-2.6.18-openvz
</pre>

install a kernel
<pre>
# apt-get install <linux-image>
</pre>

=== precompiled kernel images at debian.systs.org ===

Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ etch openvz
</pre>

Add the signing key of debian.systs.org (dso) apt-keyring, (need root permissions)
<pre>
# wget http://debian.systs.org/dso_archiv_signing_key.asc -q -O - | apt-key add -
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

linux-image (version 028stab023.1):
<pre>
ovzkernel-2.6.18 (i386 and amd64)
ovzkernel-2.6.18-smp (i386 and amd64)
ovzkernel-2.6.18-enterprise only (i386)
</pre>

# apt-get install <linux-image>

=== or build your own kernel-image (debian way) ===

To install the kernel-source and the OpenVZ kernel patch, run:
<pre>
# apt-get install kernel-package linux-source-2.6.18 kernel-patch-openvz libncurses5-dev
</pre>

Unpack the kernel-source:
<pre>
# cd /usr/src
# tar xjf linux-source-2.6.18.tar.bz2
# cd linux-source-2.6.18
</pre>

You need a kernel config.
You can use the config of the debian-kernel:
<pre>
# cp /boot/config-2.6.18-3-686 .config
</pre>

Or get a 2.6.18 kernel config from http://download.openvz.org/kernel/devel/current/configs/
<pre>
# wget http://download.openvz.org/kernel/devel/current/configs/kernel-2.6.18-028test010-i686.config.ovz -O .config
</pre>

Now you can apply openvz kernel patch and modify your kernel-config:
<pre>
# ../kernel-patches/all/apply/openvz
# make menuconfig
</pre>

You need following OpenVZ kernel config settings:
<pre>
(taken from a OpenVZ Kernel 2.6.18-028test010.1 on 686)

Filesystem
\_ [*] 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)

Security
\->[ ] Enable different security models

OpenVZ ... (what else :-)
\_[*] 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)
\_ [*] 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>

<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 :
# make-kpkg --targets
</pre>

Compile your Kernel (as user root, or you need the --rootcmd!)
<pre>
# 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
</pre>

Install the kernel and update initramfs:
<pre>
# dpkg -i ../linux-image-2.6.18-1-openvz_1_i386.deb
# update-initramfs -c -k 2.6.18-1-openvz
</pre>

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

Update the bootloader (when not done above)

GRUB :

# /usr/sbin/update-grub

INFO: since the Debian ETCH-release the location of update-grub is moved from /sbin/update-grub to /usr/sbin/update-grub !

== install the toolset ==

You need the toolset for manage-ing OpenVZ Virtual Enviromennt (VE)

<pre>
# apt-get install vzctl vzquota
</pre>

= modify needed settings =

If you want network access for the virtual server then you need to enable IP forwarding.

An old (before Etch) Debian Way: set "ip_forward" to yes in /etc/network/option.

# editor /etc/network/options

The new (from Etch) standard way is to use sysctl for this (see below).

In some cases you may need to enable proxy_arp for the network devices that you want your virtual hosts to be accessible on.
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>
[...]
# 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
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.

<pre>
INFO: # man 5 interfaces (to read more about debian's network interface configuration for ifup and ifdown)
INFO: It is recommanded to add the magic-sysrq key, to your /etc/sysctl.conf
</pre>

a (plain) OpenVZ Linux Way:

Add settings to "/etc/sysctl.conf"

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

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

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

# reboot

That's all!

Now it's time to create a OS Template or download another precreated OS-Template.

INFO: Suggestions: Setup your default OS Template in /etc/vz/vz.conf

[[Category: HOWTO]]
[[Category: Installation]]

Installation on Debian/old

2007-05-04T15:12:13Z

Curx: /* precompiled kernel images at debian.systs.org (dso) */ update, debian 4.0 is stable, 3.1 moved to dso-archive

= Sarge-Dapper (OldStable) =
The OpenVZ packages at http://debian.systs.org/ aimed to install OpenVZ in a easy way, some task are done on install process!

== edit apt source settings ==
Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ sarge openvz
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

== precompiled kernel images at debian.systs.org (dso) ==
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 deb.
If there is more than 4 Gb of RAM available, use the kernel-enterprise deb.
Otherwise, use the plain kernel deb (kernel).

{| class="wikitable"
|+'''Kernel flavors list'''
! Kernel type !! Description !! Hardware !! Use case
|-
! -
| 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-image: i368 and amd64
<pre>
ovzkernel-2.6.9
ovzkernel-2.6.9-smp
</pre>

kernel-image: i386 only:
<pre>
ovzkernel-2.6.9-enterprise
ovzkernel-2.6.9-entnosplit
</pre>

OpenVZ tool(s) for i386 and amd64
<pre>
vzctl
vzquota
vzprocps
vzdump
</pre>

template(s) for i368 and amd64 : Debian 3.1 Minimal
<pre>
vzctl-ostmpl-debian
</pre>

== installing the kernel-images, toolset and debian-os-template ==
Example: install the stable OpenVZ kernel, tools and Debian OS Template

# aptitude install ovzkernel-2.6.9 vzctl vzquota vzdump vzctl-ostmpl-debian

Maybe you need to update your "linux-loader" (can be configured at /etc/kernel-img.conf)

for the "GRUB":

# /sbin/grub-update

Reboot in your new Debian Stable OpenVZ System

# reboot

That's all :-)

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.

= Etch (Stable) =
OpenVZ is now a part of Debian Etch repository.

== install the kernel-image ==

=== precompiled kernel images at download.openvz.org ===
Can be found at http://download.openvz.org/kernel/debian/etch/

<pre>
List of precompiled kernel-images

linux-image-2.6.18-openvz-486_02_i386.deb
linux-image-2.6.18-openvz-686_02_i386.deb
linux-image-2.6.18-openvz-amd64_01_amd64.deb
linux-image-2.6.18-openvz-ia64_01_ia64.deb
linux-image-2.6.18-openvz-k7_02_i386.deb
linux-image-2.6.18-openvz-sparc64-smp_01_sparc.deb
linux-image-2.6.18-openvz-sparc64_01_sparc.deb
</pre>

Example: Installing an OpenVZ precompiled Debian Kernel-Image for an i686:

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

=== precompiled kernel images at debian.systs.org ===

Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ etch openvz
</pre>

Add the signing key of debian.systs.org (dso) apt-keyring, (need root permissions)
<pre>
# wget http://debian.systs.org/dso_archiv_signing_key.asc -q -O - | apt-key add -
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

linux-image (version 028stab023.1):
<pre>
ovzkernel-2.6.18 (i386 and amd64)
ovzkernel-2.6.18-smp (i386 and amd64)
ovzkernel-2.6.18-enterprise only (i386)
</pre>

# apt-get install <linux-image>

=== or build your own kernel-image (debian way) ===

To install the kernel-source and the OpenVZ kernel patch, run:
<pre>
# apt-get install kernel-package linux-source-2.6.18 kernel-patch-openvz libncurses5-dev
</pre>

Unpack the kernel-source:
<pre>
# cd /usr/src
# tar xjf linux-source-2.6.18.tar.bz2
# cd linux-source-2.6.18
</pre>

You need a kernel config.
You can use the config of the debian-kernel:
<pre>
# cp /boot/config-2.6.18-3-686 .config
</pre>

Or get a 2.6.18 kernel config from http://download.openvz.org/kernel/devel/current/configs/
<pre>
# wget http://download.openvz.org/kernel/devel/current/configs/kernel-2.6.18-028test010-i686.config.ovz -O .config
</pre>

Now you can apply openvz kernel patch and modify your kernel-config:
<pre>
# ../kernel-patches/all/apply/openvz
# make menuconfig
</pre>

You need following OpenVZ kernel config settings:
<pre>
(taken from a OpenVZ Kernel 2.6.18-028test010.1 on 686)

Filesystem
\_ [*] 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)

Security
\->[ ] Enable different security models

OpenVZ ... (what else :-)
\_[*] 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)
\_ [*] 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>

<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 :
# make-kpkg --targets
</pre>

Compile your Kernel (as user root, or you need the --rootcmd!)
<pre>
# 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
</pre>

Install the kernel and update initramfs:
<pre>
# dpkg -i ../linux-image-2.6.18-1-openvz_1_i386.deb
# update-initramfs -c -k 2.6.18-1-openvz
</pre>

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

Update the bootloader (when not done above)

GRUB :

# /usr/sbin/update-grub

INFO: since the Debian ETCH-release the location of update-grub is moved from /sbin/update-grub to /usr/sbin/update-grub !

== install the toolset ==

You need the toolset for manage-ing OpenVZ Virtual Enviromennt (VE)

<pre>
# apt-get install vzctl vzquota
</pre>

= modify needed settings =

If you want network access for the virtual server then you need to enable IP forwarding.

An old (before Etch) Debian Way: set "ip_forward" to yes in /etc/network/option.

# editor /etc/network/options

The new (from Etch) standard way is to use sysctl for this (see below).

In some cases you may need to enable proxy_arp for the network devices that you want your virtual hosts to be accessible on.
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>
[...]
# 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
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.

<pre>
INFO: # man 5 interfaces (to read more about debian's network interface configuration for ifup and ifdown)
INFO: It is recommanded to add the magic-sysrq key, to your /etc/sysctl.conf
</pre>

a (plain) OpenVZ Linux Way:

Add settings to "/etc/sysctl.conf"

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

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

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

# reboot

That's all!

Now it's time to create a OS Template or download another precreated OS-Template.

INFO: Suggestions: Setup your default OS Template in /etc/vz/vz.conf

[[Category: HOWTO]]
[[Category: Installation]]

Installation on Debian/old

2007-04-03T21:08:13Z

Curx: /* precompiled kernel images at debian.systs.org */ add info for apt-key

= Sarge-Dapper (Stable) =
The OpenVZ packages at http://debian.systs.org/ aimed to install OpenVZ in a easy way, some task are done on install process!

== edit apt source settings ==
Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ sarge openvz
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

== precompiled kernel images at debian.systs.org (dso) ==
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 deb.
If there is more than 4 Gb of RAM available, use the kernel-enterprise deb.
Otherwise, use the plain kernel deb (kernel).

{| class="wikitable"
|+'''Kernel flavors list'''
! Kernel type !! Description !! Hardware !! Use case
|-
! -
| 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-image: i368 and amd64
<pre>
ovzkernel-2.6.9
ovzkernel-2.6.9-enterprise
ovzkernel-2.6.9-entnosplit
ovzkernel-2.6.9-smp

ovzkernel-2.6.18
ovzkernel-2.6.18-enterprise
ovzkernel-2.6.18-smp
</pre>

i386 only:
<pre>
ovzkernel-2.6.18-enterprise
</pre>

OpenVZ tool(s) for i386 and amd64
<pre>
vzctl
vzquota
vzprocps
vzdump
</pre>

template(s) for i368 and amd64 : Debian 3.1 Minimal
<pre>
vzctl-ostmpl-debian
</pre>

== installing the kernel-images, toolset and debian-os-template ==
Example: install the stable OpenVZ kernel, tools and Debian OS Template

# aptitude install ovzkernel-2.6.9 vzctl vzquota vzdump vzctl-ostmpl-debian

Maybe you need to update your "linux-loader" (can be configured at /etc/kernel-img.conf)

for the "GRUB":

# /sbin/grub-update

Reboot in your new Debian Stable OpenVZ System

# reboot

That's all :-)

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.

= Etch (Testing) =
OpenVZ is now a part of Debian Etch (a.k.a. "testing") repository.

== install the kernel-image ==

=== precompiled kernel images at download.openvz.org ===
Can be found at http://download.openvz.org/kernel/debian/etch/

<pre>
List of precompiled kernel-images

linux-image-2.6.18-openvz-486_02_i386.deb
linux-image-2.6.18-openvz-686_02_i386.deb
linux-image-2.6.18-openvz-amd64_01_amd64.deb
linux-image-2.6.18-openvz-ia64_01_ia64.deb
linux-image-2.6.18-openvz-k7_02_i386.deb
linux-image-2.6.18-openvz-sparc64-smp_01_sparc.deb
linux-image-2.6.18-openvz-sparc64_01_sparc.deb
</pre>

Example: Installing an OpenVZ precompiled Debian Kernel-Image for an i686:

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

=== precompiled kernel images at debian.systs.org ===

Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ etch openvz
</pre>

Add the signing key of debian.systs.org (dso) apt-keyring, (need root permissions)
<pre>
# wget http://debian.systs.org/dso_archiv_signing_key.asc -q -O - | apt-key add -
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

linux-image (version 028stab023.1):
<pre>
ovzkernel-2.6.18 (i386 and amd64)
ovzkernel-2.6.18-smp (i386 and amd64)
ovzkernel-2.6.18-enterprise only (i386)
</pre>

# apt-get install <linux-image>

=== or build your own kernel-image (debian way) ===

To install the kernel-source and the OpenVZ kernel patch, run:
<pre>
# apt-get install kernel-package linux-source-2.6.18 kernel-patch-openvz libncurses5-dev
</pre>

Unpack the kernel-source:
<pre>
# cd /usr/src
# tar xjf linux-source-2.6.18.tar.bz2
# cd linux-source-2.6.18
</pre>

You need a kernel config.
You can use the config of the debian-kernel:
<pre>
# cp /boot/config-2.6.18-3-686 .config
</pre>

Or get a 2.6.18 kernel config from http://download.openvz.org/kernel/devel/current/configs/
<pre>
# wget http://download.openvz.org/kernel/devel/current/configs/kernel-2.6.18-028test010-i686.config.ovz -O .config
</pre>

Now you can apply openvz kernel patch and modify your kernel-config:
<pre>
# ../kernel-patches/all/apply/openvz
# make menuconfig
</pre>

You need following OpenVZ kernel config settings:
<pre>
(taken from a OpenVZ Kernel 2.6.18-028test010.1 on 686)

Filesystem
\_ [*] 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 :-)
\_[*] 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)
\_ [*] 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>

<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 :
# make-kpkg --targets
</pre>

Compile your Kernel (as user root, or you need the --rootcmd!)
<pre>
# 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
</pre>

Install the kernel and update initramfs:
<pre>
# dpkg -i ../linux-image-2.6.18-1-openvz_1_i386.deb
# update-initramfs -c -k 2.6.18-1-openvz
</pre>

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

Update the bootloader (when not done above)

GRUB :

# /usr/sbin/update-grub

INFO: since the Debian ETCH-release the location of update-grub is moved from /sbin/update-grub to /usr/sbin/update-grub !

== install the toolset ==

You need the toolset for manage-ing OpenVZ Virtual Enviromennt (VE)

<pre>
# apt-get install vzctl vzquota
</pre>

== modify needed settings ==

a Debian Way:

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.

# editor /etc/network/options

In some cases you may need to enable proxy_arp for the network devices that you want your virtual hosts to be accessible on.
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>
[...]
# 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
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.

<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 settings to "/etc/sysctl.conf"

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

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

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

# reboot

That's all!

Now it's time to create a OS Template or download another precreated OS-Template.

INFO: Suggestions: Setup your default OS Template in /etc/vz/vz.conf

[[Category: HOWTO]]
[[Category: Installation]]

Installation on Debian/old

2007-04-03T18:59:57Z

Curx: add info for etch dso kernel images

= Sarge-Dapper (Stable) =
The OpenVZ packages at http://debian.systs.org/ aimed to install OpenVZ in a easy way, some task are done on install process!

== edit apt source settings ==
Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ sarge openvz
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

== precompiled kernel images at debian.systs.org (dso) ==
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 deb.
If there is more than 4 Gb of RAM available, use the kernel-enterprise deb.
Otherwise, use the plain kernel deb (kernel).

{| class="wikitable"
|+'''Kernel flavors list'''
! Kernel type !! Description !! Hardware !! Use case
|-
! -
| 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-image: i368 and amd64
<pre>
ovzkernel-2.6.9
ovzkernel-2.6.9-enterprise
ovzkernel-2.6.9-entnosplit
ovzkernel-2.6.9-smp

ovzkernel-2.6.18
ovzkernel-2.6.18-enterprise
ovzkernel-2.6.18-smp
</pre>

i386 only:
<pre>
ovzkernel-2.6.18-enterprise
</pre>

OpenVZ tool(s) for i386 and amd64
<pre>
vzctl
vzquota
vzprocps
vzdump
</pre>

template(s) for i368 and amd64 : Debian 3.1 Minimal
<pre>
vzctl-ostmpl-debian
</pre>

== installing the kernel-images, toolset and debian-os-template ==
Example: install the stable OpenVZ kernel, tools and Debian OS Template

# aptitude install ovzkernel-2.6.9 vzctl vzquota vzdump vzctl-ostmpl-debian

Maybe you need to update your "linux-loader" (can be configured at /etc/kernel-img.conf)

for the "GRUB":

# /sbin/grub-update

Reboot in your new Debian Stable OpenVZ System

# reboot

That's all :-)

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.

= Etch (Testing) =
OpenVZ is now a part of Debian Etch (a.k.a. "testing") repository.

== install the kernel-image ==

=== precompiled kernel images at download.openvz.org ===
Can be found at http://download.openvz.org/kernel/debian/etch/

<pre>
List of precompiled kernel-images

linux-image-2.6.18-openvz-486_02_i386.deb
linux-image-2.6.18-openvz-686_02_i386.deb
linux-image-2.6.18-openvz-amd64_01_amd64.deb
linux-image-2.6.18-openvz-ia64_01_ia64.deb
linux-image-2.6.18-openvz-k7_02_i386.deb
linux-image-2.6.18-openvz-sparc64-smp_01_sparc.deb
linux-image-2.6.18-openvz-sparc64_01_sparc.deb
</pre>

Example: Installing an OpenVZ precompiled Debian Kernel-Image for an i686:

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

=== precompiled kernel images at debian.systs.org ===

Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ etch openvz
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

linux-image: OpenVZ version: 028stab023.1
<pre>
ovzkernel-2.6.18 (i386 and amd64)
ovzkernel-2.6.18-smp (i386 and amd64)
ovzkernel-2.6.18-enterprise only (i386)
</pre>

# apt-get install <linux-image>

=== or build your own kernel-image (debian way) ===

To install the kernel-source and the OpenVZ kernel patch, run:
<pre>
# apt-get install kernel-package linux-source-2.6.18 kernel-patch-openvz libncurses5-dev
</pre>

Unpack the kernel-source:
<pre>
# cd /usr/src
# tar xjf linux-source-2.6.18.tar.bz2
# cd linux-source-2.6.18
</pre>

You need a kernel config.
You can use the config of the debian-kernel:
<pre>
# cp /boot/config-2.6.18-3-686 .config
</pre>

Or get a 2.6.18 kernel config from http://download.openvz.org/kernel/devel/current/configs/
<pre>
# wget http://download.openvz.org/kernel/devel/current/configs/kernel-2.6.18-028test010-i686.config.ovz -O .config
</pre>

Now you can apply openvz kernel patch and modify your kernel-config:
<pre>
# ../kernel-patches/all/apply/openvz
# make menuconfig
</pre>

You need following OpenVZ kernel config settings:
<pre>
(taken from a OpenVZ Kernel 2.6.18-028test010.1 on 686)

Filesystem
\_ [*] 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 :-)
\_[*] 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)
\_ [*] 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>

<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 :
# make-kpkg --targets
</pre>

Compile your Kernel (as user root, or you need the --rootcmd!)
<pre>
# 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
</pre>

Install the kernel and update initramfs:
<pre>
# dpkg -i ../linux-image-2.6.18-1-openvz_1_i386.deb
# update-initramfs -c -k 2.6.18-1-openvz
</pre>

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

Update the bootloader (when not done above)

GRUB :

# /usr/sbin/update-grub

INFO: since the Debian ETCH-release the location of update-grub is moved from /sbin/update-grub to /usr/sbin/update-grub !

== install the toolset ==

You need the toolset for manage-ing OpenVZ Virtual Enviromennt (VE)

<pre>
# apt-get install vzctl vzquota
</pre>

== modify needed settings ==

a Debian Way:

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.

# editor /etc/network/options

In some cases you may need to enable proxy_arp for the network devices that you want your virtual hosts to be accessible on.
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>
[...]
# 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
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.

<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 settings to "/etc/sysctl.conf"

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

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

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

# reboot

That's all!

Now it's time to create a OS Template or download another precreated OS-Template.

INFO: Suggestions: Setup your default OS Template in /etc/vz/vz.conf

[[Category: HOWTO]]
[[Category: Installation]]

Backup of a running container with vzdump

2007-03-24T12:30:05Z

Curx: /* Download */ correct rpm and deb downloads

= Vzdump =
Vzdump is an utility to make consistent snapshots of running OpenVZ VEs. It basically creates a tar archive of the VE private area, which also includes the VE configuration files.

There are several ways to provide consistency:

- Stop the VE during backup (very long downtime)

- Use rsync and suspend/resume (minimal downtime)

- Use LVM2 (no downtime)

Vzdump stores the backup on the disk in a single file. This file should go to a tape backup for archiving.

== Download ==
Download vzdump rpm or deb packages from http://download.openvz.org/contrib/utils/vzdump/

For rpm based systems:
<pre>wget http://download.openvz.org/contrib/utils/vzdump/vzdump-0.3-1.noarch.rpm</pre>

For Debian based systems:
<pre>wget http://download.openvz.org/contrib/utils/vzdump/vzdump_0.3-1_all.deb</pre>

== Installation ==
For rpm based systems:
<pre>rpm -i vzdump-0.3-1.noarch.rpm</pre>

For Debian based systems:
<pre>dpkg -i vzdump_0.3-1_all.deb</pre>

== Synopsis ==

<pre>vzdump OPTIONS [--all â <VEID>]

--compress compress dump file (gzip)

--dumpdir DIR store resulting files in DIR

--xdelta create a differential backup using xdelta

--mailto EMAIL send notification mail to EMAIL

--stop stop/start VPS if running

--suspend suspend/resume VPS when running

--snapshot use LVM snapshot when running

--restore FILENAME restore FILENAME
</pre>

= Examples =
== Backup ==

Simply dump VE 777 - no snapshot, just archive the VE private area and configuration files to the default dump directory (usually /vz/dump/).

<pre>vzdump 777</pre>

Use rsync and suspend/resume to create a snapshot (minimal downtime).

<pre>vzdump --suspend 777</pre>

Backup all VEs and send notification mails to root.

<pre>vzdump --suspend --all --mailto root</pre>

Use LVM2 to create snapshots (no downtime).

<pre>vzdump --dumpdir /space/backup --snapshot 777</pre>

== Restore ==

Restore above backup to VE 600

<pre>vzdump --restore /space/backup/vzdump-777.tar 600</pre>

[[Category: HOWTO]]

Archlinux Template creation

2007-03-14T18:26:54Z

Curx: inital release

Instructions manually create a minimal Archlinux (0.8) "Voodoo" OS Template.

== Prerequisites ==

I used a modified archbootstrap script which can be found at http://forzza.systs.org/openvz-misc/

Edit settings of script "archbootstrap" :

<pre>
ARCH="i686"
IGNORE="rp-pppoe ppp wireless_tools xfsdump xfsprogs reiserfsprogs lshwd usbutils pciutils pcmciautils module-init-tools mdadm mkinitcpio libusb jfsutils lvm2 lilo cryptsetup device-mapper dhcpcd hwdetect dmapi gen-init-cpio grub"

umark PACMAN_OPTS (remove '#')
</pre>

{{Note|I suggest to place the build for OpenVZ templates to /vz/template/, schema: /vz/template/$DIST/$VERSION/$ARCH/}}

<pre>
Built this OS-Template with:

VE0_dist Debian
VE0_ARCH i386

DIST arch
VERSION 0.8
ARCH depends on VE0 settings above
</pre>

== bootstrapping Archlinux ==

Syntax:

VE0_# /usr/bin/archbootstrap /vz/template/$DIST/$VERSION/$ARCH/ [MIRROR]

{{Note|Please use mirrors ! A full list of Archlinux mirrors : http://wiki.archlinux.org/index.php/Mirror}}

== enter the Build with chroot ==

All the commands below are executed from the root shell. I this howto "chroot" is used to enter as NEWROOT, a BUILD-VE must not be created!

VE0_# chroot /vz/template/$DIST/$VERSION/$ARCH/

=== setting DNS server ===

For the chroot BUILD we also need to specify a DNS for it:

BUILD_# mv /etc/resolv.conf.pacorig /etc/resolv.conf

=== update and install packages ===

Update (sync) pacman cache and update installed packages

BUILD_# pacman -Syu

Install openssh (client and server) , quota-tools and iproute

BUILD_# pacman -S openssh quota-tools iproute

=== fix /etc/mtab ===

Add symlink /proc/mount /etc/mtab

BUILD_# ln -s /proc/mounts /etc/mtab

=== fix /etc/inittab ===

Remove getties from inittab

BUILD_# sed -i -e '/getty/d' /etc/inittab

=== create device nodes ===

Create device nodes at /dev, like console, full, null, zero, urandom, ptmx and fifo of initctl

BUILD_# mknod -m 600 /dev/console c 5 1

BUILD_# mknod -m 666 /dev/tty c 5 0

BUILD_# mknod -m 666 /dev/full c 1 7

BUILD_# mknod -m 600 /dev/initctl p

BUILD_# mknod -m 666 /dev/null c 1 3

BUILD_# mknod -m 666 /dev/ptmx c 5 2

BUILD_# mkdir pts

BUILD_# mknod -m 666 /dev/random c 1 8

BUILD_# mknod -m 444 /dev/urandom c 1 9

BUILD_# mknod -m 666 /dev/zero c 1 5

=== sysinit script modification ===

Remove deleting of /etc/mtab in /etc/rc.sysinit and add mounting of /dev/pts

BUILD_# nano /etc/rc.sysinit

<pre>
[...]
/bin/rm -f /etc/mtab
[...]
</pre>

to

<pre>
[...]
#/bin/rm -f /etc/mtab
/bin/mount -t devpts none /dev/pts
[...]
</pre>

=== modify the main configuration file ===

BUILD_# nano /etc/rc.conf

<pre>
# Localization
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"

# example : German KEYMAP and Timezone to Berlin
TIMEZONE="Europe/Berlin"
KEYMAP="de-latin1-nodeadkeys"

CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# Network settings
HOSTNAME="localhost"

# DAEMONS
# Add openssh to DAEMONS, start at bootup ; ssh-keys are build on first VE start !!!
DAEMONS=(syslog-ng network netfs crond ssh)
</pre>

=== enable ssh connections ===

{{Note|All connection are disabled to VE, see /etc/hosts.deny, only affected server built-in with libwrap}}

Allow ssh :

<pre>
BUILD_# echo "ssh: ALL : ALLOW" >> /etc/hosts.allow}
</pre>

=== lock (disable) the root account ===

BUILD_# passwd -l root

=== exit the chroot to VE0 ===

BUILD_# exit

== build a exclude list ==

Shrink the OS-Template, so not all files needed in a VE - OS - TEMPLATE

Remove unused pacman backup files

VE0_# find ./ -name '*.pacorig' > ../exclude.list-$ARCH

/etc/resolv.conf is added by vzctl:

VE0_# echo "etc/resolv.conf" >> ../exclude.list-$ARCH

dont add downloaded pkg to ostemplate:

VE0_# find ./var/cache/ -name '*.tar.gz' >> ../exclude.list-$ARCH

we dont need no logs and historys

VE0_# find ./var/cache/ -name '*.tar.gz' >> ../exlcude.list-$ARCH

VE0_# find ./root/.bash_history >> ../exclude.list-$ARCH

== create OS-Template ==

VE0_# tar -X ../exclude.list-$ARCH -czf /vz/template/cache/arch-0.8-$ARCH-minimal.tar.gz ./

== use the OS-Template ==

VE0_# vzctl create <VEID> --ostemplate arch-0.8-$ARCH-minimal ...

== update the OS-Template ==

to update a template is really easy, enter the build with chroot, performing upgrade task

VE0_# chroot /vz/template/$DIST/$VERSION/$ARCH/ 'pacman -Syu'

Update the exclude list, and pack upgraded OS - Template

== Links ==

Archlinux wiki http://wiki.archlinux.org/index.php/Main_Page

[[Category: HOWTO]]
[[Category: Templates]]

Virtual Ethernet device

2007-03-06T09:45:11Z

Curx: add infos of syntax change in 3.0.14

'''Virtual ethernet device''' is an ethernet-like device which can be used inside a [[VE]]. Unlike
[[venet]] network device, veth device has a MAC address. Due to this, it can be used in configurations, when veth is bridged to ethX or other device and VE user fully sets up his networking himself,
including IPs, gateways etc.

Virtual ethernet device consist of two ethernet devices - one in [[VE0]] and another one
in VE. These devices are connected to each other, so if a packet goes to one
device it will come out from the other device.

== Virtual ethernet device usage ==

=== Kernel module ===
First of all, make sure the <code>vzethdev</code> module is loaded:
<pre>
# lsmod | grep vzeth
vzethdev 8224 0
vzmon 35164 5 vzethdev,vznetdev,vzrst,vzcpt
vzdev 3080 4 vzethdev,vznetdev,vzmon,vzdquota
</pre>

In case it is not loaded, load it:
<pre>
# modprobe vzethdev
</pre>

You might want to add the module to <code>/etc/init.d/vz script</code>, so it will be loaded during startup.

{{Note|since vzctl version 3.0.11, vzethdev is loaded by /etc/init.d/vz}}

=== Adding veth to a VE ===

{{Note|Use random MAC addresses. Do not use MAC addresses of real eth devices, because this can lead to collisions and MAC addresses must be entered in XX:XX:XX:XX:XX:XX format.}}

==== syntax vzctl version < 3.0.14 ====

<pre>
vzctl set <VEID> --veth_add <dev_name>,<dev_addr>,<ve_dev_name>,<ve_dev_addr>
</pre>

Here
* <tt>dev_name</tt> is the ethernet device name that you are creating on the [[VE0|host system]]
* <tt>dev_addr</tt> is its MAC address
* <tt>ve_dev_name</tt> is the corresponding ethernet device name you are creating on the VE
* <tt>ve_dev_addr</tt> is its MAC address

{{Note| that this option is incremental, so devices are added to already existing ones.}}

NB there are no spaces after the commas

Example:

<pre>
vzctl set 101 --veth_add veth101.0,00:12:34:56:78:9A,eth0,00:12:34:56:78:9B --save
</pre>
After executing this command <tt>veth</tt> device will be created for VE 101 and veth configuration will be saved to a VE configuration file.
Host-side ethernet device will have <tt>veth101.0</tt> name and <tt>00:12:34:56:78:9A</tt> MAC address.
VE-side ethernet device will have <tt>eth0</tt> name and <tt>00:12:34:56:78:9B</tt> MAC address.

==== syntax vzctl version >= 3.0.14 ====

Read Update infos about [http://openvz.org/news/updates/vzctl-3.0.14-1 vzctl 3.0.14]

<pre>
vzctl set <VEID> --netif_add <ifname>[,<mac>,<host_ifname>,<host_mac]
</pre>

Here
* <tt>ifname</tt> is the ethernet device name in the VE
* <tt>mac</tt> is its MAC address in the VE
* <tt>host_ifname</tt> is the ethernet device name on the host ([[VE0]])
* <tt>host_mac</tt> is its MAC address on the host ([[VE0]])

{{Note|All parameters except ifname are optional and are automatically generated if not specified.}}

Example:

<pre>
vzctl set 101 --netif_add eth0,00:12:34:56:78:9A,veth101.0,00:12:34:56:78:9B --save
</pre>

=== Removing veth from a VE ===

==== syntax vzctl version < 3.0.14 ====

<pre>
vzctl set <VEID> --veth_del <dev_name>
</pre>
Here <tt>dev_name</tt> is the ethernet device name in the [[VE0|host system]].

Example:
<pre>
vzctl set 101 --veth_del veth101.0 --save
</pre>
After executing this command veth device with host-side ethernet name veth101.0 will be removed from VE 101 and veth configuration will be updated in VE config file.

==== syntax vzctl version >= 3.0.14 ====
<pre>
vzctl set <VEID> --netif_del <dev_name>|<all>
</pre>

Here
* <tt>dev_name</tt> is the ethernet device name in the [[VE]].

{{Note|If you want to remove all ethernet devices in VE, use all.}}

Example:

<pre>
vzctl set 101 --netif_del eth0 --save
</pre>

== Common configurations with virtual ethernet devices ==
Module <tt>vzethdev</tt> must be loaded to operate with veth devices.

=== Simple configuration with virtual ethernet device ===

==== Start a VE ====
<pre>
[host-node]# vzctl start 101
</pre>

==== Add veth device to VE ====
<pre>
[host-node]# vzctl set 101 --veth_add veth101.0,00:12:34:56:78:9A,eth0,00:12:34:56:78:9B --save
</pre>

==== Configure devices in VE0 ====
<pre>
[host-node]# ifconfig veth101.0 0
[host-node]# echo 1 > /proc/sys/net/ipv4/conf/veth101.0/forwarding
[host-node]# echo 1 > /proc/sys/net/ipv4/conf/veth101.0/proxy_arp
[host-node]# echo 1 > /proc/sys/net/ipv4/conf/eth0/forwarding
[host-node]# echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp
</pre>

==== Configure device in VE ====
<pre>
[host-node]# vzctl enter 101
[ve-101]# /sbin/ifconfig eth0 0
[ve-101]# /sbin/ip addr add 192.168.0.101 dev eth0
[ve-101]# /sbin/ip route add default dev eth0
</pre>

==== Add route in [[VE0]] ====
<pre>
[host-node]# ip route add 192.168.0.101 dev veth101.0
</pre>

=== Virtual ethernet device with IPv6 ===

==== Start [[VE]] ====
<pre>
[host-node]# vzctl start 101
</pre>

==== Add veth device to [[VE]] ====
<pre>
[host-node]# vzctl set 101 --veth_add veth101.0,00:12:34:56:78:9A,eth0,00:12:34:56:78:9B --save
</pre>

==== Configure devices in [[VE0]] ====
<pre>
[host-node]# ifconfig veth101.0 0
[host-node]# echo 1 > /proc/sys/net/ipv6/conf/veth101.0/forwarding
[host-node]# echo 1 > /proc/sys/net/ipv6/conf/eth0/forwarding
[host-node]# echo 1 > /proc/sys/net/ipv6/conf/all/forwarding
</pre>

==== Configure device in [[VE]] ====
<pre>
[host-node]# vzctl enter 101
[ve-101]# /sbin/ifconfig eth0 0
</pre>

==== Start router advertisement daemon (radvd) for IPv6 in VE0 ====
First you need to edit radvd configuration file. Here is a simple example of <tt>/etc/radv.conf</tt>:
<pre>
interface veth101.0
{
AdvSendAdvert on;
MinRtrAdvInterval 3;
MaxRtrAdvInterval 10;
AdvHomeAgentFlag off;

prefix 3ffe:2400:0:0::/64
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr off;
};
};

interface eth0
{
AdvSendAdvert on;
MinRtrAdvInterval 3;
MaxRtrAdvInterval 10;
AdvHomeAgentFlag off;

prefix 3ffe:0302:0011:0002::/64
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr off;
};
};
</pre>

Then, start radvd:
<pre>
[host-node]# /etc/init.d/radvd start
</pre>

==== Add IPv6 addresses to devices in [[VE0]] ====
<pre>
[host-node]# ip addr add dev veth101.0 3ffe:2400::212:34ff:fe56:789a/64
[host-node]# ip addr add dev eth0 3ffe:0302:0011:0002:211:22ff:fe33:4455/64
</pre>

=== Virtual ethernet devices can be joined in one bridge ===
Perform steps 1 - 4 from Simple configuration chapter for several VEs and/or veth devices

==== Create bridge device ====
<pre>
[host-node]# brctl addbr vzbr0
</pre>

==== Add veth devices to bridge ====
<pre>
[host-node]# brctl addif vzbr0 veth101.0
...
[host-node]# brctl addif vzbr0 veth101.n
[host-node]# brctl addif vzbr0 veth102.0
...
...
[host-node]# brctl addif vzbr0 vethXXX.N
</pre>

==== Configure bridge device ====
<pre>
[host-node]# ifconfig vzbr0 0
[host-node]# echo 1 > /proc/sys/net/ipv4/conf/vzbr0/forwarding
[host-node]# echo 1 > /proc/sys/net/ipv4/conf/vzbr0/proxy_arp
</pre>

==== Add routes in [[VE0]] ====
<pre>
[host-node]# ip route add 192.168.101.1 dev vzbr0
...
[host-node]# ip route add 192.168.101.n dev vzbr0
[host-node]# ip route add 192.168.102.1 dev vzbr0
...
...
[host-node]# ip route add 192.168.XXX.N dev vzbr0
</pre>

Thus you'll have more convinient configuration, i.e. all routes to VEs will be through this bridge and VEs can communicate with each other even without these routes.

=== Making a veth-device persistent ===
At the moment, it is not possible to have the commands needed for a persistent veth being made automatically be vzctl. A bugreport ( http://bugzilla.openvz.org/show_bug.cgi?id=301 ) has already been made. Until then, here's a way to make the above steps persistent (for a debian based system in this example).

==== Cleaning ${VEID}.conf ====
=====Option A)=====
Open up /etc/vz/conf/VEID.conf and comment out any IP_ADDRESS-entries to prevent a VENET-device from being created in the VE. Add or change the entry CONFIG_CUSTOMIZED="yes".

=====Option B)=====
Follow Option A and add in addition a VETH_IP_ADDRESS="<your VE IP>" entry to your /etc/vz/conf/VEID.conf including the IP Address you want to set.

====Adding an external script to VE0 ====
Copy and paste the following code (either Option A or B) into /usr/sbin/vznetaddroute:
=====Option A)=====
<pre>
#!/bin/bash
#
# This script adds the appropriate VE0-route for veth-enabled VEs.
# See http://wiki.openvz.org/Virtual_Ethernet_device for more information.
#

# check the VEID
if [ "${VEID}" == 101 ]; then
echo "Adding interface veth101.0 and route 192.168.0.101 for VE101 to VE0"
/sbin/ifconfig veth101.0 0
echo 1 > /proc/sys/net/ipv4/conf/veth101.0/forwarding
echo 1 > /proc/sys/net/ipv4/conf/veth101.0/proxy_arp
echo 1 > /proc/sys/net/ipv4/conf/eth0/forwarding
echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp
/sbin/ip route add 192.168.0.101 dev veth101.0
elsif [ "${VEID}" == 102 ]; then
echo "Adding interface veth102.0 and route 192.168.0.102 for VE101 to VE0"
/sbin/ifconfig veth101.0 0
echo 1 > /proc/sys/net/ipv4/conf/veth102.0/forwarding
echo 1 > /proc/sys/net/ipv4/conf/veth102.0/proxy_arp
echo 1 > /proc/sys/net/ipv4/conf/eth0/forwarding
echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp
/sbin/ip route add 192.168.0.102 dev veth102.0
elsif [ "${VEID}" == YOUR_VE ]; then
# same as above with the vethYOUR_VE.0 device and the appropriate ip
fi
exit
</pre>

Add one elsif-section for every veth-enabled VE you'd like to have automatically configured. Remember to run <pre>chmod +x /usr/sbin/vznetaddroute</pre> to make the script executable.
=====Option B)=====
<pre>
#!/bin/bash

VZCONFDIR=/etc/vz
VZHOSTIF=$BASH_ARGV

. $VZCONFDIR/conf/$VEID.conf

if [ -n $VETH_IP_ADDRESS ]; then
echo "Adding interface $VZHOSTIF and route $VETH_IP_ADDRESS for VE$VEID to VE0"
/sbin/ifconfig $VZHOSTIF 0
echo 1 > /proc/sys/net/ipv4/conf/$VZHOSTIF/proxy_arp
echo 1 > /proc/sys/net/ipv4/conf/$VZHOSTIF/forwarding
/sbin/ip route add $VETH_IP_ADDRESS dev $VZHOSTIF
else
echo "found no VETH_IP_ADDRESS in $VZCONFDIR/conf/$VEID.conf!"
exit 1;
fi
exit
</pre>
Remember to run <pre>chmod +x /usr/sbin/vznetaddroute</pre> to make the script executable.

in addition you need to edit your /etc/network/interfaces and add the sysctl statements for forwardings and proxy_arp like this:
<pre>
auto eth0
iface eth0 inet static
address 10.1.1.1
netmask 255.255.255.0
network 10.1.1.0
broadcast 10.1.1.255
gateway 10.215.1.254
dns-nameservers 10.215.1.20
dns-search prod.your.domain
up sysctl -w net.ipv4.conf.eth0.proxy_arp=1
up sysctl -w net.ipv4.conf.eth0.forwarding=1
</pre>

afterwards execute both statements manualy:
<pre>
sysctl -w net.ipv4.conf.eth0.proxy_arp=1
sysctl -w net.ipv4.conf.eth0.forwarding=1
</pre>

====Make vzctl run the script====

To make vzctl run the script, copy and paste the following line to /etc/vz/vznet.conf:
<pre>
#!/bin/bash
EXTERNAL_SCRIPT="/usr/sbin/vznetaddroute"
</pre>
The script will now run every time a veth-enabled VE is started.

==== Adding a script to VE ====

Now we're done with VE0, we still need to add a route to the VE itself. So we start up the VE with <pre>vzctl start 101</pre>, get into it with <pre>vzctl enter 101</pre> and create a new file /etc/init.d/route-up in the VE with the following content:
<pre>
#!/bin/bash
/sbin/ip route add default dev eth0
</pre>

Make the script executable with <pre>chmod +x /etc/init.d/route-up</pre> and add it to the runlevels:
<pre>
ve101:/# update-rc.d route-up defaults
Adding system startup for /etc/init.d/route-up ...
/etc/rc0.d/K20route-up -> ../init.d/route-up
[...]
</pre>

==== Checking ====
Now to see if everything worked, leave the VE with <pre>exit</pre>, stop the VE via <pre>vzctl stop 101</pre> and restart it with <pre>vzctl start 101</pre>. Still in VE0, check the route for the VE:
<pre>
ve0:/# ip route ls
192.168.0.101 dev veth101.0 scope link
[...]
ve0:/# ping 192.168.0.101 -c 4 -q
[...]
--- 192.168.0.101 ping statistics ---
4 packets transmitted, 4 recieved, 0% packet loss, time 0ms
</pre>

If somethings not working, check the contents of the files we just created or changed. Now get into the VE via <pre>vzctl enter 101</pre> and check the routing there:
<pre>
ve101:/# ifconfig
eth0 Link encap:Ethernet HWaddr 00:12:34:56:78:9B
inet addr:192.168.0.101 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:92 errors:0 dropped:0 overruns:0 frame:0
TX packets:94 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6757 (6.5 KiB) TX bytes:10396 (10.1 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 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)
ve101:/# ip route ls
default dev eth0 scope link
ve101:/# ping 192.168.0.101 -c 4 -q
[...]
--- 192.168.0.101 ping statistics ---
4 packets transmitted, 4 recieved, 0% packet loss, time 0ms
</pre>

If you have problems getting it persistent, please comment.

=== Virtual ethernet devices + VLAN ===
This configuration can be done by adding vlan device to the previous configuration.

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

== External links ==
* [http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/hints-daemons-radvd.html Linux IPv6 HOWTO, a chapter about radvd]

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

Installation on Debian/old

2007-01-18T07:31:24Z

Curx: /* precompiled kernel images at debian.systs.org (dso) */ removed 2.6.16

= Sarge (Stable) =
The OpenVZ packages at http://debian.systs.org/ aimed to install OpenVZ in a easy way, some task are done on install process!

== edit apt source settings ==
Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ stable openvz
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

== precompiled kernel images at debian.systs.org (dso) ==
The kernel-images on debian.systs.org (dso) use the same kernel-config taken from OpenVZ.
(most kernel-modules are built-in!)

kernel(s) for i368 and amd64
<pre>
ovzkernel-2.6.9
ovzkernel-2.6.9-smp

ovzkernel-2.6.18
ovzkernel-2.6.18-smp
</pre>

i386 only:
<pre>
ovzkernel-2.6.18-enterprise
</pre>

OpenVZ tool(s) for i386 and amd64
<pre>
vzctl
vzquota
vzprocps
</pre>

template(s) for i368 and amd64 : Debian 3.1 Minimal
<pre>
vzctl-ostmpl-debian
</pre>

== installing the kernel-images, toolset and debian-os-template ==
Example: install the stable OpenVZ kernel, tools and Debian OS Template

# aptitude install ovzkernel-2.6.9 vzctl vzquota vzctl-ostmpl-debian

Maybe you need to update you "linux-loader" (can be configured at /etc/kernel-img.conf)

for the "GRUB":

# /sbin/grub-update

Reboot in your new Debian Stable OpenVZ System

# reboot

That's all :-)

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.

= Etch (Testing) =
OpenVZ is now a part of Debian Etch (a.k.a. "testing") repository.

== install the kernel-image ==

=== use precomiled kernel images ===
Can be found at http://download.openvz.org/kernel/debian/etch/

<pre>
List of precompiled kernel-images

linux-image-2.6.18-openvz-486_02_i386.deb
linux-image-2.6.18-openvz-686_02_i386.deb
linux-image-2.6.18-openvz-amd64_01_amd64.deb
linux-image-2.6.18-openvz-ia64_01_ia64.deb
linux-image-2.6.18-openvz-k7_02_i386.deb
linux-image-2.6.18-openvz-sparc64-smp_01_sparc.deb
linux-image-2.6.18-openvz-sparc64_01_sparc.deb
</pre>

Example: Installing an OpenVZ precompiled Debian Kernel-Image for an i686:

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

=== or build your own kernel-image (debian way) ===

To install the kernel-source and the OpenVZ kernel patch, run:
<pre>
# apt-get install kernel-package linux-source-2.6.18 kernel-patch-openvz libncurses5-dev
</pre>

Unpack the kernel-source:
<pre>
# cd /usr/src
# tar xjf linux-source-2.6.18.tar.bz2
# cd linux-source-2.6.18
</pre>

You need a kernel config.
You can use the config of the debian-kernel:
<pre>
# cp /boot/config-2.6.18-3-686 .config
</pre>

Or get a 2.6.18 kernel config from http://download.openvz.org/kernel/devel/current/configs/
<pre>
# wget http://download.openvz.org/kernel/devel/current/configs/kernel-2.6.18-028test010-i686.config.ovz -O .config
</pre>

Now you can apply openvz kernel patch and modify your kernel-config:
<pre>
# ../kernel-patches/all/apply/openvz
# make menuconfig
</pre>

You need following OpenVZ kernel config settings:
<pre>
(taken from a OpenVZ Kernel 2.6.18-028test010.1 on 686)

Filesystem
\_ [*] 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 :-)
\_[*] 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)
\_ [*] 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>

<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 :
# make-kpkg --targets
</pre>

Compile your Kernel (as user root, or you need the --rootcmd!)
<pre>
# 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
</pre>

Install the kernel and update initramfs:
<pre>
# dpkg -i ../linux-image-2.6.18-1-openvz_1_i386.deb
# update-initramfs -c -k 2.6.18-1-openvz
</pre>

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

Update the bootloader (when not done above)

GRUB :

# /usr/sbin/update-grub

INFO: since the Debian ETCH-release the location of update-grub is moved from /sbin/update-grub to /usr/sbin/update-grub !

== install the toolset ==

You need the toolset for manage-ing OpenVZ Virtual Enviromennt (VE)

<pre>
# apt-get install vzctl vzquota
</pre>

== modify needed settings ==

a Debian Way:

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.

# editor /etc/network/options

In some cases you may need to enable proxy_arp for the network devices that you want your virtual hosts to be accessible on.
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>
[...]
# 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=1
pre-down sysctl -w net.ipv4.conf.%DEV%.proxy_arp=0
[...]
</pre>

or use the /etc/network/if-up/ and /etc/network/if-down.d/ directories.

<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 settings to "/etc/sysctl.conf"

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

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

'''Before you restart you Server, keep in mind, that your system has all needed modules enabled; booting from your harddisk (e.g. hardware modules, raid system(s), lvm2 etc). May you need a INITRD (initramdisk) or compile needed kernel modules statically in.'''

# reboot

That's all!

Now it's time to create a OS Template or download another precreated OS-Template.

INFO: Suggestions: Setup your default OS Template in /etc/vz/vz.conf

[[Category: HOWTO]]
[[Category: Installation]]

Installation on Debian/old

2007-01-18T07:29:41Z

Curx: add kernel config option, minor changes

= Sarge (Stable) =
The OpenVZ packages at http://debian.systs.org/ aimed to install OpenVZ in a easy way, some task are done on install process!

== edit apt source settings ==
Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ stable openvz
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

== precompiled kernel images at debian.systs.org (dso) ==
The kernel-images on debian.systs.org (dso) use the same kernel-config taken from OpenVZ.
(most kernel-modules are built-in!)

kernel(s) for i368 and amd64
<pre>
ovzkernel-2.6.9
ovzkernel-2.6.9-smp

ovzkernel-2.6.16
ovzkernel-2.6.16-smp

ovzkernel-2.6.18
ovzkernel-2.6.18-smp
</pre>

i386 only:
<pre>
ovzkernel-2.6.18-enterprise
</pre>

OpenVZ tool(s) for i386 and amd64
<pre>
vzctl
vzquota
vzprocps
</pre>

template(s) for i368 and amd64 : Debian 3.1 Minimal
<pre>
vzctl-ostmpl-debian
</pre>

== installing the kernel-images, toolset and debian-os-template ==
Example: install the stable OpenVZ kernel, tools and Debian OS Template

# aptitude install ovzkernel-2.6.9 vzctl vzquota vzctl-ostmpl-debian

Maybe you need to update you "linux-loader" (can be configured at /etc/kernel-img.conf)

for the "GRUB":

# /sbin/grub-update

Reboot in your new Debian Stable OpenVZ System

# reboot

That's all :-)

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.

= Etch (Testing) =
OpenVZ is now a part of Debian Etch (a.k.a. "testing") repository.

== install the kernel-image ==

=== use precomiled kernel images ===
Can be found at http://download.openvz.org/kernel/debian/etch/

<pre>
List of precompiled kernel-images

linux-image-2.6.18-openvz-486_02_i386.deb
linux-image-2.6.18-openvz-686_02_i386.deb
linux-image-2.6.18-openvz-amd64_01_amd64.deb
linux-image-2.6.18-openvz-ia64_01_ia64.deb
linux-image-2.6.18-openvz-k7_02_i386.deb
linux-image-2.6.18-openvz-sparc64-smp_01_sparc.deb
linux-image-2.6.18-openvz-sparc64_01_sparc.deb
</pre>

Example: Installing an OpenVZ precompiled Debian Kernel-Image for an i686:

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

=== or build your own kernel-image (debian way) ===

To install the kernel-source and the OpenVZ kernel patch, run:
<pre>
# apt-get install kernel-package linux-source-2.6.18 kernel-patch-openvz libncurses5-dev
</pre>

Unpack the kernel-source:
<pre>
# cd /usr/src
# tar xjf linux-source-2.6.18.tar.bz2
# cd linux-source-2.6.18
</pre>

You need a kernel config.
You can use the config of the debian-kernel:
<pre>
# cp /boot/config-2.6.18-3-686 .config
</pre>

Or get a 2.6.18 kernel config from http://download.openvz.org/kernel/devel/current/configs/
<pre>
# wget http://download.openvz.org/kernel/devel/current/configs/kernel-2.6.18-028test010-i686.config.ovz -O .config
</pre>

Now you can apply openvz kernel patch and modify your kernel-config:
<pre>
# ../kernel-patches/all/apply/openvz
# make menuconfig
</pre>

You need following OpenVZ kernel config settings:
<pre>
(taken from a OpenVZ Kernel 2.6.18-028test010.1 on 686)

Filesystem
\_ [*] 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 :-)
\_[*] 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)
\_ [*] 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>

<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 :
# make-kpkg --targets
</pre>

Compile your Kernel (as user root, or you need the --rootcmd!)
<pre>
# 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
</pre>

Install the kernel and update initramfs:
<pre>
# dpkg -i ../linux-image-2.6.18-1-openvz_1_i386.deb
# update-initramfs -c -k 2.6.18-1-openvz
</pre>

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

Update the bootloader (when not done above)

GRUB :

# /usr/sbin/update-grub

INFO: since the Debian ETCH-release the location of update-grub is moved from /sbin/update-grub to /usr/sbin/update-grub !

== install the toolset ==

You need the toolset for manage-ing OpenVZ Virtual Enviromennt (VE)

<pre>
# apt-get install vzctl vzquota
</pre>

== modify needed settings ==

a Debian Way:

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.

# editor /etc/network/options

In some cases you may need to enable proxy_arp for the network devices that you want your virtual hosts to be accessible on.
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>
[...]
# 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=1
pre-down sysctl -w net.ipv4.conf.%DEV%.proxy_arp=0
[...]
</pre>

or use the /etc/network/if-up/ and /etc/network/if-down.d/ directories.

<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 settings to "/etc/sysctl.conf"

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

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

'''Before you restart you Server, keep in mind, that your system has all needed modules enabled; booting from your harddisk (e.g. hardware modules, raid system(s), lvm2 etc). May you need a INITRD (initramdisk) or compile needed kernel modules statically in.'''

# reboot

That's all!

Now it's time to create a OS Template or download another precreated OS-Template.

INFO: Suggestions: Setup your default OS Template in /etc/vz/vz.conf

[[Category: HOWTO]]
[[Category: Installation]]

Talk:Installation on Debian/old

2007-01-08T23:05:52Z

Curx:

info about needed modules in kernel-config

info about "Yet Another mkInitRD" yaid tools creating initrd-files

Talk:Installation on Debian/old

2007-01-08T23:05:34Z

Curx: todo, hints and suggestions

todo:

info about needed modules in kernel-config
info about "Yet Another mkInitRD" yaid tools creating initrd-files

Installation on Debian/old

2007-01-08T22:58:07Z

Curx: add info's about precreated debian at download.openvz.org, add minor hints

= Sarge (Stable) =
The OpenVZ packages at http://debian.systs.org/ aimed to install OpenVZ in a easy way, some task are done on install process!

== edit apt source settings ==
Add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ stable openvz
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

== precompiled kernel images at debian.systs.org (dso) ==
The kernel-images on debian.systs.org (dso) use the same kernel-config taken from OpenVZ.
(most kernel-modules are built-in!)

kernel(s) for i368 and amd64
<pre>
ovzkernel-2.6.9
ovzkernel-2.6.9-smp

ovzkernel-2.6.16
ovzkernel-2.6.16-smp

ovzkernel-2.6.18
ovzkernel-2.6.18-smp
</pre>

i386 only:
<pre>
ovzkernel-2.6.18-enterprise
</pre>

OpenVZ tool(s) for i386 and amd64
<pre>
vzctl
vzquota
vzprocps
</pre>

template(s) for i368 and amd64 : Debian 3.1 Minimal
<pre>
vzctl-ostmpl-debian
</pre>

== installing the kernel-images, toolset and debian-os-template ==
Example: install the stable OpenVZ kernel, tools and Debian OS Template

# aptitude install ovzkernel-2.6.9 vzctl vzquota vzctl-ostmpl-debian

Maybe you need to update you "linux-loader" (can be configured at /etc/kernel-img.conf)

for the "GRUB":

# /sbin/grub-update

Reboot in your new Debian Stable OpenVZ System

# reboot

That's all :-)

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.

= Etch (Testing) =
OpenVZ is now a part of Debian Etch (a.k.a. "testing") repository.

== install the kernel-image ==

=== use precomiled kernel images ===
Can be found at http://download.openvz.org/kernel/debian/etch/

<pre>
List of precompiled kernel-images

linux-image-2.6.18-openvz-486_02_i386.deb
linux-image-2.6.18-openvz-686_02_i386.deb
linux-image-2.6.18-openvz-amd64_01_amd64.deb
linux-image-2.6.18-openvz-ia64_01_ia64.deb
linux-image-2.6.18-openvz-k7_02_i386.deb
linux-image-2.6.18-openvz-sparc64-smp_01_sparc.deb
linux-image-2.6.18-openvz-sparc64_01_sparc.deb
</pre>

Example: Installing an OpenVZ precompiled Debian Kernel-Image for an i686:

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

=== or build your own kernel-image (debian way) ===

To install the kernel-source and the OpenVZ kernel patch, run:
<pre>
# apt-get install kernel-package linux-source-2.6.18 kernel-patch-openvz libncurses5-dev
</pre>

Unpack the kernel-source:
<pre>
# cd /usr/src
# tar xjf linux-source-2.6.18.tar.bz2
# cd linux-source-2.6.18
</pre>

You need a kernel config.
You can use the config of the debian-kernel:
<pre>
# cp /boot/config-2.6.18-3-686 .config
</pre>

Or get a 2.6.18 kernel config from http://download.openvz.org/kernel/devel/current/configs/
<pre>
# wget http://download.openvz.org/kernel/devel/current/configs/kernel-2.6.18-028test007-i686.config.ovz -O .config
</pre>

Now you can apply openvz kernel patch and modify your kernel-config:
<pre>
# ../kernel-patches/all/apply/openvz
# make menuconfig
</pre>

You need following OpenVZ kernel config settings:
<pre>
</pre>

Compile your Kernel (as user root, or you need the --fakerootcmd!)
<pre>
# make-kpkg --append_to_version=-1-openvz --added_patches=openvz --revision=1 kernel_image --initrd
</pre>

Install the kernel and update initramfs:
<pre>
# dpkg -i ../linux-image-2.6.18-1-openvz_1_i386.deb
# update-initramfs -c -k 2.6.18-1-openvz
</pre>

INFO: update-initramfs is done, when make-kpkg is use with --initrd option

INFO: update-grub can be configured by /etc/kernel-img.conf

Update the bootloader (when not done above)

GRUB :

# /usr/sbin/update-grub

INFO: since the Debian ETCH-release the location of update-grub is moved from /sbin/update-grub to /usr/sbin/update-grub !

== install the toolset ==

You need the toolset for manage-ing OpenVZ Virtual Enviromennt (VE)

<pre>
# apt-get install vzctl vzquota
</pre>

== modify needed settings ==

Debian Way:

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.

# editor /etc/network/options

In some cases you may need to enable proxy_arp for the network devices that you want your virtual hosts to be accessible on.
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>
[...]
# 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=1
pre-down sysctl -w net.ipv4.conf.%DEV%.proxy_arp=0
[...]
</pre>

or use the /etc/network/if-up/ and /etc/network/if-pre-down.d/ directories.

INFO: # man 5 interfaces (to read more about debian's network interface configuration for ifup and ifdown)

INFO: Please add to use the magic-sysrq key, to your /etc/sysctl.conf

plain OpenVZ Linux Way:

Add settings to "/etc/sysctl.conf"

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

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

'''Before you restart you Server, keep in mind, that your system has all needed modules enabled; booting from your harddisk (e.g. hardware modules, raid system(s), lvm2 etc). May you need a INITRD (initramdisk) or compile needed kernel modules statically in.'''

# reboot

That's all!

Now it's time to create a OS Template or download another precreated OS-Template.

INFO: Suggestions: Setup your default OS Template in /etc/vz/vz.conf

[[Category: HOWTO]]
[[Category: Installation]]

Talk:Debian template creation

2007-01-08T12:43:39Z

Curx: Debian template creation

Hi all,
This is my first trial with openVZ and a wiki. Please give me some hints, if anything is wrong. Don't hesitate to correct my poor english.

I just installed openVZ on a rather old test box with Debian. Installation failed at first and I suppose there is a wrong path statement used for the debian packages.

When I came to
<code>vzctl start 777</code>
I received the message
<code>Starting VE ...
VE private area /var/lib/vz/private/777 does not exist</code>

Moving the directory 777 from /vz/private to /var/lib/vz/private solves this problem.

Now I could start and enter the new VE.

== Debian template creation ==

For backward compablity to main OpenVZ:

Create a symlink from /var/lib/vz to /vz
<pre>
# ln -s /var/lib/vz /vz
</pre>

Installation on Debian/old

2006-12-05T20:10:58Z

Curx: add the test-18 to (dso-)repro

= Stable =

== Edit apt settings ==

add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ stable openvz
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

== Packages at debian.systs.org (dso) ==

precreated OpenVZ Debian Packages:

kernel(s) for i368 and amd64
<pre>
ovzkernel-2.6.9
ovzkernel-2.6.9-smp

ovzkernel-2.6.16
ovzkernel-2.6.16-smp

ovzkernel-2.6.18
ovzkernel-2.6.18-smp
</pre>

i386 only:
<pre>
ovzkernel-2.6.18-enterprise
</pre>

OpenVZ tool(s) for i386 and amd64
<pre>
vzctl
vzquota
vzprocps
</pre>

template(s) for i368 and amd64 : Debian 3.1 Minimal
<pre>
vzctl-ostmpl-debian
</pre>

== Installing the kernels and OpenVZ toolset ==

Example: install the stable OpenVZ kernel, tools and debian OS Template

# aptitude install ovzkernel-2.6.9 vzctl vzquota vzctl-ostmpl-debian

Maybe you need to update you "linux-loader" like lilo or grub:

for the "GRUB":
# /sbin/grub-update

Reboot in your new Debian Stable OpenVZ System

# reboot

That's all :-)

=Unstable=

OpenVZ is now a part of Debian Sid (a.k.a. "unstable") repository. This article describes how to install OpenVZ on a Debian Sid system.

== Installing the utilities and kernel patch ==

To install the OpenVZ kernel patch and utilities, run the following:
<pre>
apt-get update
apt-get install kernel-patch-openvz vzctl vzquota
</pre>

== Creating the kernel package ==

To create a kernel package, you need to download and unpack 2.6.16 “vanilla” kernel first:
<pre>
cd /usr/src/
wget http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.16.tar.bz2
tar xjf linux-2.6.16.tar.bz2
cd linux-2.6.16
</pre>

(Note that you do need a vanilla kernel for this, because the OpenVZ kernel patch doesn't apply cleanly to the Debian linux-source-2.6.16 package; see [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377707 Debian bug #377707].)

Next, get the proper kernel config from [http://download.openvz.org/kernel/devel/026test015.1/configs/ download.openvz.org]. Below is the example of using smp config for i686:

<pre>
wget http://download.openvz.org/kernel/devel/026test015.1/configs/kernel-2.6.16-026test015-i686-smp.config.ovz
mv kernel-2.6.16-026test015-i686-smp.config.ovz .config
</pre>

{{Note|This example uses a config file for the 026test015 kernel patch. If the kernel-patch-openvz package you installed is a different version, download a config file that corresponds with your version}}

Now you can apply openvz kernel patch and compile the kernel:

<pre>
make-kpkg --added_patches openvz
</pre>

[[Category: HOWTO]]
[[Category: Installation]]

Installation on Debian/old

2006-10-27T13:27:22Z

Curx: /* Installing the kernels and OpenVZ toolset */ kernel update

= Stable =

== Edit apt settings ==

add to your "/etc/apt/sources.list"

<pre>
deb http://debian.systs.org/ stable openvz
</pre>

and get the new package lists

<pre>
# apt-get update
</pre>

== Packages at debian.systs.org (dso) ==

precreated OpenVZ Debian Packages:

kernel(s) for i368 and amd64 - Version: 023stab032.1
<pre>
ovzkernel-2.6.9
ovzkernel-2.6.9-smp
</pre>

kernel(s) for i368 and amd64 - Version: 026test020.1
<pre>
ovzkernel-2.6.16
ovzkernel-2.6.16-smp
</pre>

OpenVZ tool(s) for i386 and amd64
<pre>
vzctl
vzquota
vzprocps
</pre>

template(s) for i368 and amd64 : Debian 3.1 Minimal
<pre>
vzctl-ostmpl-debian
</pre>

== Installing the kernels and OpenVZ toolset ==

Example:

# aptitude install ovzkernel-2.6.9 vzctl vzquota vzctl-ostmpl-debian

Maybe you need to update you "linux-loader" like lilo or grub:

for the "GRUB":
# /sbin/grub-update

Reboot in your new Debian Stable OpenVZ System

# reboot

That's all :-)

=Unstable=

OpenVZ is now a part of Debian Sid (a.k.a. "unstable") repository. This article describes how to install OpenVZ on a Debian Sid system.

== Installing the utilities and kernel patch ==

To install the OpenVZ kernel patch and utilities, run the following:
<pre>
apt-get update
apt-get install kernel-patch-openvz vzctl vzquota
</pre>

== Creating the kernel package ==

To create a kernel package, you need to download and unpack 2.6.16 “vanilla” kernel first:
<pre>
cd /usr/src/
wget http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.16.tar.bz2
tar xjf linux-2.6.16.tar.bz2
cd linux-2.6.16
</pre>

(Note that you do need a vanilla kernel for this, because the OpenVZ kernel patch doesn't apply cleanly to the Debian linux-source-2.6.16 package; see [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377707 Debian bug #377707].)

Next, get the proper kernel config from [http://download.openvz.org/kernel/devel/026test015.1/configs/ download.openvz.org]. Below is the example of using smp config for i686:

<pre>
wget http://download.openvz.org/kernel/devel/026test015.1/configs/kernel-2.6.16-026test015-i686-smp.config.ovz
mv kernel-2.6.16-026test015-i686-smp.config.ovz .config
</pre>

{{Note|This example uses a config file for the 026test015 kernel patch. If the kernel-patch-openvz package you installed is a different version, download a config file that corresponds with your version}}

Now you can apply openvz kernel patch and compile the kernel:

<pre>
make-kpkg --added_patches openvz
</pre>

[[Category: HOWTO]]
[[Category: Installation]]