= Sarge (Stable) ={{Warning|The OpenVZ packages at http://debian.systs.org/ aimed majority of the content on this page only applies to install OpenVZ in a easy wayolder, some task are done unsupported Debian versions and is archived on install process!this page for historical reasons only. '''The page you need is [[Installation on Debian]].'''}}
OpenVZ consists of a kernel, user-level tools, and container templates.
== edit apt source settings ==Add This guide tells how to your "install the kernel and the tools on [http:/etc/aptwww.debian.org Debian] Etch or Lenny/sourcesSqueeze.list"
<pre>For Squeeze, use the Lenny directions. For Wheezy (7.0), use the vzctl package included in wheezy, together with the Wheezy OpenVZ kernels from [http://download.openvz.org/debian/ http://download.openvz.org/debian/]. deb Alternatively reduced functionality may be possible using the stock Debian Wheezy kernel (based on kernel.org version 3.2) and [[Vzctl_for_upstream_kernel]]. You may also wish to check the information on [http://wiki.debian.systs.org/ stable openvzOpenVz the Debian wiki]. For Etch users, this document explains how to partially upgrade to Debian Lenny and install from lenny repositories ('''use this options at your risk'''). == Requirements == === Filesystems ===It's recommended that you use a separate partition for container privatedirectories (by default <code>/var/lib/vz/private/<CTID></precode>). The reason for this is that if you wish to use the OpenVZ per-container disk quota, you won't be able to use usual Linux disk quotas on the same partition. Bear in mind that "per-container quota" in this context includes not only pure per-container quota but also the usual Linux disk quota used in container, not on the [[HN]]. At the very least try to avoid using the root partition for containers, because the root user of a container will be able to overcome the 5% disk space barrier in some situations. If the HN root partition is completely filled, it will break the system. OpenVZ per-container disk quota is supported only for ext2/ext3 filesystems; therefore it makes sense to use one of these filesystems (ext3 is recommended) if you need per-container disk quota. === Repository setup (Etch only) === '''If you are using Debian Lenny, this step in no longer required. Openvz kernel packages and tools are available on main repository.'''
and get the new package lists==== 1. Using openvz.org repositories ====
<pre># apt-get update<At the moment two different repositories are online at http:/pre>/download.openvz.org:
; by Ola Lundqvist <opal@debian.org>
: (OpenVZ kernels only)
: apt-uri http://download.openvz.org/debian
== precompiled kernel images at ; by Thorsten Schifferdecker <tsd@debian.systs.org (dso) ==>The kernel: apt-images on debianuri http://download.systsopenvz.org /debian-systs: (dso) use the same kernel-config taken Mirror of OpenVZ Repository from OpenVZhttp://debian.systs.(most kernel-modules are built-in!org/)
kernel(s) for i368 and amd64<pre> ovzkernel-2{{Note|The next steps use the repository at http://download.6openvz.9 ovzkernelorg/debian-2systs; the actual OpenVZ Tools for Debian exist only as unstable builds, see http://packages.6debian.9-smporg/vzctl}}
ovzkernel-2{{Note|By default, on Ubuntu systems root tasks are executed with [https://help.6ubuntu.18 ovzkernel-2.6.18-smp<com/community/pre>RootSudo sudo]}}
i386 only:This can be done via the following commands, as root or as privileged "sudo" user
<pre>
ovzkernel# echo -2e "\ndeb http://download.6openvz.18org/debian-enterprise 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>
OpenVZ tool==== 2. Using Debian repositories (supgrade to lenny) for i386 and amd64==== There is even a '''lenny''' repository with kernel 2.6.28. '''Use it at your own risk!''' Add lenny repositories to your '''/etc/apt/sources.list'''
<pre>
vzctldeb http://DEBIAN-MIRROR/debian/ testing main vzquota vzprocpsdeb http://DEBIAN-MIRROR/debian-security/ testing/updates main
</pre>
template(s) for i368 and amd64 Enlarge apt-cache adding to '''/etc/apt/apt.conf''' this line: Debian 3.1 Minimal
<pre>
vzctlAPT::Cache-ostmpl-debianLimit "100000000";
</pre>
== installing the kernel-images, toolset Give etch package priority over lenny packages. Edit '''/etc/apt/preferences''' and debian-os-template =set like this:<pre>Package: *Pin: release a=etchExamplePin-Priority: install the stable OpenVZ kernel, tools and Debian OS Template700
# aptitude install ovzkernelPackage: *Pin: release a=lennyPin-2.6.9 vzctl vzquota vzctl-ostmpl-debianPriority: 650</pre>
Then '''apt-get update && apt-get dist-upgrade''' to upgrade to lenny.
Maybe you need to update you "linux-loader" (can be configured at /etc/kernel-img.conf)== Kernel installation ==
for the "GRUB": === Wheezy and Lenny ===
# {{Note|The best kernel to use is [[Download/sbinkernel/grubrhel6|RHEL6-update based]]. Please see [[Install_kernel_from_RPM_on_Debian_6.0]]}}
=== Etch ===
Reboot in your new Debian Stable OpenVZ System==== 1. Using openvz kernel repositories ====
# reboot{{Note|In case you want to recompile the OpenVZ kernel yourself on Debian, see [[Compiling the OpenVZ kernel (the Debian way)]].}}
First, you need to choose what kernel you want to install.
That{| class="wikitable"|+'s all ''OpenVZ Kernel list built with kernel config from http://download.openvz.org'''! Kernel !! Description !! Hardware !! Debian Architecture|-! ovzkernel-2.6.18| uniprocessor| up to 4GB of RAM| i386 and amd64|-! ovzkernel-2.6.18-smp| symmetric multiprocessor| up to 4 GB of RAM| i386 and amd64|-! ovzkernel-2.6.18-)enterprise| SMP + PAE support + 4/4GB split| up to 64 GB of RAM| i386 only|}
Now it{| class="wikitable"|+''s time to setup your VE's OpenVZ Kernel list built with the minimal official Debian kernel config and OpenVZ Settings'''! Kernel !! Description !! Hardware !! DebianArchitecture|-! fzakernel-32.1 Template, create new one or download another precreated OS6.18-686| uni- and multiprocessor| up to 4GB of RAM| i386|-Template! 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 =====
= Etch (Testing) =OpenVZ In case GRUB is now a part of Debian Etch (a.k.a. "testing") repositoryused 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:
== install the <pre>[...] title Debian GNU/Linux, kernel 2.6.18-ovz-028stab051.1-686 root (hd0,1) kernel /vmlinuz-image 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>
=== use precomiled kernel images ===Can be found at http:/{{Note|per default on debian/downloadubuntu, a 2.openvz6.org/22 kernel/debian/etch/will boot before a 2.6.18, please check manually the grub boot order. See man update-grub for more details}}
<pre>List of precompiled kernel===== Installing the user-imageslevel tools =====
linuxOpenVZ needs some user-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_sparclevel tools installed.deb </pre>Those are:
Example; vzctl: Installing an A utility to control OpenVZ precompiled Debian Kernel-Image containers (create, destroy, start, stop, set parameters etc.); vzquota: A utility to manage quotas for an i686:containers. Mostly used indirectly (by vzctl).
<pre>
# wget http://download.openvz.org/kernel/debian/etch/linux[sudo] apt-image-2.6.18-openvz-686_02_i386.deb # dpkg -i linux-image-2.6.18-openvz-686_02_i386.debget install vzctl vzquota
</pre>
==== 2 Using Debian lenny repositories ====
=== or build your own If you upgrade to lenny, you can search openvz kernel-image (debian way) === To and can install the kernel-source and the OpenVZ kernel patch, runwith:
<pre>
# apt-get install kernel-package linux-source-2.6.18 kernel-patchimage-openvz libncurses5-dev686
</pre>
Unpack the this command will install latest kernel-sourceand all required packages like:
<pre>
# cd /usr/src # tar xjf apt-get install iproute libatm1 linux-sourceimage-2.6.18.tar.bz2 # cd 26-1-openvz-686 linux-sourceimage-openvz-2.6.18686 rsync vzctl vzquota libcgroup-dev
</pre>
and will arrange grub bootloader properly.
=== Rebooting into OpenVZ kernel ===
{{Warning|Before you restart your Server, verify that your system has all needed modules enabled in order to boot your harddisk (e.g. hardware modules, raid system(s), lvm2 etc). You may need an INITRD (initramdisk) or to compile needed kernel modules statically.}}
You need a kernel config.You can use Now reboot the machine and choose the config of OpenVZ Linux Kernel on the debian-kernel:<pre> # cp /boot/config-2loader menu.6.18-3If the OpenVZ kernel has been booted successfully, proceed to installing the user-686 level tools for OpenVZ.config</pre>
=== Confirm proper installation ===
Or get a 21.6.18 kernel config from httpKernel://download.openvz.org/kernel/devel/current/configs/
<pre>
# wget http://download.openvz.org/kernel/devel/current/configs/kerneluname -r 2.6.1826-028test0101-i686.config.ovz openvz-O .config686 #
</pre>
Now you can apply openvz 2. Openvz kernel patch and modify your kernel-configfacility:
<pre>
# ../kernel-patches/all/apply/openvzps ax | grep vz # make menuconfig2349 ? S 0:00 [vzmond]
</pre>
You need following OpenVZ kernel config settings3. A network interface for containers:
<pre>
# ifconfig venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (taken from a OpenVZ Kernel 20.60 B) TX bytes:0 (0.18-028test010.1 on 6860 B)</pre>
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)== Configuring ==
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)=== sysctl ===
User resources There are a number of kernel parameters that should be set for OpenVZ to work correctly... (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 These parameters are stored in <tt>/etc/proc (CONFIG_USER_RESOURCE_PROC)\_ [*] User resources debug features (CONFIG_UBC_DEBUG)\_ [*] Debug kmemsize with cache counters (CONFIG_UBC_DEBUG_KMEM)sysctl.conf</prett>file. Here is the relevant part of the file; please edit it accordingly.
{{Note|vzctl version from debian-systs, automatically inserts these options at the last of <tt>/etc/sysctl.conf</tt>, except for net.ipv4.ip_forward}}
<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 --targetsOn Hardware Node we generally need</pre># 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
Compile your Kernel (as user root, or you need the --rootcmd!)# Enables source route verification<pre> # make-kpkg --append_to_version=-1-openvz --added_patches=openvz --revisionnet.ipv4.conf.all.rp_filter=1 --initrd binary-arch or all above with one step
# makeEnables the magic-kpkg --append_to_version=-1-openvz --added_patches=openvz --revisionsysrq keykernel.sysrq=1 --initrd --config menuconfig binary-arch</pre>
# TCP Explict Congestion Notification
#net.ipv4.tcp_ecn=0
Install the kernel and update initramfs:# we do not want all our interfaces to send redirects<pre> # dpkg -i net.ipv4./linux-image-2conf.6default.18-send_redirects=1-openvz_1_i386net.deb # update-initramfs -c -k 2ipv4.conf.6all.18-1-openvz</pre>send_redirects=0
<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) # [sudo] sysctl -p
GRUB :{{Note|You can make a symlink from /var/lib/vz to /vz as backwardcompatibility to OpenVZ as installed in other distributions(Debian vz root directory is /var/lib/vz to be FHS-compliant.}}
# [sudo] ln -s /usrvar/sbinlib/update-grubvz /vz
INFO: since the Debian ETCH-release the location of update-grub is moved from /sbin/update-grub to /usr/sbin/update-grub !=== OS templates ===
{{Note|Support of OS templates on 64 bit hosts is somewhat limited for the time being, so that not all tools or features are available - please see [[Making template tools to work on x86_64]] and [[Install OpenVZ on a x86 64 system Centos-Fedora]] for additional details and information on possible workarounds}}
== To install the toolset ==a container, you need OS template(s).
You need the toolset for manage-ing OpenVZ Virtual Enviromennt (VE)Precreated templates can be found [http://wiki.openvz.org/Download/template/precreated here] and [http://download.openvz.org/contrib/template/precreated/ here].
<pre>You can create your own templates, see # apt-get install vzctl vzquota</pre>[[Debian template creation]], [[Ubuntu Gutsy template creation]] and [[:Category: Templates]].
{{Note|Setup your prefered standard OS Template : edit the /etc/vz/vz.conf}}
== modify needed settings == # [sudo] apt-get install vzctl-ostmpl-debian-5.0-i386-minimal
a Debian Way: == Additional User Tools ==
If you want network access for the virtual server then you need ; vzprocps: A set of utilities to enable IP forwarding. Set "ip_forward" to yes in /etc/network/option.provide system information (vzps and vztop)
# editor /etc/network/options; [[vzdump]]: A utility to backup and restore container.
# [sudo] apt-get install vzprocps vzdump
In some cases you may need to enable proxy_arp for the network devices that you want your virtual hosts to be accessible onOn Debian squeeze, vzdump seems packaged in standard aptline.You can add this to a specific interface in the network configuration (/etc/network/interfaces) by the following linesFor lenny, replace %DEV% with your device name (ie. eth0).See [[Backup_of_a_running_container_with_vzdump]]
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>Secure it ==
If you want to secure your container with individual firewall rules (instead or use additionally to securing the /etc/network/if-up/ and /etc/network/if-downhost node) then you must run iptables inside the container.d/ directoriesThis works slightly different than on a physical server. So make sure that you check that iptables rules are indeed applied as expected inside the container.
<pre> INFO: # man 5 interfaces (to read more about debian's network interface configuration for ifup and ifdown) INFO: Please add to use Iptables modules required by the magic-sysrq key, to your /etc/sysctlcontainer must be specified in the general vz.conf file or the vzXXX.conf</pre>file of the container.
a (plain) OpenVZ Linux Way:Add the following line into vz.conf to activate the respective iptables modules for all containers.
Add settings to IPTABLES="/etc/sysctl.confip_tables ipt_REJECT ipt_tos ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length ip_conntrack ip_conntrack_ftp ip_conntrack_irc ipt_LOG ipt_conntrack ipt_helper ipt_state iptable_nat ip_nat_ftp ip_nat_irc ipt_TOS"
<pre> # On Hardware Node we generally need # packet forwarding enabled and proxy arp disabled net[[http://wiki.ipv4debian.ip_forward = 1 netorg/DebianFirewall][Configure]] your iptable rules inside the container.ipv4.conf.default.proxy_arp = 0
# Enables source route verification net.ipv4.conf.all.rp_filter = 1{{Warning|Note that iptables rules inside the container are not applied automatically as on a physical server by starting the iptables module! Follow the instructions below}}
# Enables To make sure the magic-sysrq key kernel.sysrq = 1iptables rules are applied on a startup/reboot we'll create a new file:
# TCP Explict Congestion Notification # netnano /etc/network/if-pre-up.ipv4.tcp_ecn = 0d/iptables
# we do not want all our interfaces Add these lines to send redirects net.ipv4.conf.default.send_redirects = 1 net.ipv4.conf.all.send_redirects = 0 </pre>it:
#!/bin/bash
/sbin/iptables-restore < /etc/iptables.up.rules
<pre> INFOThe file needs to be executable so change the permissions: Suggestion: Please make a symlink from /var/lib/vz to /vz as backward compability to Main OpenVZ (Debian vz root directory is installed FHS-like to /var/lib/vz)
# ln -s chmod +x /varetc/libnetwork/vz if-pre-up.d/vz</pre>iptables
Start iptables
'''Before you restart you Server, keep in mind, that your system has all needed modules enabled; booting from your harddisk (e.g. hardware modules, raid system(s), lvm2 /etc). May you need a INITRD (initramdisk) or compile needed kernel modules statically in/init.'''d/iptables start
If the startup shows errors then you have probably not activated the needed iptables modules. See above.
# rebootCheck inside the container that your iptables rules are indeed applied:
iptables -L
If the rules do not show up as you would expect on a physical server then you might not have activated the needed iptables modules.
That's all== Start it!==
Now it's time to create a OS Template or download another precreated OS-Template # [sudo] /etc/init.d/vz start
This does not make the vz system automatically start at boot time. For automatic start:
INFO: Suggestions: Setup your default OS Template in /etc/# [sudo] update-rc.d vz/vz.confdefaults 98
== Use it! ==
After installing the OpenVZ kernel, user tools and a minimal OS template
to create a first container and do some [[basic operations in OpenVZ environment]]. Read the [[download:doc/OpenVZ-Users-Guide.pdf]], browse this wiki.
[[Category: HOWTO]]
[[Category: Debian]]
[[Category: Installation]]