OpenVZ Virtuozzo Containers Wiki - User contributions [en]

Download/vzctl/4.8/changes

2014-10-07T20:22:43Z

Paparaciz: I believe it have to be #2083

== Changes ==
Since {{dlink|vzctl|4.7.2}}:

'''New functionality'''
* vzctl set: add NUMA --nodemask (sponsored by FastVPS)
* vzmigrate: speed up by using se ploop copy with feedback if available
* vzmigrate: speed up by reusing ssh connection
* init.d/vz: show CT stop status
* init.d/vz: implement parallel CT start ({{B|2954}}, {{B|2083}})
* init.d/vz, vz.conf: use/expose VE_PARALLEL
* vzctl start,restore: add --skip-remount
* vzctl snapshot-switch: add --must-restore
* vzmigrate: ability to run ploop copy with timestamps

'''Fixes'''
* vzctl.spec: disable VE0 conntracks only if unused ({{B|2755}})
* vzmigrate: fix for --snapshot ({{B|2907}})
* vzmigrate: don't run vzfsync if there is no need ({{B|3055}})
* vzmigrate: undo_lock if check_cpt_props failed
* vzmigrate: don't exit 1 on success
* vzlist: fix showing DISABLED ({{B|3029}})
* vzlist: fix cpulimit rounding ({{B|3063}})
* redhat-set_hostname.sh: fix for F15+/RHEL7 ({{B|3051}})
* vzctl compact: use built-in PATH ({{B|2990}})
* postcreate.sh: fix caps for suexec

'''Improvements'''
* debian-add_ip.sh: support for Ubuntu 14.04
* postcreate.sh: add RHEL7/CentOS7 support
* vzctl create --diskinodes: check for max ploop size
* vzctl set --ostemplate: require --save ({{B|2909}})
* vzmigrate: don't specify default cipher
* vzmigrate: use getopt for option parsing
* vzmigrate: detect "can't lock CT" error
* vzmigrate: don't use rsync --delete-excluded
* cpumask: allow for up to 4096 CPUs
* vz_setcpu(): don't ignore errors from set_cpu*
* fixed a few memory leaks and non-closed fds reported by Coverity
* compare_osrelease(): fix for 3.x kernels
* parse_{chkpnt,restore}_opt: don't print error twice
* parse*opt(): add/improve extra args check
* vzctl create: improve "no ploop" error message

'''Documentation'''
* vznnc(8): add
* vzctl --help: fix iolimit
* vzctl(8): document set --ostemplate ({{B|2909}})
* vzctl(8): add --nodemask, --must-restore, --skip-remount
* vzctl(8): improve --netfilter
* vz.conf(5): document VE_PARALLEL
* vzmigrate(8), vzmigrate --help: document --ssh-mux

'''Build system'''
* setver.sh: check for ./configure to run autogen
* setver.sh: abort if autogen.sh/configure fails

{{git log|vzctl|vzctl-4.8|}}

=== Thanks ===

OpenVZ project would like to thank the following people who contributed patches
and/or provided bug reports for this vzctl release (in no particular order):

* Anthony Moon
* Aleksandar Ivanisevic
* Pavel Odintsov
* paparaciz
* Florian Bantner
* Ionut Biru
* Evgenii Terechkov
* Kevin Holly
* Stefan Eriksson
* Sean Fulton
* Andrey Tataranovich

Ploop/sparse

2013-11-20T12:42:05Z

Paparaciz: missed closing bracket

'''Sparse file''' is a file that contains blocks of zeroes that are not allocated on disk (see [[w:Sparse file]]). By design, ploop images can't contain such non-allocated blocks.

While ploop is never creating sparse image files, they can be accidentally made so when tools such as <code>rsync --sparse</code> or <code>cp --sparse=always</code> are used to copy images. So, one should not use backup or copy tools that create sparse files out of non-sparse ones.

Since [[Download/ploop/1.10|ploop-1.10]], ploop images are checked for being sparse and are automatically fixed on mount, in case DiskDescriptor.xml is used. Otherwise, you can use <code>ploop check --repair-sparse</code> to check for and repair such images.

== See also ==

* [[Ploop]]
* [[w:Sparse file]]

[[Category: ploop]]

Download mirrors

2013-11-03T10:14:49Z

Paparaciz: https://lists.openvz.org/pipermail/users/2013-November/005388.html

OpenVZ software is available from [http://download.openvz.org/ download.openvz.org] via [http://download.openvz.org/ http] and [ftp://download.openvz.org/ ftp].

The software is also available from a number of mirrors. See the table below.
{| class="wikitable sortable"
|+ OpenVZ Mirrors
|-
! Host !! http !! ftp !! Physical location !!class="unsortable" | Notes

|-
|openvz.org
|| [http://download.openvz.org/ http]
|| [ftp://ftp.openvz.org/ ftp]
|| USA, Virginia, Mc Lean
|| Master site. Also available via rsync, see [[Setting up a mirror]].
|-





|-
| iij.ad.jp
|| [http://ftp.iij.ad.jp/pub/openvz/ http]
|| [ftp://ftp.iij.ad.jp/pub/openvz/ ftp]
|| Japan, Tokyo, Chiyoda
||
|-

|-
| yandex.ru
|| [http://mirror.yandex.ru/mirrors/download.openvz.org/ http]
|| [ftp://mirror.yandex.ru/mirrors/download.openvz.org/ ftp]
|| Russia, Moscow
|| Also available via rsync: mirror.yandex.ru::mirrors/download.openvz.org/



|-
| proserve.nl
|| [http://openvz.proserve.nl http]
|| [ftp://mirror.proserve.nl/openvz ftp]
|| Netherlands (Holland), Amsterdam
|| 1Gbit connection, in a 25Gbit network. Also available via rsync: rsync://openvz.proserve.nl::openvz
|-

| xservers.ro
|| [http://mirrors.xservers.ro/openvz/ http]
| align="center" | —
|| Romania, Bucharest
|| Speeds up to 100Mbps from outside country, up to 1Gbps within Romania




|-
| Ircam.fr
|| [http://mirrors.ircam.fr/openvz/ http]
|| [ftp://mirrors.ircam.fr/pub/OpenVZ/ ftp]
|| France, Paris
|| Also available via rsync: rsync://mirrors.ircam.fr/openvz/





|-
|| tsukuba.wide.ad.jp
|| [http://openvz.tsukuba.wide.ad.jp/ http]
| align="center" | —
|| Japan,　Ibaraki, Tsukuba
|| Updated daily


|-
|| Netriplex.com
|| [http://openvz.mirror.netriplex.com http]
| align="center" | —
|| USA, North Carolina, Asheville
|| Updated every 6 hours






|-
|| Steadfast Networks
|| [http://mirror.steadfast.net/openvz/ http]
|| [ftp://mirror.steadfast.net/openvz/ ftp]
|| USA, IL, Chicago
|| Sync Frequency: hourly This mirror is available via IPv4 and IPv6 and is on an uncapped gigabit line.



|-
|| balticservers.com
|| [http://mirror.duomenucentras.lt/openvz/ http]
|| [ftp://mirror.duomenucentras.lt/openvz ftp]
|| Lithuania, Šiauliai
|| Updated every two hours

|-
|| InterServer, Inc
|| [http://mirror.trouble-free.net/openvz/ http]
| align="center" | —
|| USA, New Jersey, Secaucus
|| 100 mbps, updated 3 times per day Also available via rsync: rsync://mirror.trouble-free.net/openvz

|-
|| RUE Beltelecom
|| [http://mirror.datacenter.by/pub/download.openvz.org/ http]
|| [ftp://mirror.datacenter.by/pub/download.openvz.org/ ftp]
|| Belarus, Minsk
|| 2Gbps, http, ftp, rsync, @hourly


|-
|| IHC.ru
|| [http://mirror.ihc.ru/download.openvz.org/ http]
| align="center" | —
|| Moscow, Russia
|| 1 Gbps, updated hourly

|-
|| THZ Hosting
|| [http://mirrors.thzhost.com/openvz/ http]
| align="center" | —
|| Bangkok, Thailand
|| Updated every 4 hours






|-
|| Softaculous
|| [http://mirror.softaculous.com/openvz/ http]
| align="center" | —
|| Germany
|| Updated once a day

|-
|| FDCServers.net
|| [http://mirror.fdcservers.net/openvz/ http]
|| [ftp://mirror.fdcservers.net/openvz/ ftp]
|| USA, Illinois, Chicago
|| Updated every 2 hours

|-
|| SecureAX Internet
|| [http://mirror.secureax.com/openvz/ http]
| align="center" | —
|| Singapore
|| Updated daily at 2359hrs GMT+8


|-
|| Abdicar
|| [http://mirrors.abdicar.com/OpenVZ http]
|| [ftp://mirrors.abdicar.com/OpenVZ ftp]
|| Costa Rica, Heredia
|| updated hourly Also available via rsync: mirrors.abdicar.com::costarica_OpenVZ

|-
|| JustHosting
|| [http://openvz.just-hosting.ru/ http]
|| [ftp://openvz.just-hosting.ru/ ftp]
|| Germany, Falkenstein
|| Connected at 100 mbit link, hourly updates Also available via rsync://openvz.just-hosting.ru/openvz

|-
|| HitMe.pl
|| [http://openvz.hitme.net.pl/ http]
|| [ftp://openvz.hitme.net.pl/openvz/ ftp]
|| Poland, Gdansk
|| Link 100 Mbit, updated hourly



|-
|| Mj webhosting
|| [http://mirror.serverbeheren.nl/openvz http]
| align="center" | —
|| Netherlands, Overijssel, Enschede
|| Updated every hour. Available on ipv4 and ipv6. 1 gbit uplink.


|-
|| spd.co.il
|| [http://openvz.spd.co.il/ http]
| align="center" | —
|| Israel, Rishon letzion
|| Updated every hour, 100 mbit link

|-
|| DIGIPOWER Co.,ltd
|| [http://mirrors.digipower.vn/openvz http]
|| [ftp://mirrors.digipower.vn/openvz ftp]
|| VietNam
|| Updated 2 times a day rsync:mirrors.digipower.vn::openvz

|-
|| fastvps.ru
|| [http://mirror.fastvps.ru/openvz/ http]
| align="center" | —
|| Germany, Falkenstein, DC: Hetzner Online AG
|| Updated hourly

|-
|| tocici.com
|| [http://mirror.tocici.com/openvz/ http]
| align="center" | —
|| US, Oregon, Portland
|| Updated every four hours, with a randomized start time. Two 1Gbps uplinks leveraging dual-stack IPv4/IPv6.

|-
|| Webtastix Internet Services
|| [http://mirror.webtastix.net/openvz/ http]
|| [ftp://mirror.webtastix.net/openvz/ ftp]
|| New Zealand, Auckland
|| Updated hourly

|-
|| Colocall Internet Data Center
|| [http://ftp.colocall.net/pub/openvz/ http]
|| [ftp://ftp.colocall.net/pub/openvz/ ftp]
|| Ukraine, Kiev
|| updated hourly

|-
|| Interneto Vizija
|| [http://openvz.mirror.serveriai.lt/ http]
| align="center" | —
|| Lithuania, Vilnius
|| updated hourly

|-
|| Ionic
|| [http://ovz.ionic.net.pl http]
| align="center" | —
|| Poland, Kraków
|| updated every 24 h

|-
|| University of Science and Technology of China
|| [http://mirrors.ustc.edu.cn/openvz/ http]
|| [ftp://mirrors.ustc.edu.cn/openvz/ ftp]
|| Hefei, Anhui, China
|| updated every 6 hours rsync:mirrors.ustc.edu.cn::openvz

|-
|| VinaHost Co., Ltd
|| [http://mirrors.vinahost.vn/openvz/ http]
| align="center" | —
|| Ho Chi Minh City, Viet Nam
|| Updated hourly

|-
|| Neterra LTD
|| [http://mirrors.neterra.net/openvz http]
|| [ftp://mirrors.neterra.net/openvz ftp]
|| Bulgaria, Sofia
|| IPv6 enabled, 2 gbps link, Updated hourly rsync://mirrors.neterra.net/rsync

|-
|| vpsFree.cz
|| [http://mirror.vpsfree.cz/openvz http]
|| [ftp://mirror.vpsfree.cz/openvz ftp]
|| Czech, Prague
|| Updated hourly rsync://mirror.vpsfree.cz/openvz

|-
|| BangmodEnterprise Co., Ltd.
|| [http://mirrors.bangmodhosting.com/openvz http]
| align="center" | —
|| Thailand, Bangkok
|| updated every 4 hours

|-
|| maeh.org
|| [http://mirror.maeh.org/openvz/ http]
|| [ftp://mirror.maeh.org/openvz/ ftp]
|| Germany, Hamburg
|| updated hourly

|-
|| reliablefilehost.com
|| [http://openvz.reliablefilehost.com/ http]
| align="center" | —
|| USA, Vermont
||

|-
|| scalabledns.com
|| [http://mirror.scalabledns.com/openvz http]
| align="center" | —
|| USA, California, Los Angeles
|| 10 Gbps Uplink, updated hourly

|-
|| GloVine.com.au
|| [http://openvz.syd.au.glomirror.com.au http]
| align="center" | —
|| Sydney, Australia
|| updated every 6 hours
|}

== Create a mirror ==

If you want to mirror OpenVZ site, see [[Setting up a mirror]].

[[Category: Installation]]
[[Category: Infrastructure]]
[[Category: Download]]

Talk:028 to 042 kernel upgrade

2013-10-30T08:08:33Z

Paparaciz: Created page with "is it requirement to convert filesystem to ext4? or is it only to have support of ploop?"

is it requirement to convert filesystem to ext4? or is it only to have support of ploop?

028 to 042 kernel upgrade

2013-10-30T07:32:18Z

Paparaciz: now should look better

This article describes a way to upgrade your old OpenVZ system with RHEL5-based
(028stabNNN kernel) to RHEL6-based (042stabNNN) kernel, and convert /vz
from ext3 to ext4.

Assumptions:
* systems is CentOS (RHEL) 5.x
* vzkernel is 028stabXXX, i.e. RHEL5-based
* /vz uses ext3

End result should be:
* Same CentOS 5 system
* vzkernel is 042stabXXX
* /vz uses ext4

== Update your system ==

yum update

== Add rhel6 kernel repos ==

Disable rhel5 and enable rhel6 OpenVZ kernel repository.
In other words, change <code>/etc/yum.repos.d/openvz.repo</code>
to look like this (changes required are '''in bold'''):

[openvz-kernel-rhel6]
name=OpenVZ RHEL6-based stable kernels
<nowiki>#baseurl=http://download.openvz.org/kernel/branches/rhel6-2.6.32/current/</nowiki>
<nowiki>mirrorlist=http://download.openvz.org/kernel/mirrors-rhel6-2.6.32</nowiki>
'''enabled=1'''
gpgcheck=1
<nowiki>gpgkey=http://download.openvz.org/RPM-GPG-Key-OpenVZ</nowiki>
'''#exclude=vzkernel-firmware'''

[openvz-kernel-rhel5]
name=OpenVZ RHEL5-based kernel
<nowiki>#baseurl=http://download.openvz.org/kernel/branches/rhel5-2.6.18/current/</nowiki>
<nowiki>mirrorlist=http://download.openvz.org/kernel/mirrors-rhel5-2.6.18</nowiki>
'''enabled=0'''
gpgcheck=1
<nowiki>gpgkey=http://download.openvz.org/RPM-GPG-Key-OpenVZ</nowiki>

== Install new OpenVZ kernel ==

# yum install vzkernel.x86_64

== Check bootloader configuration ==

Make sure 042stab kernel is there and will boot by default:

cat /boot/grub/grub.conf

timeout 5
default 0
title OpenVZ (2.6.32-042stab081.8)
root (hd0,1)
kernel /vmlinuz-2.6.32-042stab081.8 ro root=/dev/sda3 vga=0x317 selinux=0 sysfs.deprecated=1
initrd /initrd-2.6.32-042stab081.8.img

title OpenVZ (2.6.18-348.16.1.el5.028stab108.1)
root (hd0,1)
kernel /vmlinuz-2.6.18-348.16.1.el5.028stab108.1 ro root=/dev/sda3 vga=0x317 selinux=0
initrd /initrd-2.6.18-348.16.1.el5.028stab108.1.img
....

== Reboot into new kernel ==

# reboot

and make sure the system is up and running.

== Convert /vz to ext4 ==

Boot node from a live-CD (such as, CentOS 6 live CD) and perform the following steps.

Check file system:
# fsck.ext3 -f /dev/sd''xY''

Turn on ext4 features:
# tune2fs -O extents,uninit_bg,dir_index /dev/sd''xY''

Check the new file system again, as ext4 this time:
# fsck.ext4 -fD /dev/sd''xY''

You can do the same for root filesystem, too.

Now, mount your ROOT (<code>/</code>, not <code>/vz</code>) and BOOT partitions:
# mkdir /tmp/root
# mount /dev/sd''aB'' /tmp/root
# mount /dev/sd''aC'' /tmp/root/boot

Finally, chroot into it:
# chroot /tmp/root

Edit its <code>/etc/fstab</code>, replacing <code>ext3</code> with <code>ext4</code> for <code>/vz</code> (and <code>/</code> if you converted it as well).
# vi /etc/fstab

== Create new initrd with proper modules ==

This assumes you are still entered chroot:

# mkinitrd -v -f --with=ext4 --builtin=ehci-hcd --builtin=ohci-hcd --builtin=uhci-hcd \
/boot/initrd-2.6.32-042stab81.8.img 2.6.32-042stab081.8

Notes:
* you have to add ext4 explicitly
* in RHEL6 kernels some USB stuff (that used to be in ehci-hcd, ohci-hcd, uhci-hcd modules) is built-in

== Reboot and enjoy ==

End result is:

# cat /etc/issue
CentOS release 5.10 (Final)
Kernel \r on an \m

# uname -a
Linux CentOS-58-64-minimal 2.6.32-042stab081.8 #1 SMP Mon Sep 30 16:52:24 MSK 2013 x86_64 x86_64 x86_64 GNU/Linux

# df -Th
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda3 ext4 259G 1.5G 244G 1% /
tmpfs tmpfs 16G 0 16G 0% /dev/shm
/dev/sda2 ext3 496M 46M 425M 10% /boot
/dev/sdb1 ext4 1.8T 196M 1.7T 1% /vz

== See also ==

* [[Quick installation]]

== Acknowledgements ==

This article was originally written by [[User:Denis Hohryakov|Denis Hohryakov]].

[[Category: HOWTO]]

028 to 042 kernel upgrade

2013-10-30T07:24:20Z

Paparaciz: fix link to user page

Hosting providers

2013-10-08T05:40:48Z

Paparaciz: fixed formatting

OpenVZ makes for a great hosting platform for VPS hosting. The providers below offer VPS services using OpenVZ.


== Argentina ==

* [http://www.g2khosting.com/ G2K Hosting] We offers OpenVZ containers with high level hardware technology from 25 US with Control Panel, various Linux Dists and full support.
* [http://www.ihserver.net/ IHServer] Specialized virtualization on OpenVZ containers at Gigared datacenter. We have in Argentina one of the better fiber connection to the US, but also provides services from LSTN in Texas.

== Austria ==

* [http://www.austrosolutions.at/ AustroSolutions] offers fast OpenVZ containers with unlimited traffic.
* [http://www.delimitervps.com Delimiter] DelimiterVPS offers VPS's in 20+ cities with unlimited bandwidth, zero overselling, choice of all major Linux distros. 1.5GB RAM, 100GB Disk, Unlimited Traffic $20/month. Second month is free with promo code
* [http://www.edis.at/ EDIS] EDIS offers business OpenVZ containers in Austria (as well as other virtualization technologies in 17+ countries worldwiede)
* [http://kapper.net/ kapper.net] kapper.net offers OpenVZ and Virtuozzo (and other HyperVisors) based server-solutions with kind support and 24x7 maintenance.
* [http://www.snb.at/ SNB] offers OpenVZ containers and support's also existing vm's in customers environment
* [https://www.vboxes.net/ vboxes] vboxes offers generous OpenVZ containers hosted on a very fast network with fast setup. Ubuntu, Debian, CentOS.
* [http://www.waveride.at/ Waveride] Waveride, an EDIS company, offers budget full gigabit OpenVZ + solusVM VPS in Austria

== Brazil ==

* [http://www.datacorporate.com.br/ DataCorporate] OpenVZ cheap and fast, clustered solution on our own datacenter, instanst signup and install, over 10 popular templates.
* [http://www.globalmedia.com.br/ GlobalMedia] We offers OpenVZ containers hosted on a very fast network with fast setup. Ubuntu, Debian, CentOS.

== Bulgaria ==

* [http://www.bul.net/ Bul.net] Provides OpenVZ based VPS, perfect user/VPS management via [http://ispsystem.com VDSManager]. Instant creation after online payment. Debian/Ubuntu/CentOS with ISPManager Control panel. Optimal price policy.
* [http://www.cointech.eu/vps-hosting/ CoInTech] provides OpenVZ based VPS containers, free webmin managment. Containers can be CentOS, Slackware, Ubuntu, custom or our special [http://www.mandriva.com Mandriva Linux] container with own [http://mandriva.cointech.net repository].
* [http://www.rax.bg/ RAX.bg] Offers OpenVZ based VPS, hosted on a clustered infrastructure and redundant network. Easy to use user management, Instant setup, CentOS (OS).
* [http://www.jump.bg/ Jump.bg] Provides OpenVZ VPS servers hosted on a redundant network which provides a very easy to manage platform for all clients which gain instant access to their OS ( Ubuntu, CentOS , Debian etc ... )
* [https://www.fitvps.com/ FitVPS.com] Offers affordable and reliable OpenVZ based VPS in Varna, Bulgaria. Own data center, own multihomed network, with SLA. Instant automatic setup, SolusVM control panel.
* [http://www.qhoster.com/ QHoster.com] Instant activation OpenVZ VPS in UK, USA, Germany, France and Switzerland. Both 32/64 bit OpenVZ OS VPS templates : CentOS 5/6, Debian 6/7, Ubuntu 12/13.

== Canada ==

* [http://compevo.com compevo Clustered VPS Server Hosting Provider] - We offer clustered VPS Servers to avoid downtime and dataloss. Our network and service is second to none and is used by businesses around the world.
* [http://www.datacorporate.ca/ DataCorporate] OpenVZ cheap and fast, clustered solution on our own datacenter, instanst signup and install, over 10 popular templates.
* [http://www.delimitervps.com Delimiter] DelimiterVPS offers VPS's in 20+ cities with unlimited bandwidth, zero overselling, choice of all major Linux distros. 1.5GB RAM, 100GB Disk, Unlimited Traffic $20/month. Second month is free with promo code
* [http://www.letstalkdigital.com/index.php?option=com_content&view=article&id=73&Itemid=65 LetsTalkDigital VPS Hosting] LetsTalkDigital.com offers both OpenVZ and XEN™ based VPS technologies. Cheap Linux and Windows VPS Hosting, start from $14.99. Virtual Private Server (VPS) hosting is for those who want the control and flexibility of a dedicated server at a much lower cost. All VPS packages come with a web hosting control panel option such as cPanel™, full root user access and all the features listed below, with 24/7 customer service.
* [http://secure.media-hosts.com/link.php?id=7 Media-Hosts.com] Provides Quality and Scalable OpenVZ based Virtual Private Servers. 100% network uptime guaranteed. Located in Montreal Quebec with 5 Tier1 upstream providers.
* [http://www.openvz.ca OpenVZ.ca] Canadian Budget VPS Servers on OpenVZ Platform.
* [http://protoserver.com ProtoServer] Advanced VPS Hosting from $4.95/month. Many pre-installed VPS Templates available (CMS, E-commerce, Web development, Online community, Media streaming, etc.) No bundles or service plans - mix VPS resources as needed and change VPS configuration anytime. Also offering DNS Hosting, E-mail hosting, Domains Registration.
* [http://www.vistapages.com/vps Vistapages VPS] - IBM & Dell Hardware. MCI/Verizon Backbone. Distros: Centos, Fedora, Debian & more. Full management available. Located in Toronto.
* [http://vpsville.ca/ VPSVille] - Good network. Good CPU. Good choice of distros: Centos, Fedora, Debian, Ubuntu, Slackware, Gentoo, OpenSUSE, CERN. My favorite OpenVZ provider. [mailto:jak@isp2dial.com John Kelly]

== Colombia ==

* [http://www.datacorporate.co/ DataCorporate] OpenVZ cheap and fast, clustered solution on our own datacenter, instanst signup and install, over 10 popular templates.
* [http://www.soficol.com/ Soficol] Offers Enterprise OpenVZ based VPS, hosted on a clustered infrastructure and redundant network. Easy to use user management and instant setup.

== Czech Republic ==

* [http://www.hukot.cz Hukot.cz] - OpenVZ VPS Servers starting from 2.92 €, XEON, 1 Gbps uplink, unlimited traffic. Debian, Ubuntu, CentOS, Scientific, SuSe, Fedora, Elastix.
* [http://www.ultimatehosting.eu UltimateHosting.eu] - OpenVZ VPS Servers starting from $8 with custom configuration - up to 100 GB HDD, 2048 MB RAM, 2 GHz CPU, and unlimited traffic.
* [http://4smart.cz 4Smart.cz] - prepaid, you are charged only by the system resources you use, therefore you can run a VPS for as little as 1 EUR a month if your vps is not resource hungry. Even if you pay 0,50 EUR month, you still have 3 GB of RAM and 8 cores available to you VPS.
* [http://www.freecloud.cz FREECLOUD.CZ] - Free OpenVZ VPS Server - own IP, 800Mhz CPU, 512MB RAM, 50Mbits LAN, 10GB HDD, 100GB Traffic - Debian, Ubuntu, Gentoo, Slackware, Fedora, Centos

== Chile ==

* [http://www.dch.cl/ hosting] - DCH.cl Hosting Chile - High Performance VPS Servers with OpenVZ
* [http://www.hostingnic.cl/ hosting Chile] - HOSTINGNIC.cl Chile - Professional Linux OpenVZ VPS

== France ==
* [http://www.BargainVPS.co.uk/ BargainVPS] - UK / US / EU Instant setup VPS - We have some great Linux & Windows Bargain VPS packages on offer for you here all available Fully Managed.
* [http://www.cinfu.com/vps/ Cinfu] offers budget, unmanaged, unmetered, OpenVZ based VPS servers in France from 1.88EUR/month.
* [http://www.Freaksol.com/ FreaKs VPS Hosting] Self reliant hosted on independent networks & DC low ping,No restrictions on file types,Unlimited resources,high ram servers
* [http://www.harmony-hosting.com Harmony-Hosting] A high performance VPS hosting - The leader in France
* [http://www.minivps.co.uk miniVPS] miniVPS offers VPS hosting solutions with nodes located in France, utilising openvz/solusvm with future locations of USA and UK.
* [http://www.delimitervps.com Delimiter] DelimiterVPS offers VPS's in 20+ cities with unlimited bandwidth, zero overselling, choice of all major Linux distros. 1.5GB RAM, 100GB Disk, Unlimited Traffic $20/month. Second month is free with promo code
* [http://www.lws.fr/serveur_dedie_linux.php LWS - Linux VPS ] - Linux VPS Hosting - Only 9.99€/month, Affordable and Secure OpenVZ VPS Servers with 99.99% up-time, web hosting control panel Included. French datacenter
* [http://www.1euro-hosting.eu BEST EU VPS - 1€ Hosting] - Providing reliable and secure OpenVZ VPS Servers with 99.99% up-time, starting from 8€

== Germany ==

* [http://www.b2b-hosting.de/vps/ B2B Hosting]: Professional virtual servers for business applications. Performance and reliability at a fair price. Made with OpenVZ.
* [http://www.cinfu.com/vps/ Cinfu] offers budget, unmanaged, unmetered, OpenVZ based VPS servers in Germany from 1.88EUR/month.
* [http://www.delimitervps.com Delimiter] DelimiterVPS offers VPS's in 20+ cities with unlimited bandwidth, zero overselling, choice of all major Linux distros. 1.5GB RAM, 100GB Disk, Unlimited Traffic $20/month. Second month is free with promo code
* [http://afterburst.com Afterburst (Previously FanaticalVPS)]: affordable unmetered, unmanaged VPS servers in Germany.
* [http://www.hostingjuice.com/ HostingJuice] The Superioum VPS and Web Hosting provider, low prices - Premium packages.
* [http://www.ingate.de/managed-server.html Ingate] offers managed servers with openVZ virtualization. located in germany, great support.
* [http://www.serverbiz.de/vserver Serverbiz] Powerful VPS at very low prices.
* [http://www.synapseglobal.com/voip_vps.html SynapseGlobal.com] Elastix, Trixbox, PBX in a Flash and Asterisk VPS - OpenVZ based Asterisk VOIP servers located in Munich Germany.
* [http://www.vStarVPS.com vStarVPS]: Reliable VPS Hosting at lowest prices, with 99.9% uptime, Premium Unmetered Bandwidth and Custom HDD/RAM of your choice. Instant and FREE Setup. RapidLeech Allowed.
* [http://whynotavps.com WhyNOTaVPS]: Instant activated VPS SERVERS!!
* [http://hostmist.com/openvz-vps-germany.html Host Mist]: features budget OpenVZ VPS hosting in Germany.

== Guatemala ==
* [http://www.globalnetcafe.com/gnc/menu/hospedaje.htm Global Net Cafe]: Servicios de hospedaje, reseller, vps, colocacion y servidores. Incluyendo OpenVZ.

== Hong Kong ==

* [http://www.delimitervps.com Delimiter] DelimiterVPS offers VPS's in 20+ cities with unlimited bandwidth, zero overselling, choice of all major Linux distros. 1.5GB RAM, 100GB Disk, Unlimited Traffic $20/month. Second month is free with promo code
* [http://vps.timway.com/linux_vps.html Timway VPS Hosting] - Quality, non-oversold hosting provider focused on being security conscious and offering a positive client experience. Centos, Debian, Fedora, OpenSuse and Ubuntu Containers are available.

== Hungary ==

* [http://elin.hu/index.php?menu=8&nyelv=hu&cim=Virtualis-szerver Virtual server] OpenVZ server: 2xX5650 Intel Xeon, 32GB RAM, 15.000rpm SAS disks, 100Mbit/s, unlimited bandwith.
* [https://www.ivirtual.co/vps-hosting/ iVirtual.co ] OpenVZ Master Server: 2x Intel Xeon @ 3.0GHZ, 64 GB ECC Ram, 15k RPM SAS HDD's, 1Gbit/s Network, Unlimited bandwith.

== India ==
* [http://pve.proxmox.com/wiki/User:Apmuthu Ap.Muthu] sponsored by [http://www.gnuacademy.org GNUAcademy], [http://www.planettel.com.sg PlaNetTel] and [http://www.sacollege.net S A College] creates OpenVZ Templates for the Open Source Community and provides hosting in datacenters of clients choice or on site.

* [http://www.milesweb.com/vps-hosting.php Milesweb VPS Hosting] VPS hosting offered by Milesweb are powered by ''VMware, OpenVZ''. Fully Managed VPS with control panels.

* [http://www.Freaksol.com/ Freaksol VPS Hosting] Self reliant hosted on independent networks & DC low ping to India,No restrictions on file types,Unlimited resources,high ram servers

* [http://overlineindia.net/vpshosting-p-62.html Overline India VPS Hosting] Fully managed cPanel Installed VPS Hosting with 24x7x365 Live Chat Tech support, powered by OpenVZ

* [http://vpsbeach.com VpsBeach Managed Hosting] Fully managed cPanel Installed VPS Hosting with 24x7x365 Live Chat Tech support, powered by OpenVZ

* [http://www.datacorporate.in/ DataCorporate] OpenVZ cheap and fast, clustered solution on our own datacenter, instanst signup and install, over 10 popular templates.

* [http://www.servers.co.in/vps/vps_hosting.php Server Web Hosting] Offers Fully Managed OpenVZ VPS Web hosting in India/US/UK at affordable and cheap rates with best hardware quality and customer service 24/7/365 days

* [http://www.hioxindia.com/virtual-private-server.php VPS Hosting] Reliable and quality VPS Virtual Private Server Hosting

* [http://www.prohosterz.com/linux-vps.php ProHosterZ VPS Hosting] Reliable and quality Virtual Dedicated Servers | Virtual Private Servers | XEN VPS | OpenVZ VPS | Virtual Hosting

== Iran==

* [http://www.ehost.ir EHost.ir] - OpenVZ Servers , DUAL XEON Cpus , 12 Gb Ram , 100Mbit Dedicated Connection , SAS HardDisk
* [http://www.vpsfa.ir VPSFa.ir] - OpenVZ Servers , DUAL XEON Cpus - , 24Gb Ram , 1000Mbit Dedicated Connection , SAS HardDisk

== Italy ==

* [http://www.hosting-italia.net hosting italia] - OpenVZ Servers and panel enduser Virtualizor Intel® Core™ i7-920 Quad-Core 48 GB DDR3 RAM - Guaranteed Bandwidth 200 Mbit/s

== Latvia ==

* [http://www.altnet.lv/ Altnet] - Hosting and colocation services. Any flawor, you name it.

== Lithuania ==

* [http://www.databank.lt/ databank.lt] - high-quality professional OpenVZ hosting with cloud computing solutions.
* [http://www.cloudlix.com/ CloudLix.com] - Managed and unmanaged OpenVZ virtual servers based on 2.6.32 kernel. Up to 20GHz (Intel SandyBridge) CPU and 10GB RAM. Located in Vilnius and Siauliai.
* [http://www.serveriai.lt/ Serveriai.lt] - Affordable OpenVZ containers on quality HP hardware. Wide choice of virtual dedicated servers up to 8 CPU cores and 8 GB RAM. Full management available. Located in Vilnius.
* [http://www.time4vps.eu/ Time4VPS.EU] - Powerful cloud technology based infrastructure will let you build custom virtual machine and pay only for what you really need. Located in Vilnius city.

== Malaysia ==

* [http://www.bakka.my/ Bakka Hosting] - OpenVZ VPS based in Malaysia. Ubuntu, Debian, Fedora, CentOS is available. Quad Core Xeon node. DirectAdmin also available.
* [http://www.cubiex.com/ Cubiex] - Malaysia Affordable Web Hosting and Domain Name. Affordable Linux VPS Hosting in Malaysia. OpenVZ based, Quad Core Xeon node. cPanel/WHM and DirectAdmin also available.
* [http://www.delimitervps.com Delimiter] DelimiterVPS offers VPS's in 20+ cities with unlimited bandwidth, zero overselling, choice of all major Linux distros. 1.5GB RAM, 100GB Disk, Unlimited Traffic $20/month. Second month is free with promo code

== Malta ==
* [http://www.a6it.com/ A6iT] - Stable, quality managed OpenVZ VPSs based in Malta. Redundant network.

== Morocco ==
* [http://www.belsemtech.com/ BelsemTech.CoM] BelsemTech SARL offers both OpenVZ and XEN™ based VPS technologies. Cheap Linux and Windows VPS Hosting, start from 300 DH. Virtual Private Server (VPS) hosting is for those who want the control and flexibility of a dedicated server at a much lower cost. All VPS packages come with a web hosting control panel option such as cPanel™, full root user access and all the features listed below, with 24/7 customer service.
* [http://www.hostoweb.com/ HosToWeb] is the only company providing VPS hosting in Morocco Data Center.
* [http://www.adk-media.com/ ADK Media] provides affordable managed and unmanaged virtual servers based on OpenVZ, Xen Paravirtualization and Xen HVM platforms. 24/7 Technical Support. Distros: Centos, Fedora, Debian, Ubuntu and more.
* [http://www.naja7host.com/ Naja7Host.CoM] The Naja7host SARL provides affordable VPS hosting using the OpenVZ platform. Running on Full Quality Nodes of up to 8 CPU and 16 GB RAM. . All VPS's come with Real 24/7/365 Technical Support and cPanel free (if option selected ). Multiple choice of OS 32/64Bits (Centos, fedora, ubuntu, debian .ect ...)

== Netherlands ==

* [http://www.avanpad.com/ Avanpad] offers OpenVZ VPS hosting with 24\7 online support. Customer can request different control panels or templates for installation on his VPS.
* [http://www.cinfu.com/vps/ Cinfu] offers budget, unmanaged, unmetered, OpenVZ based VPS servers in Netherlands from 1.88EUR/month.
* [http://www.delimitervps.com Delimiter] DelimiterVPS offers VPS's in 20+ cities with unlimited bandwidth, zero overselling, choice of all major Linux distros. 1.5GB RAM, 100GB Disk, Unlimited Traffic $20/month. Second month is free with promo code
* [http://www.Freaksol.com/ FreaKs VPS Hosting] Self reliant hosted on independent networks & DC low ping around the world,No restrictions on file types,Unlimited resources,high ram servers
* [http://iniz.com/ INIZ VPS Hosting] INIZ provides affordable VPS Hosting in Amsterdam, Netherlands with high resources at low prices.
* [http://www.osbox.nl OsBoX Dutch Network Engineering] Cheap VPS host as low as $1 per month. Very great uptime and a overall good support. Check the website for the server plans.
* [http://www.signet.nl/ Signet VPS Hosting] - Signet delivers VPS hosting plans based on CentOS or Debian templates, including control-panel Virtualmin.
* [http://simple-webhosting.eu/ Simple-webhosting.eu] - OpenVZ based web hosting starting from €0.98 per month.
* [http://www.touchvps.com/ TouchVPS] is a company who offer Support and Managed Services for OpenVZ Servers ,also offer templates for openvz ready to go with cPanel , DirectAdmin , Plesk , Games, IRC Services, Desktop and many more.
* [http://www.voipcomplete.com/product-overview/dedicated-vps.html VOIPcomplete] offers dedicated VPS plans based on CentOS including a VPS management interface.
* [http://www.waveride.at/ Waveride] Waveride, an EDIS company, offers budget full gigabit OpenVZ + solusVM VPS from their Schiphol-Rijk location in Holland

== Poland ==

* [http://hosteam.pl/ HosTeam] offers OpenVZ VPS hosting from their DataCenter in Poland. Customer has choice of all major Linux distros (WARNING!!! restoring your backup is VERY expensive and they charge even if it wasn't restored correctly!), NATIVE IPV6 AVAILABLE!

* [http://ultimahost.pl/ UltimaHost] high grade OpenVZ VPS and FreeBSD jail (DC in Łódź, Poland), brand of statnet.pl, SSD available for more expensive packets, NO IPV6 AVAILABLE (but they can load you tun module)

* [http://budgetvps.pl/ BudgetVPS] very cheap, low end grade OpenVZ VPSes (DC in Gdańsk, Poland), brand of hitme.net.pl

* [http://hitme.net.pl/ HitMe] high grade OpenVZ/Xen PV/Xen HVM VPSes (DC in Gdańsk, Poland), NATIVE IPV6 AVAILABLE (/64 on demand for free)!

* [http://www.kr-cpd.pl/oferta/serwery-vps/ KR-CPD] Cracow's Center of Data Processing (DC of course in Cracow, Poland)

* [http://livenet.pl Livenet] cheap, middle/low end OpenVZ VPSes (DC in Łódź, Poland)

* [http://slaskdatacenter.pl/ Śląsk Data Center] high/middle grade OpenVZ VPSes (DC in Silesia province, Poland), SSD available for more expensive packets

== Portugal ==

* [http://www.ptservidor.pt/ PTServidor] - OpenVZ virtual servers with free management based in Portugal.
* [http://www.efeito.net/ Weblevel.pt] - OpenVZ virtual servers based in Portugal.

== Romania ==
* [http://www.intovps.com IntoVPS] - offers unmanaged OpenVZ virtual servers based in Romania, Netherlands and USA. A lot of resources for decent prices.
* [http://www.ename.ro/dedicated.html eName] - managed OpenVZ virtual servers in Bucharest, Romania
* [http://www.ch-center.com/virtual-servers Ch-center] - unmanaged OpenVZ virtual servers, based in Romania in it's own Data Center

== Russia ==
* [http://www.ihc.ru/vps.html IHC.RU] - VPS hosting in Moscow, Russia starting at $10/month with good set of precreated templates
* [http://mchost.ru/services/linux-vps/ McHost.ru] - Linux VDS Hosting from McHost.
* [http://hosting.agava.ru/vps/ AGAVA] - Linux VPS hosting based on OpenVZ.
* [http://vdsplanet.ru/ VDSPlanet.ru] - unmanaged VDS/VPS hosting starting at 3.99$ a month. Large variety of OS templates and free ISPmanager Lite control panel. Total automation is our goal.
* [http://www.demos.ru/service/datacenter/vps.html Demos-Internet] - we offer OpenVZ Virtual Private Server based on Linux. All VPS come with ISPmanager control panel.
* [http://www.net.ru/service/net9/ www.net.ru] - OpenVZ virtual private servers.
* [http://www.eurobyte.ru/ Eurobyte.ru] - Linux VDS Hosting from Eurobyte.
* [http://www.telekom.ru/service/vps.html Elvis Telekom] - OpenVZ hosting with base and cpanel templates from Elvis Telekom.
* [http://fastvps.ru/vds/ FastVPS] - OpenVZ hosting, ISPmanager, Hetzner, MayFlower.
* [https://lepus.su/vps.html Lepus] - OpenVZ hosting, SSD, ISPmanager free, Hetzner.

== Singapore ==
* [http://www.qoxy.com/vps QOXY.com] Affordable and Reliable OpenVZ VPS Hosting in a Singapore Data Center.
* [http://conceptlane.com/IT.php?section=plans_vps ConceptLane Pte Ltd] - OpenVZ VPS on dual hexa-core AMD Opterons running Debian Squeeze 6, custom control panel with bandwidth graphs, reboot/reinit and web-based VNC access.
* [http://www.delimitervps.com Delimiter] DelimiterVPS offers VPS's in 20+ cities with unlimited bandwidth, zero overselling, choice of all major Linux distros. 1.5GB RAM, 100GB Disk, Unlimited Traffic $20/month. Second month is free with promo code
* [http://www.secureax.com/ SecureAX Internet] - Singapore Premium Internet Solution Provider
* [http://www.planettel.com.sg PlaNetTel] - Affordable and customised OpenVZ containers across 3 data centers - contact Thomas Festus at +65-66936881. [http://pve.proxmox.com/wiki/User:Apmuthu#Squeeze_based_Templates Sponsors OpenVZ Container Template]s for the Open Source community.

== South Africa ==
* [http://www.vps.co.za/ VPS.CO.ZA] - South Africa's oldest VPS provider. Local South African servers with SolusVM control panel. OpenVZ, Xen and OnApp Cloud.
* [http://247hosting.co.za/vpshosting.php 247Hosting] - OpenVZ virtual servers locally in South Africa with SolusVM control panel. cPanel option available!
* [http://www.SoftDux.co.za/ SoftDux] - OpenVZ virtual servers based America & South Africa. All VPS's come with cPanel or Plesk control panels. XEN VPS's also available.
* [http://www.clickworks.co.za/ Clickworks] - OpenVZ / Xen VPS servers hosted in RSA. Backed by Solusvm control panel.
* [http://www.elitehost.co.za/ Elite Host] - OpenVZ virtual servers based in America & South Africa. All VPS's come with cPanel and unlimited bandwidth.
* [http://www.telasera.com/ Telasera] - OpenVZ VPS servers hosted in South Africa. Supermicro Servers powered by Intel Xeon with 24/7 Support.

== Spain ==
* [http://www.corpresa.com/servidores-virtuales.html Corpresa Hosting] - Tiene algún proyecto entre manos y un plan de hosting no le hes sufuciente y un servidor dedicado no está dentro de su presupuesto?, una solución de VPS a medida será la que cubrirá todas sus necesidades."

== Sweden ==
* [http://acon.se/vps Acon VPS Server] - VPS Server and Dedicated server provider in Sweden.
* [http://www.delimitervps.com Delimiter] DelimiterVPS offers VPS's in 20+ cities with unlimited bandwidth, zero overselling, choice of all major Linux distros. 1.5GB RAM, 100GB Disk, Unlimited Traffic $20/month. Second month is free with promo code
* [http://glesys.com GleSYS] - VPS Provider with a great control panel and good prices
* [http://www.quickvz.com QuickVZ] - Premium VPS Hosting Provider. Offer enterprise-class features (e,g. IPSec VPNs, Externalized Backups, PVLANs).
* [https://virtualcenter.se VirtualCenter] - The first Cloud provider with SSD VPS in Sweden. Offer enterprise class hardware and network infrastructure

== Switzerland ==
* [https://www.rackster.ch/vps Rackster Internet Services] Business scaled OpenVZ hosting provider in Switzerland since 2011.

== Tanzania==
* [http://www.aptus.co.tz/ Aptus Solutions] - OpenVZ / SolusVM VPS Servers located in Dar es Salaam - 100meg to TIX. CentOS & Ubuntu.

== Turkey ==
* [http://www.7x24web.net/ 7x24 WEB SERVICES] - We're offering Linux virtual servers with OpenVZ kernel (SolusVM management) and Windows Virtual Servers under KVM.

* [http://www.istanbulhost.com/ istanbulhost] - OpenVZ managed and unmanaged VPS servers. Centos[4/5] / Fedora[5/6/7/8/9/10/11/12] / Debian[3/4/5] / Ubuntu[8.04/9.10/10.04]

* [http://www.host.net.tr/ Hosting] - OpenVZ managed unmanaged VPS hosting servers. Centos[5] / Debian[3/4/5] / Ubuntu[8.04/9.10/10.04]
* [http://www.web-hosting.net.tr/ Web Hosting] - OpenVZ managed and unmanaged VPS hosting servers. Centos[5] / Debian[3/4/5] / Ubuntu[8.04/9.10/10.04]

== UK ==

* [http://www.hostxnow.com/ HostXNow] - Fast, reliable, premium quality fully managed UK based VPS (virtual private servers) starting from just £32.95 a month, running since 2009.
* [http://www.AceShells.com/ AceShells] - Fast, stable, high quality UK based virtual private servers from just £5 a month, operating since 2001
* [http://www.BargainVPS.co.uk/ BargainVPS] - UK / US / EU Instant setup VPS - We have some great Linux & Windows Bargain VPS packages on offer for you here all available Fully Managed.
* [http://www.cheapvps.co.uk/ CheapVPS] - CheapVPS provide cheap, UK based OpenVZ VPS servers. Hosted on high end hardware, in a top UK datacenter backed up with 24/7/365 support. Choice from a wide range of Linux distros. OpenVZ VPS managed with SolusVM.
* [http://www.chilliserver.com/ Chilliserver] - Affordable plans starting from just £3.99, not oversold. RHEL6 Kernel with VSwap, TUN/TAP/FUSE and ACL support enabled. SolusVM control panel with custom snapshot system and rescue system. Based in a European data Centre with UK based support.
* [http://www.cislondon.co.uk/virtual-private-servers/ Commercial Internet Solutions] - CIS provides premium hosting at competitive rates, focused on Small Businesses within the M25 orbital. Hosting is on Dual Quad core Intel Xeon supermicro servers in Tier 4 datacenters around London.
* [http://www.datacorporate.co.uk/ DataCorporate] OpenVZ cheap and fast, clustered solution on our own datacenter, instanst signup and install, over 10 popular templates.
* [http://www.DubHosting.co.uk/ DubHosting] - DubHosting started in 2004 has been providing cost effective hosting to clients world wide. Fully managed OpenVZ servers based in Europe & US are one of their many strong points. They can provide you with a dedicated server and install openvz allowing you to sell your own vps servers. Their servers are located at UKGrid in Manchester with 24/7/365 support
* [http://www.delimitervps.com Delimiter] DelimiterVPS offers VPS's in 20+ cities with unlimited bandwidth, zero overselling, choice of all major Linux distros. 1.5GB RAM, 100GB Disk, Unlimited Traffic $20/month. Second month is free with promo code
* [http://www.europhase.net/virtual-private-servers/ Europhase UK Limited, UK VPS] - OpenVZ VPS Hosting, Virtual Dedicated Servers, UK VPS hosted at multiple UK datacentres from £4.99
* [http://www.farbyte.com/servers/openvzvps/ Farbyte UK VPS] - UK based OpenVZ VPS and shared web hosting services
* [http://www.fdqwholesale.co.uk FDQ Wholesale] - UK based hosting services
* [http://www.infrenion.com./uk_vps_hosting.html Infrenion Networks UK] Cheap, economical and reliable web hosting solutions, VPS based on the openVZ platform. You can host any YouTube Clone scripts with free FFMPEG setup on our vps servers. Also offers with a choice of selecting DataCenter.
* [http://www.letstalkdigital.com/index.php?option=com_content&view=article&id=73&Itemid=65 LetsTalkDigital VPS Hosting] - LetsTalkDigital.com offers both OpenVZ and XEN™ based VPS technologies. Cheap Linux and Windows VPS Hosting, start from $14.99. Virtual Private Server(VPS) hosting is for those who want the control and flexibility of a dedicated server at a much lower cost. All VPS packages come with a web hosting control panel option such as cPanel™, full root user access and all the features listed below, with 24/7 customer service.
* [http://www.phurix.co.uk/ Phurix] - A UK based web solutions company that provides you with reliable hosting at extremely affordable prices, VPS server virtualization using OpenVZ.
* [http://www.qualityservers.co.uk Quality Servers] - Affordable OpenVZ virtual servers based in the UK and USA. Choice of control panels and management options.
* [http://www.rshosting.co.uk/vps.html RSHosting UK] - Offering the most secure, reliable, stable and fast UK VPS Web Hosting based on OpenVZ architecture. Our Virtual Dedicated Servers are physically hosted on powerfull Quad Core servers located in multiple UK datacentres.
* [http://www.vpsmachine.co.uk/ vpsMachine] Quality openvz hosting platform with a large choice of customer OS templates.
* [http://www.webhosting.uk.net/linuxvps.html WebHostUK LTD] - Offers Cheap yet Best UK VPS Web Hosting working on OpenVZ Platform.We offers fully Managed UK VPS with true 24/7/365 days support.All our Servers are located in UK London DC.
* [http://www.webhostinguk.com/vps/vps-hosting.html Web Hosting UK] - Fully managed OpenVZ VPS Hosting offered on fast and reliable and affordable servers in UK & European datacenter with 24x7x365 days lightning fast support.
* [http://www.weycrest.co.uk/vps-hosting.php Weycrest VPS] - Low Cost, Stable OpenVZ and Parallels' Virtuozzo Virtual Private Server solutions. London UK Hosted at Coreix with a choice of operating systems, and root and control panel options.
* [http://www.xilo.net/virtual_private_servers-vps/ XILO] - UK-based hosting with UK-based support. VPS services offered with a choice of cPanel, Webmin and other useful applications, VoIP, SIP, VPN to name a few.
* [http://www.zxvps.co.uk/ ZxVPS VPS Hosting] - Quality, non-oversold VPS based on the openVZ platform, using SolusVM management panel, VPS from 128mb - 2gb, cpanel, direct admin, kloxo, etc.
* [http://www.meteorvps.com/ MeteorVPS] - Professional, Non-Oversold amazing VPS plans pretty cheap using SolusVM management, range from 512MB -> 16GB
* [http://www.chvps.com/ CHVPS] - Switzerland Based VPS, Cheap Pricing with solusVM control panel.
* [http://domvps.com/ domVPS] - OpenVZ Virtual Servers in the USA, Germany, France & the Netherlands at a low cost.
* [http://www.gemvps.net/ GemVPS.NET] - UK (Manchester) Based Company, OpenVZ Virtual Servers in the UK & France on Fast nodes.

== Ukraine ==
* [http://www.gelihost.com/ Geliar Hosting Solutions] - Fast virtual dedicated servers based on OpenVZ. Geliar Hosting Solutions offering many control panels and other useful services.
* [http://www.hostpro.ua/ Hostpro.ua] - Full managed OpenVZ servers.

== USA ==

* [http://www.a2hosting.com A2 Hosting] is your high-performance [http://a2hosting.com/openvz-vps-hosting OpenVZ VPS Hosting] provider. Design your perfect [http://a2hosting.com/vps-hosting VPS Hosting] account today! Featuring SwiftServers and SSDs with page load speeds up to 300% faster compared to standard drives.
* [http://www.afterburst.com Afterburst] (Previously FanaticalVPS): affordable unmetered, unmanaged VPS servers in Miami.
* [http://www.alienvps.com AlienVPS.com] is an Affordable OpenVZ Hosting Provider with over 100 OS templates to choose from. Offering Linux & Windows VPS's in New York and Las Vegas all VPSes are fully managed with 24/7 support, daily offsite backups, premium bandwidth, and SolusVM control panel. Pricing starts at just $5/month or $19/year.
* [http://www.alticon.net Alticon] has provided OpenVZ based VPS/VE hosting for over 2½ years. Many clients use OpenVZ based VEs as a cost effective solution for hosting highly secured, customized versions of ZenCart & WordPress. Other clients use OpenVZ for DNS mirroring, messages board hosting, and general use.
* [https://www.asurahosting.com/ AsuraHosting] offers powerful, reliable, and simple OpenVZ VPS to clients. AsuraHosting has a dedicated support team, and quality hosting; Pricing starts at just $5/month!
* [http://www.BargainVPS.co.uk/ BargainVPS] - UK / US / EU Instant setup VPS - We have some great Linux & Windows Bargain VPS packages on offer for you here all available Fully Managed.
* [http://basshost.com/ BassHost.com] For over 5 years Bass Host has been providing reliable OpenVz VPS to customers. Today clients from over 100 different countries trust BassHost's web hosting services.
* [http://beyondhosting.net BeyondHosting.net] High Performance OpenVZ Virtual Private Servers (VPS) Tier 1 US Datacenter.
* [http://www.cloudshards.com Cloud Shards] High Performance, reliable, stable and affordable OpenVZ Virtual Private Servers (VPS) in data centers across the USA.
* [https://customer.binarycpu.com Binary Computer Solutions] has provided OpenVZ based Virtual Private Server hosting for over 2 years. Network outages are a thing of the past, and oversold services are never heard of here. Built on solid technology, with infrastructure to match - Binary Computer Solutions will give you hosting you need, without the cost others ask for. Starting at $1.50/mo.
* [http://www.bittraffic.com/?cmd=vps BitTraffic] High Quality Hosting Solutions! Affordable, stable, reliable OpenVZ VPS Solutions!
* [http://www.bodhost.com/ Bodhost.com] Fast, Reliable and secure web hosting service with 24*7 free customer service.
* [http://www.buildyourvps.com/ BuildYourVPS.com] mix ‘n’ match your VPS; choose only the bandwidth, RAM, disk capacity, type of IP connection, level server redundancy, and the support/monitoring you want. [http://www.buildyourvps.com/ BuildYourVPS] is the 1st to offer you a highly-customized VPS solution, without making you pay for unused extra features.
* [http://www.byethost.com Byethost.com] offers OpenVZ based VPS Hosting as its main VPS solution, with the hypervm panel. Centos, Debian, Fedora, OpenSuse and Ubuntu Containers are available.
* [http://www.chhost.net/vps.htm CH Hosting VPS Hosting] CH Hosting or chhost.net offers OpenVZ based VPS Hosting. 24/7 Support. Upgrade/Downgrade your plan as needed on-the-fly without the risk of downtime. Since 2006. Non-Oversell
* [http://www.cinfu.com/vps/ Cinfu] offers budget, unmanaged, unmetered, OpenVZ based VPS servers in USA from 1.88EUR/month.
* [http://www.cortexnetworks.com/ CortexNetworks.com] Offering quality OpenVZ VPS's at budget prices. Offsite backups of containers. 64Bit servers with RAID10 storage.
* [http://www.damnvps.com/ DamnVPS.com] is an unmanaged VPS provider offering Xen HVM, Xen PV and OpenVZ based services in the UK and US.
* [http://www.datacorporate.com/ DataCorporate] OpenVZ cheap and fast, clustered solution on our own datacenter, instanst signup and install, over 10 popular templates.
* [http://www.delimitervps.com Delimiter] DelimiterVPS offers VPS's in 20+ cities with unlimited bandwidth, zero overselling, choice of all major Linux distros. 1.5GB RAM, 100GB Disk, Unlimited Traffic $20/month. Second month is free with promo code
* [http://www.DubHosting.com/ DubHosting] - DubHosting started in 2004 has been providing cost effective hosting to clients world wide. Fully managed OpenVZ servers based in Europe & US are one of their many strong points. They can provide you with a dedicated server and install openvz allowing you to sell your own vps servers.
* [http://www.evolucix.com/ Evolucix.com] Evolucix offers state of the art, professional, and reliable OpenVZ VPS solutions on top-notch hardware while providing quality support.
* [http://fanaticalvps.com FanaticalVPS]: affordable unmetered, unmanaged VPS servers in Pennsylvania.
* [http://www.fliphost.net Fliphost.net]: Powerful, affordable instant setup VPS systems. Servers based in Phoenix Az with another location coming soon.
* [http://www.frontrangehosting.com Front Range Hosting]: SSD Cached KVM & OpenVZ VPS Hosting Prices Start at 2.00/mo, located in Colorado Springs, Colorado.
* [http://glesys.se GleSYS] is a hosting company specialized in serverhosting. Also offering VPS hosting mainly based on OpenVZ. GleSYS has provided access to server and Cisco hardware for developers from OpenVZ to find problem with VLAN implementation.
* [http://goodealhosting.com/ GOODEALHOSTING.com] Quality Hosting Solutions! Provides affordable unmanaged/managed VPS based on OpenVZ! start from $10.00, real 24/7 support.
* [http://gothost.net GotHost.net] Providing OpenVZ based VPS Hosting with SolusVM. All nodes are Quad Core Xeon with RAID-10 for speed and redundancy. Budget plans starting at $7.99.
* [http://www.greengeeksvps.com/ GreenGeeks VPS Hosting] Green VPS Hosting. Dual Intel Xeon 64-Bit CPU's, DDR3 RAM, RAID-10 Storage Arrays. 24/7 Support. cPanel/WHM + more!
* [http://hostarmor.com HostArmor™] - is best known for low-cost and reliable shared hosting and dedicated servers. Recently the company expanded to offer OpenVZ virtual server plans at 8 worldwide locations, five in the U.S., one in Germany, one in France, and one in the Netherlands. VPS plans start at $13.99/month.
* [http://www.hostavps.com HostAVPS] - Providing Fully Managed VPS's on both the West & East Coast.
* [http://www.hostcolor.com Host Color] - OpenVZ based virtual servers hosted in a Tier 4 class data center based out of South Bend, Indiana. Juniper managed, fully-redundant network with uplinks to Level 3, Cogent and Internap.
* [http://www.hostigation.com Hostigation] - High resource unmanage VPS hosting solutions.
* [http://www.hostmist.com Host Mist] features budget OpenVZ VPS hosting from four major cities across the US.
* [http://www.hostingrails.com Hosting Rails] offers Rails-targeted OpenVZ VPS Hosting and updated Rails-ready OS images.
* [https://www.hostwinds.com Hostwinds] Affordable managed/unmanaged VPS Solutions.
* [http://www.infrenion.com./vps_hosting.html Infrenion Networks] Cheap, reliable and secure VPS hosting solutions, based on the openVZ platform. You can host any YouTube Clone scripts with enhanced support quality round the clock.
* [http://iniz.com/ INIZ VPS Hosting] INIZ provides affordable VPS Hosting in Los Angeles & New York with high resources at low prices.
* [http://www.joinvps.com JoinVPS.com] ISPmanager OpenVZ based VPS hosting. 24/7 Technical Support. Free ISPmanager control panel.
* [http://www.lovevps.com LoveVPS] Budget VPS provider starting at $5.99/month located in the US with Xeon nodes.
* [http://www.letstalkdigital.com/index.php?option=com_content&view=article&id=73&Itemid=65 LetsTalkDigital VPS Hosting] LetsTalkDigital.com offers both OpenVZ and XEN™ based VPS technologies. Cheap Linux and Windows VPS Hosting, start from $14.99 Virtual Private Server(VPS) hosting is for those who want the control and flexibility of a dedicated server at a much lower cost. All VPS packages come with a web hosting control panel option such as cPanel™, full root user access and all the features listed below, with 24/7 customer service.
* [http://lylix.net LYLIX] offers affordable VPS hosting with a choice of eight different Linux distributions, dedicated VPS hosting, and specializes in Asterisk/VOIP based hosting including Trixbox, AsteriskNow, Elastix, and PBX-in-a-Flash. Popular choice for unmanaged IP-PBX services; entire infrastructure built on a High-availability (HA) network across three regional NOCs.
* [http://www.micfo.com Micfo.com] offers VPS hosting services for both Linux VPS hosting and Window VPS hosting on affordable price combined with world-class 24x7x365 support.
* [http://www.neostreams.info/neoshop/cart.php?gid=9 nEo Stream Services] Offer's Top Quality OpenVZ Servers, Starting at $18.95 per month! SolusVM Control panel , 7 day Money Back Guarantee , 24x7 Professional Support.
* [http://pogiweb.com/vps/ PogiWeb LLC] Instant and free setup. Includes SolusVM control panel and free level 1 support during first month.
* [http://www.theserverexperts.com TheServerExperts.com] TheServerExperts VPS line is the ideal solution for clients who require the control of a dedicated server matched with the affordability and simplicity of a traditional shared hosting account.
* [http://thenynoc.com New York NOC] affordable Linux VPS hosting out of New York and Chicago. Plans as low as $5 a month and are backed by a redundant infrastructure and 24/7 support.
* [http://railsplayground.com RailsPlayground.com] Ruby on Rails VPS with ready to go Rails images with the LxAdmin control panel
* [http://www.raidlogic.net RaidLogic.NET] RaidLogic.NET offers OpenVZ based Linux VPS out of multiple facilities across the United States, including Miami, Los Angeles, and Chicago. Starting as low as $3.95/month.
* [http://www.ramhost.us RAM Host] RAM Host offers OpenVZ based Linux VPS out of multiple facilities across the United States, including Atlanta, Kansas City, and Phoenix.
* [http://www.reconhosting.com Recon Hosting] Recon Hosting offers affordable OpenVZ VPS solutions where you get Quality Hosting at a Fraction of the price. Instant setup with the latest Operating System templates including cPanel.
* [http://www.rokabear.com Rokabear] Rokabear offers OpenVZ Linux VPS, Dedicated Server, and Colocation. All Hardware setup in High Availability mode including raided drives and redudnant power and network connections. With multiple upstream providers, Rokabear's connectivity is fast and reliable! Rokabear supports LAMP, Openvpn, and Asterisk configurations. VPSes start at $7.99!
* [http://www.rshosting.com/vps.html RSHosting.com] RSHosting offers the most secure, reliable and stable VPS - Virtual Private Servers based on OpenVZ architecture, powered by the most professional and qualified 24/7 lightening fast support.
* [http://www.servercomplete.com Server Complete, LLC] Server Complete offers OpenVZ based Linux VPS out of multiple facilities across the United States, including Atlanta, Dallas, and Chicago.
* [http://www.servergrove.com ServerGrove] uses OpenVZ as the main virtualization platform for its state of the art VPS hosting services.
* [http://serverswarm.com ServerSwarm] provides stable, affordable, high performance OpenVZ virtual private servers.
* [http://www.silverrack.com/ SilverRack VPS Hosting] - SilverRack provides affordable VPS hosting using the OpenVZ platform.
* [http://www.soficol.com/ Soficol] Offers Enterprise OpenVZ based VPS, hosted on a clustered infrastructure and redundant network. Easy to use user management and instant setup.
* [http://www.budgetvds.com/ BudgetVDS] - Offers VPS Servers running openvz we've been in business for 2 years now using openvz platform.
* [http://www.syera.net/ Syera Networks] Unmetered VPS From $18.88/M, 24/7 Support, OpenVZ/HyperVM, Instant Setup!, Free 1Gbps Upgrade with Coupon: syera1G
* [http://www.synapseglobal.com/voip_vps.html SynapseGlobal.com] Elastix, Trixbox, PBX in a Flash and Asterisk VPS - OpenVZ based Asterisk VOIP servers with 14 Tier 1 premium bandwidth providers.
* [http://www.tektonic.net TekTonic] provides VPS hosting services using both Virtuozzo and OpenVZ technology.
* [http://www.tigerservers.com/ TigerServers] - Provides affordable managed VPS based on OpenVZ. Servers located in Chicago, Illinois
* [http://www.tocici.com/ TOCICI VPS Hosting Services] Since 1995 TOCICI has offered web hosting services, with 24/7 support commitments and a strong non-oversell policy. Our purpose-built hosting infrastructure has serviced many organizations for over a decade. Offering OpenVZ VPS, data center colocation, and equipment leasing options, visit our website for prices and more details.
* [http://www.triphost.com TripHost] provides OpenVZ based VPS accounts powered by SolusVM. Kansas City, KS Data Center.
* [http://www.ultravps.com UltraVPS] UltraVPS offers managed and unmanaged OpenVZ-based VPS hosting utilizing dual CPU hardware nodes with redundant, high-performance RAID-10 storage. UltraVPS offers VPS servers with many popular control panel options and turn-key applications.
* [http://www.vpsfx.com VPSFX] VPSFX.com offers OpenVZ VPS, data center colocation, and dedicated servers.
* [http://www.Webhost.US.Com/linuxvps.html US Web Hosting] Webhost.US.Com offers powerful GUI based VPS management system with full OpenVZ, Xen Paravirtualization and Xen HVM support.All our Virtual Private servers are fully Managed with 99.9% uptime and 24/7 top notch support.
* [http://worldhostnetwork.net OGN Network DBA WorldHostNetwork]Cheap reliable vps and website hosting.
* [http://unixservice.com Unixservice/unxsVZ] Low cost OpenVZ ONLY hosting we specialize in Mail, DNS and RADIUS multiple container hosting. At the world famous Market St. San Jose, CA Silicon Valley datacenter. Ping times from your containers to local yahoo and google sites guaranteed single digit ms times. Your containers are backed up at 4 local and 2 remote locations. Contact supportgrp at unixservice dot com.
* [http://vpslink.com VPSLink.com] provides virtual private server hosting on the OpenVZ platform.
* [http://www.vpsspeed.com/ VPSSpeed] - VPSSpeed provides unmanaged OpenVZ based VPS hosting with over 50 OS Templates, real 24/7/365 support and fast US servers. No overselling.
* [http://vpsnoc.com VPSNOC] offers unmanaged vps hosting based in the USA utilizing OpenVZ hypervisor behind an in-house VPS control panel.
* [http://www.webappcabaret.com WebAppCabaret] provides VPS solutions for hosting applications. We offer OpenVZ with cPanel or Plesk for web site management; and NGASI Universal App Manager for deploying and managing JAVA and RAILS applications.
* [http://www.wirenine.com/vps-hosting/ WireNine.com VPS Hosting] Low cost fully managed and unmanaged OpenVZ based VPS Hosting with SAS 15k enterprise drives in high-performance RAID-10 storage.
* [http://www.zoidial.com/ Zoidial Hosting and VPS] - offers VPS and Virtual Dedicated Server solutions utilizing OpenVZ. In business since 1998, Zoidial Incorporated is a small hosting provider focused on being security conscious, proactive, and offering a positive client experience.
* [http://zensix.com ZenSix Hosting] Cheap OpenVZ based VPS accounts with the SolusVM control panel.

== Vietnam ==
* [http://appvz.com AppVZ.com] (www.appvz.com) is a leading web solution provider offering domain, hosting, reseller and VPS hosting packages from 2009. Just recently, the company has offered discount packages where customers can avail managed and un-managed VPS for only $9.5 per month.

== See also ==

* [[Partners]]
* [[Download mirrors]]
* [[VPS vs Dedicated]]

Using NAT for container with private IPs

2013-09-21T16:10:09Z

Paparaciz: Reverted edits by Paparaciz (talk) to last revision by 217.82.102.23

Usually you supply public IP addresses to your containers. Sometimes you don't want to do it (lack of IPs, etc.). This article describes how to use private IP addresses for containers.

== Prerequisites ==

=== IP forwarding ===
IP forwarding should be turned on, on the hardware node in order for container networking to work. Make sure it is turned on:

$ cat /proc/sys/net/ipv4/ip_forward
1

Output should be '1'. If it is '0', enable IP forwarding as it is described in [[Quick installation#sysctl]].

NOTE: '''Ubuntu''' made some changes to the syntax for NAT. See this link if you are needing to enable NAT on an Ubuntu host :

[https://bugs.launchpad.net/ubuntu/+source/procps/+bug/84537 Launchpad]

The syntax of /etc/sysctl.conf has changed to :

<pre>net.ipv4.conf.default.forwarding=1
net.ipv4.conf.all.forwarding=1</pre>

=== IP conntracks ===
IP connection tracking should be enabled for CT0.

'''For OpenVZ kernels 2.6.8''', put the following line into /etc/modprobe.conf:

modprobe ip_conntrack ip_conntrack_enable_ve0=1

and reboot.

'''For OpenVZ kernels later than 2.6.8''', connection tracking for CT0 is enabled by default. '''However''', make sure there is '''no''' line like

options ip_conntrack ip_conntrack_disable_ve0=1

in /etc/modules.conf or /etc/modprobe.conf. If there is such line, comment it out (or remove) and reboot.

== How to provide access for container to Internet ==

To enable the [[container]]s, which have only internal IP addresses, to access the Internet, SNAT (Source Network Address Translation, also known as IP masquerading) should be configured on the [[Hardware Node]]. This is ensured by the standard Linux <tt>iptables</tt> utility. To perform a simple SNAT setup, execute the following command on the [[Hardware Node]]:
<pre>
# iptables -t nat -A POSTROUTING -s src_net -o eth0 -j SNAT --to ip_address
</pre>

where <tt>src_net</tt> is a range of IP addresses of containers to be translated by SNAT, and <tt>ip_address</tt> is the external IP address of your [[Hardware Node]]. The format of src_net is xx.xx.xx.xx/xx ([[w:CIDR|CIDR notation]]). For example to specify IP addresses from 192.168.2.1 through 192.168.2.127 use:
<pre>
# iptables -t nat -A POSTROUTING -s 192.168.2.0/25 -o eth0 -j SNAT --to ip_address
</pre>

Multiple rules are allowed, for example, in case you wish to specify several ranges of IP addresses. If you are using a number of physical network interfaces on the [[Hardware Node|Node]], you may need to specify a different interface for outgoing connections, e.g. <tt>-o eth2</tt>.

To make all IP addresses to be translated by SNAT (not only the ones of [[container]]s with private addresses), you should type the following string:
<pre>
# iptables -t nat -A POSTROUTING -o eth0 -j SNAT --to ip_address
</pre>

{{Note|For a Debian O.S v4 or v5 Hardware Node, you may need to allow a forward rule. The table still being the default table (filter) but the chain is FORWARD :

<pre>
# /sbin/iptables -A FORWARD -s 172.16.150.0/24 -j ACCEPT
# /sbin/iptables -A FORWARD -d 172.16.150.0/24 -j ACCEPT
</pre>}}

If you are using an iptables firewall (for example the default RedHat/CentOS firewall), don't forget to allow outgoing connections from your containers. For example if you are using the subnet 172.16.150.0/24 for your VMs, you should do the following:
<pre>
# /sbin/iptables -A RH-Firewall-1-INPUT -s 172.16.150.0/24 -j ACCEPT
# /sbin/iptables-save > /etc/sysconfig/iptables
# /sbin/service iptables restart
</pre>

{{Note|If the above is not working then check if one of the following solutions does the trick.}}
1. If you are using stable (currently 2.6.8-based) kernel, then to enable SNAT for the containers on your local network you need to explicitly enable connection tracking in [[CT0]]. Make sure that the following string is present in the <tt>/etc/modprobe.conf</tt> file:
<pre>
options ip_conntrack ip_conntrack_enable_ve0=1
</pre>

{{Note|in kernels later than 2.6.8, connection tracking is enabled by default}}

In case it is not, add this string to the file by means of any text editor (for example, vi). This setting is not needed for kernels more recent than 2.6.8, since connection tracking for [[CT0]] is enabled by default in those kernels.

2. For unknown reasons the above didn't work on a Debian host. The solution is to do it in an init.d script as follows:
<pre>
modprobe ip_conntrack ip_conntrack_enable_ve0=1
</pre>
Make sure that this module is loaded before any of the other iptables-modules are loaded! Also remember that if this module is loaded without the option, unloading and reloading doesn't work! You need to reboot the computer.

{{Note|in kernels later than 2.6.8, connection tracking is enabled by default}}

{{Note| you may need to modify the /etc/vz/vz.conf file to include:}}
<pre>
IPTABLES="iptable_filter iptable_mangle ipt_limit ipt_multiport ipt_tos ipt_TOS ipt_REJECT ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_LOG ipt_length ip_conntrack ip_conntrack_ftp ip_conntrack_irc ipt_conntrack ipt_state ipt_helper iptable_nat ip_nat_ftp ip_nat_irc ipt_REDIRECT"
</pre>

Now you should be able to reach internet from yours [[container]]:

<pre>
vzctl exec <container ID> ping www.openvz.org
</pre>

== How to provide access from Internet to a container ==

In addition, to make some services in container with private IP address be accessible from the Internet, DNAT (Destination Network Address Translation) should be configured on the [[Hardware Node]]. To perform a simple DNAT setup, execute the following command on the [[Hardware Node]]:
<pre>
# iptables -t nat -A PREROUTING -p tcp -d ip_address --dport port_num \
-i eth0 -j DNAT --to-destination ve_address:dst_port_num
</pre>

where <tt>ve_address</tt> is an IP address of the container, <tt>dst_port_num</tt> is a tcp port which requires service use, <tt>ip_address</tt> is the external (public) IP address of your [[Hardware Node]], and <tt>port_num</tt> is a tcp port of [[Hardware Node]], which will be used for Internet connections to private container service. Note that this setup makes the service which is using <tt>port_num</tt> on the [[Hardware Node]] be unaccessible from the Internet. Also note that SNAT translation is required too.

For example, if you need a web server in a container to be accessible from outside and, at the same time, keep a web server on the [[Hardware Node]] be accessible, use the following config:
<pre>
# iptables -t nat -A PREROUTING -p tcp -d ip_address --dport 8080 \
-i eth0 -j DNAT --to-destination ve_address:80
# iptables -t nat -A POSTROUTING -s ve_address -o eth0 -j SNAT --to ip_address
</pre>

After applying this, you'll see container' web server at <code><nowiki>http://ip_address:8080/</nowiki></code>.

{{Note|this rule will only work for external clients, i.e. connections originating from a different host — so you can not test if it works locally.}}

{{Note|If you get any errors relating to:
<code>iptables: No chain/target/match by that name</code>
double check to see if you have all the iptables/netfilter modules loaded properly. I had to <code> modprobe xt_tcpudp </code> before getting it to work.}}

The <tt>iptables</tt> utility allows to set up more complex rules for Network Address Translation, involving various protocols and ports. If you wish to get more information on this, consult the numerous Internet sites (e.g. [http://www.netfilter.org netfilter.org]) and tutorials devoted to this issue.

== External Links ==
* [http://www.netfilter.org netfilter.org]
* [[w:Private network]]

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

Using NAT for container with private IPs

2013-09-21T15:58:34Z

Paparaciz: /24 subnet mask is more common

Usually you supply public IP addresses to your containers. Sometimes you don't want to do it (lack of IPs, etc.). This article describes how to use private IP addresses for containers.

== Prerequisites ==

=== IP forwarding ===
IP forwarding should be turned on, on the hardware node in order for container networking to work. Make sure it is turned on:

$ cat /proc/sys/net/ipv4/ip_forward
1

Output should be '1'. If it is '0', enable IP forwarding as it is described in [[Quick installation#sysctl]].

NOTE: '''Ubuntu''' made some changes to the syntax for NAT. See this link if you are needing to enable NAT on an Ubuntu host :

[https://bugs.launchpad.net/ubuntu/+source/procps/+bug/84537 Launchpad]

The syntax of /etc/sysctl.conf has changed to :

<pre>net.ipv4.conf.default.forwarding=1
net.ipv4.conf.all.forwarding=1</pre>

=== IP conntracks ===
IP connection tracking should be enabled for CT0.

'''For OpenVZ kernels 2.6.8''', put the following line into /etc/modprobe.conf:

modprobe ip_conntrack ip_conntrack_enable_ve0=1

and reboot.

'''For OpenVZ kernels later than 2.6.8''', connection tracking for CT0 is enabled by default. '''However''', make sure there is '''no''' line like

options ip_conntrack ip_conntrack_disable_ve0=1

in /etc/modules.conf or /etc/modprobe.conf. If there is such line, comment it out (or remove) and reboot.

== How to provide access for container to Internet ==

To enable the [[container]]s, which have only internal IP addresses, to access the Internet, SNAT (Source Network Address Translation, also known as IP masquerading) should be configured on the [[Hardware Node]]. This is ensured by the standard Linux <tt>iptables</tt> utility. To perform a simple SNAT setup, execute the following command on the [[Hardware Node]]:
<pre>
# iptables -t nat -A POSTROUTING -s src_net -o eth0 -j SNAT --to ip_address
</pre>

where <tt>src_net</tt> is a range of IP addresses of containers to be translated by SNAT, and <tt>ip_address</tt> is the external IP address of your [[Hardware Node]]. The format of src_net is xx.xx.xx.xx/xx ([[w:CIDR|CIDR notation]]). For example to specify IP addresses from 192.168.2.1 through 192.168.2.127 use:
<pre>
# iptables -t nat -A POSTROUTING -s 192.168.2.0/24 -o eth0 -j SNAT --to ip_address
</pre>

Multiple rules are allowed, for example, in case you wish to specify several ranges of IP addresses. If you are using a number of physical network interfaces on the [[Hardware Node|Node]], you may need to specify a different interface for outgoing connections, e.g. <tt>-o eth2</tt>.

To make all IP addresses to be translated by SNAT (not only the ones of [[container]]s with private addresses), you should type the following string:
<pre>
# iptables -t nat -A POSTROUTING -o eth0 -j SNAT --to ip_address
</pre>

{{Note|For a Debian O.S v4 or v5 Hardware Node, you may need to allow a forward rule. The table still being the default table (filter) but the chain is FORWARD :

<pre>
# /sbin/iptables -A FORWARD -s 172.16.150.0/24 -j ACCEPT
# /sbin/iptables -A FORWARD -d 172.16.150.0/24 -j ACCEPT
</pre>}}

If you are using an iptables firewall (for example the default RedHat/CentOS firewall), don't forget to allow outgoing connections from your containers. For example if you are using the subnet 172.16.150.0/24 for your VMs, you should do the following:
<pre>
# /sbin/iptables -A RH-Firewall-1-INPUT -s 172.16.150.0/24 -j ACCEPT
# /sbin/iptables-save > /etc/sysconfig/iptables
# /sbin/service iptables restart
</pre>

{{Note|If the above is not working then check if one of the following solutions does the trick.}}
1. If you are using stable (currently 2.6.8-based) kernel, then to enable SNAT for the containers on your local network you need to explicitly enable connection tracking in [[CT0]]. Make sure that the following string is present in the <tt>/etc/modprobe.conf</tt> file:
<pre>
options ip_conntrack ip_conntrack_enable_ve0=1
</pre>

{{Note|in kernels later than 2.6.8, connection tracking is enabled by default}}

In case it is not, add this string to the file by means of any text editor (for example, vi). This setting is not needed for kernels more recent than 2.6.8, since connection tracking for [[CT0]] is enabled by default in those kernels.

2. For unknown reasons the above didn't work on a Debian host. The solution is to do it in an init.d script as follows:
<pre>
modprobe ip_conntrack ip_conntrack_enable_ve0=1
</pre>
Make sure that this module is loaded before any of the other iptables-modules are loaded! Also remember that if this module is loaded without the option, unloading and reloading doesn't work! You need to reboot the computer.

{{Note|in kernels later than 2.6.8, connection tracking is enabled by default}}

{{Note| you may need to modify the /etc/vz/vz.conf file to include:}}
<pre>
IPTABLES="iptable_filter iptable_mangle ipt_limit ipt_multiport ipt_tos ipt_TOS ipt_REJECT ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_LOG ipt_length ip_conntrack ip_conntrack_ftp ip_conntrack_irc ipt_conntrack ipt_state ipt_helper iptable_nat ip_nat_ftp ip_nat_irc ipt_REDIRECT"
</pre>

Now you should be able to reach internet from yours [[container]]:

<pre>
vzctl exec <container ID> ping www.openvz.org
</pre>

== How to provide access from Internet to a container ==

In addition, to make some services in container with private IP address be accessible from the Internet, DNAT (Destination Network Address Translation) should be configured on the [[Hardware Node]]. To perform a simple DNAT setup, execute the following command on the [[Hardware Node]]:
<pre>
# iptables -t nat -A PREROUTING -p tcp -d ip_address --dport port_num \
-i eth0 -j DNAT --to-destination ve_address:dst_port_num
</pre>

where <tt>ve_address</tt> is an IP address of the container, <tt>dst_port_num</tt> is a tcp port which requires service use, <tt>ip_address</tt> is the external (public) IP address of your [[Hardware Node]], and <tt>port_num</tt> is a tcp port of [[Hardware Node]], which will be used for Internet connections to private container service. Note that this setup makes the service which is using <tt>port_num</tt> on the [[Hardware Node]] be unaccessible from the Internet. Also note that SNAT translation is required too.

For example, if you need a web server in a container to be accessible from outside and, at the same time, keep a web server on the [[Hardware Node]] be accessible, use the following config:
<pre>
# iptables -t nat -A PREROUTING -p tcp -d ip_address --dport 8080 \
-i eth0 -j DNAT --to-destination ve_address:80
# iptables -t nat -A POSTROUTING -s ve_address -o eth0 -j SNAT --to ip_address
</pre>

After applying this, you'll see container' web server at <code><nowiki>http://ip_address:8080/</nowiki></code>.

{{Note|this rule will only work for external clients, i.e. connections originating from a different host — so you can not test if it works locally.}}

{{Note|If you get any errors relating to:
<code>iptables: No chain/target/match by that name</code>
double check to see if you have all the iptables/netfilter modules loaded properly. I had to <code> modprobe xt_tcpudp </code> before getting it to work.}}

The <tt>iptables</tt> utility allows to set up more complex rules for Network Address Translation, involving various protocols and ports. If you wish to get more information on this, consult the numerous Internet sites (e.g. [http://www.netfilter.org netfilter.org]) and tutorials devoted to this issue.

== External Links ==
* [http://www.netfilter.org netfilter.org]
* [[w:Private network]]

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

Ploop/Getting started

2012-09-02T15:59:44Z

Paparaciz: vzlist about diskspace usage

This article describes how to use container-in-a-file technology aka [[ploop]]

== Requirements ==

* OpenVZ kernel 042stab052.8 or later
* vzctl 3.1 or later
* ploop-lib 1.1 or later

== Making a CT on ploop ==

=== Global configuration ===

In global VZ configuration file [[Man/vz.conf.5|/etc/vz/vz.conf]], set

VE_LAYOUT=ploop

This means that all new containers you will create will have ploop layout by default.

You don't have to set this option if you don't want ploop to be default. Alternatively, you can:

* use <code>--layout</code> option of <code>vzctl create</code> command;
* convert existing container to ploop.

=== Creating a new CT ===

To create a new container on ploop, use:

vzctl create ''CTID'' [--layout ploop] [--diskspace ''nnn''G]

# You can omit <code>--layout</code> option if you have set <code>VE_LAYOUT=ploop</code> in {{Man|vz.conf|5}}
# You can specify initial file system size using <code>--diskspace</code> option (example: 10G for 10 gigabytes)
# If <code>--diskspace</code> is not specified, the size defaults to DISKSPACE limit value in sample CT config used

=== Converting an existing CT ===

1. Set some sane diskspace value (which will be used as a size of newly created ploop image). Here is the example to set diskspace to 10 gigabytes:
vzctl set ''CTID'' --diskspace 10G --save

2. Convert:
vzctl convert ''CTID''

== Resizing a ploop image ==

Ploop image can be resized in both directions (i.e. either shrank or grown). Ploop also supports online/live resize so you don't have to stop a CT to do resize.

{{Note|resize is potentially dangerous operation, backup is recommended to have before you proceed.}}

To resize a ploop CT image (either online or offline), use

vzctl set ''CTID'' --diskspace ''nnn''G --save

Note that
* there is no need to specify two values for diskspace (unlike simfs, there is no soft and hard quota).
* there is no way to limit or change the number of inodes available for a container (i.e. option '''--diskinodes''' is ignored)

== Showing disk space usage / limits ==

You can use {{Man|vzlist|8}} to see CT disk space usage and limits in a uniform way for any containers (simfs or ploop, started or stopped). The field '''diskspace''' is showing the current usage, and the fields '''diskspace.s''' and '''diskspace.h''' are showing the filesystem size (or disk space quotas, for simfs case).

vzlist -o smart_ctid,diskspace

== Using disk quotas inside container ==

If you want to use standard Linux per-user and per-group disk quota inside a container, you have to enable it using

vzctl set ''CTID'' --quotaugidlimit 1000 --save

Note that:
* unlike with simfs, ''--quotaugidlimit'' argument can be any non-zero value;
* enabling or disabling in-container disk quotas requires a container restart, so you can use vzctl's '''--setmode''' option.

See {{Man|vzctl|8}} for more details.

== See also ==

* [[Ploop]]
* {{Man|vz.conf|5}}
* {{Man|vzctl|8}}

Vzkernel-firmware

2012-07-13T08:06:17Z

Paparaciz: exclude vzkernel-firmware in yum

When using CentOS 6 (RHEL6, Scientific Linux 6) distribution and OpenVZ RHEL6-based kernel, the following problem occurs while running yum update:

Transaction Check Error:
file /lib/firmware/3com/3C359.bin from install of kernel-firmware-2.6.32-279.1.1.el6.centos.plus.noarch conflicts with file from package vzkernel-firmware-2.6.32-042stab056.11.noarch
file /lib/firmware/3com/typhoon.bin from install of kernel-firmware-2.6.32-279.1.1.el6.centos.plus.noarch conflicts with file from package vzkernel-firmware-2.6.32-042stab056.11.noarch
file /lib/firmware/acenic/tg1.bin from install of kernel-firmware-2.6.32-279.1.1.el6.centos.plus.noarch conflicts with file from package vzkernel-firmware-2.6.32-042stab056.11.noarch
file /lib/firmware/acenic/tg2.bin from install of kernel-firmware-2.6.32-279.1.1.el6.centos.plus.noarch conflicts with file from package vzkernel-firmware-2.6.32-042stab056.11.noarch
....
file /lib/firmware/yamaha/ds1e_ctrl.fw from install of kernel-firmware-2.6.32-279.1.1.el6.centos.plus.noarch conflicts with file from package vzkernel-firmware-2.6.32-042stab056.11.noarch
file /lib/firmware/yamaha/yss225_registers.bin from install of kernel-firmware-2.6.32-279.1.1.el6.centos.plus.noarch conflicts with file from package vzkernel-firmware-2.6.32-042stab056.11.noarch

There could also be a different conflict between <code>kernel-firmware</code> and <code>vzkernel-firmware</code> packages.

== Explanation ==

Package <code>vzkernel-firmware</code> is provided for distributions other than RHEL/CentOS 6, which lacks the package. On a CentOS 6, this package is not needed and it conflicts with the <code>kernel-firmware</code> package.

== Solution ==

The solution is to remove <code>vzkernel-firmware</code> package:

# rpm -e vzkernel-firmware

and exclude vzkernel-firmware in openvz yum repo file ( /etc/yum.repos.d/openvz.repo ):
[openvz-kernel-rhel6]
name=OpenVZ RHEL6-based kernel
#baseurl=http://download.openvz.org/kernel/branches/rhel6-2.6.32/current/
mirrorlist=http://download.openvz.org/kernel/mirrors-rhel6-2.6.32
enabled=1
gpgcheck=1
gpgkey=http://download.openvz.org/RPM-GPG-Key-OpenVZ
exclude=vzkernel-firmware*

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

Download/kernel/rhel6-testing/042stab057.1/changes

2012-06-27T06:05:03Z

Paparaciz: add missing brackets

== Changes ==
Since {{kernel link|rhel6-testing|042stab056.11}}:
* rebase to RHEL6.2 kernel-2.6.32-220.23.1.el6 kernel (security and bug fixes, see below)
* Note that CONFIG_OPENVSWITCH is not set in this kernel
* [fuse] fuse_flush() must wait till writeback is completed (PSBM-13697)
* [fuse] synchronous close has been reimplemented
* [fuse] file size handling has been corrected (PSBM-13216)
* [ubc/net] potential infinite loop fixed in case network code
* [pid namespaces] missing BSD_PROCESS_ACCT ifdef added. Required to compile kernel without CONFIG_BSD_PROCESS_ACCT kernel option ({{B|2273}})
* [fairsched] vmstat floating point operation fixed: idle scaling has been enhanced once again (PCLIN-30773)
* [scheduler] idle time should not be accounted on "possible" but offline cpus
* [mm] fix a corner case in memory reclaimer - guarantee to invoke OOM in case of no progress (PCLIN-30976)
* [cpt] Fedora 17 CTs should not migrate to older kernels without mount namespaces support, other CTs should migrate fine (PSBM-13534)
* [cpt] allow migration of tasks with SCHED_IDLE or SCHED_BATCH scheduler policy set ({{B|2283}})
* [fuse] PCS special files i_size handling has been fixed in case writeback is enabled (PSBM-13636)
* [pfcache] lockdep false-positive report fixed. The report is false-positive only in case we do not enable pfcache for pfcache cache.
* [scheduler] compilation without CONFIG_SCHEDSTATS config option fixed ({{B|2299}})

=== See also ===
* {{RHSA|2012:0743}}

NFS server inside container

2012-05-13T19:19:08Z

Paparaciz: Undo revision 12383 by MargaritaWatson (talk)

There are two ways to setup NFS server on common [[HN]]:
use a user-space NFS server daemon or use an in-kernel implementation
of NFS server.

{{Note|for information about NFS client inside container, see [[NFS]].}}

== Kernel NFS server ==

Kernel-space NFS server is supported by latest RHEL5 and RHEL6 based kernels and since vzctl-3.0.24.

In order to run an NFS server inside a container, make sure:
* nfsd kernel module is loaded on host system before starting a container
* nfsd feature for a container is turned on (<code>vzctl set $CTID --feature nfsd:on --save</code>)

== User-space NFS server ==
Advantage of user-space NFS server is that it does not require kernel support.
Also if it crashes — there is no crash of the system: just one process dies, not the kernel!
The disadvantage of user-space NFS server is its productivity: no one can be faster than in-kernel implementation.

One well-known implementation of NFS server is "The LINUX User-Space NFS Server" by Olaf Kirch.
Some Linux distributions contain this package: Debian Sarge (<code>nfs-user-server</code>), OpenSUSE 10.0 (<code>nfs-server</code>).
For other distributions you can download sources (for example from Debian repository) and compile it.
There is a small trick you have to know about running <code>mountd</code> and <code>nfsd</code> (these two daemons and <code>portmap</code> constitute a user-space server). You should run them with the <code>-r</code> option:
<pre>
# portmap
# rpc.mountd -r
# rpc.nfsd -r
</pre>
The reason is that these daemons check the major number of the device where the directory to export resides.
If major equals 0 then daemons assume that it is NFS and don't want to re-export it. Symptoms are
that clients will always get a "permission denied" error. Simfs (the file system on which container is located)
is associated with so called unnamed device, in which major equals 0. So, to prevent daemons from checking for
re-exporting — just use this <code>-r</code> option.

“The LINUX User-Space NFS Server” by Olaf Kirch implements NFSv2. It means that only files with sizes less
than 2GB are processed. If you intend to use such big files then you should use another user-space NFS server
implementation: [http://unfs3.sourceforge.net/ unfs3]. It implements v3 of NFS protocol standard.

Please note that the user-space NFS server does not provide locking, or at least I couldn't get locking to work - [[User:Elronxenu|Elronxenu]] 19:49, 15 November 2007 (EST)

=== On Debian Lenny ===

The current stable debian version 5.0 (lenny) provides two packages for user space nfs support: <code>nfs-user-server</code> and <code>unfs3</code>. Here i describe my experiences with them --[[User:Strimo|Strimo]] 17:47, 16 February 2009 (UTC)

It seems that also the unfs3 package has been removed from the debian repositories. --[[Special:Contributions/95.21.175.189|95.21.175.189]] 23:39, 30 July 2011 (UTC)

==== nfs-user-server ====

IMPORTANT : read http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515957 , nfs-user-server was removed

<pre>
aptitude install nfs-user-server
</pre>

First i used nfs-user-server package since i didn't know unfs3. After installing i always got the '''permission denied''' error when i tried to mount any exported path until i found this article. So i patched the /etc/init.d/nfs-user-server file to include the <code>-r</code> parameter by adding <code>-- -r</code> to the <code>start-stop-daemon</code> line responsible for starting <code>rpc.mountd</code> and <code>rpc.nfsd</code>:

<pre>
start-stop-daemon --start --oknodo --quiet --exec /usr/sbin/rpc.nfsd -- -r
start-stop-daemon --start --oknodo --quiet --exec /usr/sbin/rpc.mountd -- -r
</pre>

After the modification and a nfs server restart (<code>/etc/init.d/nfs-user-server restart</code>) i was able to mount a nfs share. At first the nfs server seems to work fine but anytime i want to edit any text file (using nano or mcedit) i got strange errors on writing to the file and i never solved the problem nor detected why this happens. So i switched to unfs3 ...

Note: nfsmount from busybox not works with nfs-user-server in Debian Lenny, it write message "rpc failed: 2" when I try boot from nfs server. unfs3 works fine.
Such problem into Ubuntu: https://bugs.launchpad.net/ubuntu/+source/nfs-user-server/+bug/189593

==== unfs3 ====

<pre>
aptitude install unfs3
</pre>

Works fine until now. Note that both unfs3 and nfs-user-server do not support file locking!
NOTE: I tested on centos 5.6 using unfs3 and I had to run the /etc/init.d/nfs service and see it work before I could use unfs. also use exports -a before using sudo /usr/sbin/unfsd -T -e /etc/exports

=== On CentOS 5 ===

If you are running RedHat/CentOS, you can [http://dag.wieers.com/rpm/packages/unfs3/ get unfs3 from the DAG repository]

== External links ==
* [http://nfs.sourceforge.net/ Linux NFS Overview, FAQ and HOWTO Documents]
* [http://www.tldp.org/LDP/nag/nag.html The Network Administrators' Guide by Olaf Kirch]
* [http://unfs3.sourceforge.net/ unfs3 homepage]
* [http://packages.qa.debian.org/n/nfs-user-server.html Overview of nfs-user-server source package]

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

NFS server inside container

2012-04-26T18:20:17Z

Paparaciz: Undo revision 12317 by Arianaqrsn (talk)

There are two ways to setup NFS server on common [[HN]]:
use a user-space NFS server daemon or use an in-kernel implementation
of NFS server.

{{Note|for information about NFS client inside container, see [[NFS]].}}

== Kernel NFS server ==

Kernel-space NFS server is supported by latest RHEL5 and RHEL6 based kernels and since vzctl-3.0.24.

In order to run an NFS server inside a container, make sure:
* nfsd kernel module is loaded on host system before starting a container
* nfsd feature for a container is turned on (<code>vzctl set $CTID --feature nfsd:on --save</code>)

== User-space NFS server ==
Advantage of user-space NFS server is that it does not require kernel support.
Also if it crashes — there is no crash of the system: just one process dies, not the kernel!
The disadvantage of user-space NFS server is its productivity: no one can be faster than in-kernel implementation.

One well-known implementation of NFS server is "The LINUX User-Space NFS Server" by Olaf Kirch.
Some Linux distributions contain this package: Debian Sarge (<code>nfs-user-server</code>), OpenSUSE 10.0 (<code>nfs-server</code>).
For other distributions you can download sources (for example from Debian repository) and compile it.
There is a small trick you have to know about running <code>mountd</code> and <code>nfsd</code> (these two daemons and <code>portmap</code> constitute a user-space server). You should run them with the <code>-r</code> option:
<pre>
# portmap
# rpc.mountd -r
# rpc.nfsd -r
</pre>
The reason is that these daemons check the major number of the device where the directory to export resides.
If major equals 0 then daemons assume that it is NFS and don't want to re-export it. Symptoms are
that clients will always get a "permission denied" error. Simfs (the file system on which container is located)
is associated with so called unnamed device, in which major equals 0. So, to prevent daemons from checking for
re-exporting — just use this <code>-r</code> option.

“The LINUX User-Space NFS Server” by Olaf Kirch implements NFSv2. It means that only files with sizes less
than 2GB are processed. If you intend to use such big files then you should use another user-space NFS server
implementation: [http://unfs3.sourceforge.net/ unfs3]. It implements v3 of NFS protocol standard.

Please note that the user-space NFS server does not provide locking, or at least I couldn't get locking to work - [[User:Elronxenu|Elronxenu]] 19:49, 15 November 2007 (EST)

=== On Debian Lenny ===

The current stable debian version 5.0 (lenny) provides two packages for user space nfs support: <code>nfs-user-server</code> and <code>unfs3</code>. Here i describe my experiences with them --[[User:Strimo|Strimo]] 17:47, 16 February 2009 (UTC)

It seems that also the unfs3 package has been removed from the debian repositories. --[[Special:Contributions/95.21.175.189|95.21.175.189]] 23:39, 30 July 2011 (UTC)

==== nfs-user-server ====

IMPORTANT : read http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515957 , nfs-user-server was removed

<pre>
aptitude install nfs-user-server
</pre>

First i used nfs-user-server package since i didn't know unfs3. After installing i always got the '''permission denied''' error when i tried to mount any exported path until i found this article. So i patched the /etc/init.d/nfs-user-server file to include the <code>-r</code> parameter by adding <code>-- -r</code> to the <code>start-stop-daemon</code> line responsible for starting <code>rpc.mountd</code> and <code>rpc.nfsd</code>:

<pre>
start-stop-daemon --start --oknodo --quiet --exec /usr/sbin/rpc.nfsd -- -r
start-stop-daemon --start --oknodo --quiet --exec /usr/sbin/rpc.mountd -- -r
</pre>

After the modification and a nfs server restart (<code>/etc/init.d/nfs-user-server restart</code>) i was able to mount a nfs share. At first the nfs server seems to work fine but anytime i want to edit any text file (using nano or mcedit) i got strange errors on writing to the file and i never solved the problem nor detected why this happens. So i switched to unfs3 ...

Note: nfsmount from busybox not works with nfs-user-server in Debian Lenny, it write message "rpc failed: 2" when I try boot from nfs server. unfs3 works fine.
Such problem into Ubuntu: https://bugs.launchpad.net/ubuntu/+source/nfs-user-server/+bug/189593

==== unfs3 ====

<pre>
aptitude install unfs3
</pre>

Works fine until now. Note that both unfs3 and nfs-user-server do not support file locking!
NOTE: I tested on centos 5.6 using unfs3 and I had to run the /etc/init.d/nfs service and see it work before I could use unfs. also use exports -a before using sudo /usr/sbin/unfsd -T -e /etc/exports

=== On CentOS 5 ===

If you are running RedHat/CentOS, you can [http://dag.wieers.com/rpm/packages/unfs3/ get unfs3 from the DAG repository]

== External links ==
* [http://nfs.sourceforge.net/ Linux NFS Overview, FAQ and HOWTO Documents]
* [http://www.tldp.org/LDP/nag/nag.html The Network Administrators' Guide by Olaf Kirch]
* [http://unfs3.sourceforge.net/ unfs3 homepage]
* [http://www.foredi.asia/ Gasa]
* [http://packages.qa.debian.org/n/nfs-user-server.html Overview of nfs-user-server source package]
* [http://www.diamondlinks.net link building service]
* [http://www.ovcio.com/ Software Akuntansi Laporan Keuangan Terbaik]

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

NFS server inside container

2012-04-16T15:08:07Z

Paparaciz: Undo revision 12286 by JuliaCherri (talk)

There are two ways to setup NFS server on common [[HN]]:
use a user-space NFS server daemon or use an in-kernel implementation
of NFS server.

{{Note|for information about NFS client inside container, see [[NFS]].}}

== Kernel NFS server ==

Kernel-space NFS server is supported by latest RHEL5 and RHEL6 based kernels and since vzctl-3.0.24.

In order to run an NFS server inside a container, make sure:
* nfsd kernel module is loaded on host system before starting a container
* nfsd feature for a container is turned on (<code>vzctl set $CTID --feature nfsd:on --save</code>)

== User-space NFS server ==
Advantage of user-space NFS server is that it does not require kernel support.
Also if it crashes — there is no crash of the system: just one process dies, not the kernel!
The disadvantage of user-space NFS server is its productivity: no one can be faster than in-kernel implementation.

One well-known implementation of NFS server is "The LINUX User-Space NFS Server" by Olaf Kirch.
Some Linux distributions contain this package: Debian Sarge (<code>nfs-user-server</code>), OpenSUSE 10.0 (<code>nfs-server</code>).
For other distributions you can download sources (for example from Debian repository) and compile it.
There is a small trick you have to know about running <code>mountd</code> and <code>nfsd</code> (these two daemons and <code>portmap</code> constitute a user-space server). You should run them with the <code>-r</code> option:
<pre>
# portmap
# rpc.mountd -r
# rpc.nfsd -r
</pre>
The reason is that these daemons check the major number of the device where the directory to export resides.
If major equals 0 then daemons assume that it is NFS and don't want to re-export it. Symptoms are
that clients will always get a "permission denied" error. Simfs (the file system on which container is located)
is associated with so called unnamed device, in which major equals 0. So, to prevent daemons from checking for
re-exporting — just use this <code>-r</code> option.

“The LINUX User-Space NFS Server” by Olaf Kirch implements NFSv2. It means that only files with sizes less
than 2GB are processed. If you intend to use such big files then you should use another user-space NFS server
implementation: [http://unfs3.sourceforge.net/ unfs3]. It implements v3 of NFS protocol standard.

Please note that the user-space NFS server does not provide locking, or at least I couldn't get locking to work - [[User:Elronxenu|Elronxenu]] 19:49, 15 November 2007 (EST)

=== On Debian Lenny ===

The current stable debian version 5.0 (lenny) provides two packages for user space nfs support: <code>nfs-user-server</code> and <code>unfs3</code>. Here i describe my experiences with them --[[User:Strimo|Strimo]] 17:47, 16 February 2009 (UTC)

It seems that also the unfs3 package has been removed from the debian repositories. --[[Special:Contributions/95.21.175.189|95.21.175.189]] 23:39, 30 July 2011 (UTC)

==== nfs-user-server ====

IMPORTANT : read http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515957 , nfs-user-server was removed

<pre>
aptitude install nfs-user-server
</pre>

First i used nfs-user-server package since i didn't know unfs3. After installing i always got the '''permission denied''' error when i tried to mount any exported path until i found this article. So i patched the /etc/init.d/nfs-user-server file to include the <code>-r</code> parameter by adding <code>-- -r</code> to the <code>start-stop-daemon</code> line responsible for starting <code>rpc.mountd</code> and <code>rpc.nfsd</code>:

<pre>
start-stop-daemon --start --oknodo --quiet --exec /usr/sbin/rpc.nfsd -- -r
start-stop-daemon --start --oknodo --quiet --exec /usr/sbin/rpc.mountd -- -r
</pre>

After the modification and a nfs server restart (<code>/etc/init.d/nfs-user-server restart</code>) i was able to mount a nfs share. At first the nfs server seems to work fine but anytime i want to edit any text file (using nano or mcedit) i got strange errors on writing to the file and i never solved the problem nor detected why this happens. So i switched to unfs3 ...

Note: nfsmount from busybox not works with nfs-user-server in Debian Lenny, it write message "rpc failed: 2" when I try boot from nfs server. unfs3 works fine.
Such problem into Ubuntu: https://bugs.launchpad.net/ubuntu/+source/nfs-user-server/+bug/189593

==== unfs3 ====

<pre>
aptitude install unfs3
</pre>

Works fine until now. Note that both unfs3 and nfs-user-server do not support file locking!
NOTE: I tested on centos 5.6 using unfs3 and I had to run the /etc/init.d/nfs service and see it work before I could use unfs. also use exports -a before using sudo /usr/sbin/unfsd -T -e /etc/exports

=== On CentOS 5 ===

If you are running RedHat/CentOS, you can [http://dag.wieers.com/rpm/packages/unfs3/ get unfs3 from the DAG repository]

== External links ==
* [http://nfs.sourceforge.net/ Linux NFS Overview, FAQ and HOWTO Documents]
* [http://www.tldp.org/LDP/nag/nag.html The Network Administrators' Guide by Olaf Kirch]
* [http://unfs3.sourceforge.net/ unfs3 homepage]
* [http://www.foredi.asia/ Gasa]
* [http://packages.qa.debian.org/n/nfs-user-server.html Overview of nfs-user-server source package]
* [http://www.diamondlinks.net link building service]
* [http://www.ovcio.com/ Software Akuntansi Laporan Keuangan Terbaik]

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

OpenVZ Virtuozzo Containers Wiki:External links policy

2012-04-10T07:43:18Z

Paparaciz: Undo revision 12263 by Tianshishiabn (talk)

This is an official policy of OpenVZ Wiki.

== Scope and definition ==

External link is the link that points to outside of this wikipedia. Note that links to other *.openvz.org sites are considered internal.

This policy describes what kind of external links one can not add to this wiki. This policy is needed because some people try to use OpenVZ Wiki as a [http://en.wikipedia.org/wiki/SEO SEO] tool.

== Links that can not be added ==

The following types of links are strictly prohibited to be added to OpenVZ Wiki.

; Links to irrelevant pages
: Page linked is not relevant to the content of a wiki article, such as links to [http://en.wikipedia.org/wiki/Doorway_page doorways], casino sites, etc.

; Links to non-original content
: Page linked contains basically the same information as a wiki article, adding nothing new, or other content taken from openvz.org sites.

== Enforcement ==

This policy is enforced by reverting edits which add links prohibited by this policy. Other means can be used as well (such as blocking users, IPs, etc).

Remote console setup

2012-04-10T07:42:53Z

Paparaciz: Undo revision 12262 by Tianshishiabn (talk)

In case you are experiencing a kernel crash ([[oops]]) and have already [[Hardware testing|tested your hardware]], you should report what kernel says to the console (i.e. an [[oops]] text) to [http://bugzilla.openvz.org/ Bugzilla]. Sometimes kernel crashes so badly that <tt>syslogd</tt> is not working and what kernel says is never written to a file. If this is the case, you have to catch what kernel says. There are several ways possible.

== Manual/Photo ==
If kernel backtrace is not long enough there are chances that it can fit into a single screen. In that case, you can just make a photo of the kernel crash screen and attach it to the bug report. If you do not have a camera, you still can carefully write down (using a piece of paper and a pen, that is) what you see on the screen, and later type it into the bug report.

== Serial console ==
Here is a description of a common routine that is necessary to set up a serial console.

=== Hardware setup ===
First of all you should make sure that your node has a [[w:Serial port|serial port]]. If there is no such port then
unfortunately this way is not for you.

Then you need to find a second machine with a serial port on it.
This machine will be used to collect logs from your primary machine. Further you need to acquire
so-called [[w:Serial cable|null modem cable (a.k.a. serial cable)]] and it must be long enough to connect these two machines.

=== Software setup ===

==== Sending side ====
In your boot loader add the following kernel parameters:
<pre>
console=ttyS0,115200 console=tty0
</pre>

{{Warning|make sure kernel command line does '''not''' contain the word '''<code>quiet</code>''', otherwise most of the kernel messages will not be printed to console.}}

For example, in GRUB boot loader configuration file <tt>/boot/grub/grub.conf</tt> it looks like this:
<pre>
title Fedora Core (2.6.16-026test014.1-smp)
root (hd0,0)
kernel /vmlinuz-2.6.16-026test014.1-smp ro root=LABEL=/ console=ttyS0,115200 console=tty debug silencelevel=8
initrd /initrd-2.6.16-026test014.1-smp.img
</pre>

Kernel loaded with such parameters will send all kernel messages to /dev/ttyS0 (first serial port, a.k.a. COM1). If you have several ports, make sure that your null modem cable is connected to the appropriate port.

==== Receiving side ====
On the second node you should run any software that can log from /dev/ttyS0.

It can be usual
<pre>
cat /dev/ttyS0 > /var/log/serial.log &
</pre>
or something more sophisticated: syslogd, watchtty etc.

==== Port setup ====
One more important thing. 115200 in the example above is the rate of emitting port. Receiving port must also work at the same rate. For example, to tune ttyS0 rate use stty program like this:
<pre>
stty 115200 < /dev/ttyS0
</pre>

Some other serial port parameters, like parity, number of stop bits etc. should also be the same on both sides.

== Netconsole ==

=== Kernel recompilation ===
If you use binary kernel from openvz.org, it already has netconsole module compiled in, so just skip to next section.

If you build the kernel yourself, you might need to check if netconsole is compiled. To that effect, change to your kernel source directory and grep your kernel <tt>.config</tt> for NETCONSOLE:
<pre>
# cd /usr/src/openvz/linux-2.6.16
# grep NETCONSOLE .config
</pre>

If you see nothing or "# CONFIG_NETCONSOLE is not set" you need to recompile the kernel.

Edit your kernel configuration file <tt>.config</tt> with a text editor (<tt>nano .config</tt> or <tt>vi .config</tt>). Set netconsole to Y or M (depending on whether you want it as a module or built into the kernel; I have compiled it as a module):

<pre>CONFIG_NETCONSOLE=m</pre>

Save the file, then recompile the kernel:

<pre>
# make bzImage && make modules && make modules_install
</pre>
Update your bootloader for the new updated kernel. In my case I use LILO so I just type lilo at the prompt.

Reboot into new kernel.

=== Setting up OpenVZ side ===

Next you want your netconsole to send the request to somewhere. Load netconsole module, specifying the remote server parameters:

<pre># modprobe netconsole netconsole=4444@10.0.2.1/eth0,6666@10.0.2.2/00:05:5D:34:11:AF</pre>

This will load the module with your settings. Replace your local IP address with where <tt>10.0.2.1</tt> is, <tt>eth0</tt> with your network interface card device, <tt>6666</tt> with the remote netconsole port (UDP), and <tt>10.0.2.2</tt> with your remote netconsole server IP. Also add in the mac address of your remote netconsole server, which in my case was 00:05:5D:34:11:AF. You can get the MAC address using arp utility:

<pre>
# ping -c 1 10.0.2.2
# /sbin/arp -n 10.0.2.2
Address HWtype HWaddress Flags Mask Iface
10.0.2.2 ether 00:05:5D:34:11:AF C eth0
</pre>

If the remote netconsole server is outside of local network area, use mac address of default gateway or router on local network area and IP address of remote netconsole server (loging via WAN). Mac address of default gateway or router you can get the same way (ping to gateway/router and see mac address via arp command).

Netconsole documentation is available from <tt>Documentation/networking/netconsole.txt</tt> file under your kernel source directory.

=== Setting from initrd ===

To durable logging boot process before root filesystem mounting network device driver and netconsole module must be loaded from initd.

RedHat 5/CentOS 5:
echo 'MODULES+="<network-driver-module> netconsole "' > /etc/sysconfig/mkinitrd/netconsole
chmod +x /etc/sysconfig/mkinitrd/netconsole
echo 'options netconsole netconsole=<sport>@<saddr>/<dev>,<dport>@<daddr>/<dmac>' >> /etc/modprobe.conf
Debian/Ubuntu:
echo '<network-driver-module>' >> /etc/initramfs-tools/modules
echo 'netconsole netconsole=<sport>@<saddr>/<dev>,<dport>@<daddr>/<dmac>' >> /etc/initramfs-tools/modules

and rebuild initrd

=== Setting up remote side ===

Setup '''netcat''' ('''nc''' on some Linux distributions) on your console server to listen on port 6666 UDP:
<pre>netcat -u -l -p6666</pre>
or
<pre>nc -lu 6666</pre>
When your kernel prints something on the console, the text will be also captured on this netconsole server.

==== Adding to inittab ====
For automatic care about capturing on console server you can use init respawn feature in this way:

<pre>
echo "n1:23:respawn:/bin/netcat -u -l -p 6666 >> /var/log/netconsole" >> /etc/inittab
telinit q
</pre>

==== Adding date/time to messages ====

If you want the log to contain date/time of each line, you can use '''awk''' like this:

netcat -u -l -p6666 | awk '{print strftime("%d %b %Y %H:%M:%S"), $0; fflush(stdout);}' >> /var/log/netconsole

See man strftime for info about how to tailor strftime() argument to your needs.

Note that if you want to add this to /etc/inittab, it should be done like this:

echo "netcat -u -l -p6666 | awk '{print \
strftime("%d %b %Y %H:%M:%S"), \$0; fflush(stdout);}' \
>> /var/log/netconsole" > /usr/local/sbin/netconsole
chmod a+x /usr/local/sbin/netconsole
echo "n1:23:respawn:/usr/local/sbin/netconsole" >> /etc/inittab
telinit q

==== Configuring logrotate ====

For long term capturing you would like to do log rotating some way. With logrotate you can do it by creating config file /etc/logrotate.d/netconsole:

<pre>
/var/log/netconsole {
weekly
rotate 8
missingok
compress
copytruncate
notifempty
# Need to restart logger after log file move
postrotate
# Below line assumes netcat will be restarted by init
killall -TERM netcat > /dev/null 2>&1 || true
}
</pre>

For more details, see man logrotate.

=== Testing netconsole ===

First check log level of console messages on OpenVZ side by:

<pre>cat /proc/sys/kernel/printk</pre>

First number should be 7 for testing. You can arrange it by:

<pre>sysctl -w kernel.printk="7 4 1 7"</pre>

After testing you can restore previous setting the same way.

Load '''netconsole''' module (see above) and on the console server run netcat (nc) command. On OpenVZ side provoke any console message, for example connect any USB hardware or try command:

modprobe tun

If you see any console message on OpenVZ side, you should see message on console server too. If not, something is wrong. When debugging a problem, do not use tcpdump on OpenVZ side — it is not able to show netconsole packets. Instead, use tcpdump on console server. Quite a common source of problems with netconsole are firewalls.

== See also ==
* [[SysRq debugger]]
* [[Kernel debug options]]

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

User Guide/Installation and Preliminary Operations

2012-04-04T18:32:27Z

Paparaciz: vzpkg is deprecated

<noinclude>{{UG/Header}}</noinclude>
The current chapter provides exhaustive information on the process of installing and deploying your OpenVZ system including the pre-requisites and the stages you shall pass.

== Installation Requirements ==
After deciding on the structure of your OpenVZ system, you should make sure that all the Hardware Nodes where you are going to deploy OpenVZ for Linux meet the following system (hardware and software) and network requirements.

=== System Requirements ===
This section focuses on the hardware and software requirements for the OpenVZ for Linux software product.

==== Hardware Compatibility ====
The Hardware Node requirements for the standard 32-bit edition of OpenVZ are the following:
* IBM PC-compatible computer;
* Intel Celeron, Pentium II, Pentium III, Pentium 4, Xeon, or AMD Athlon CPU;
* At least 128 MB of RAM;
* Hard drive(s) with at least 4 GB of free disk space;
* Network card (either Intel EtherExpress100 (i82557-, i82558- or i82559-based) or 3Com (3c905 or 3c905B or 3c595) or RTL8139-based are recommended).

The computer should satisfy the Red Hat Enterprise Linux or Fedora Core hardware requirements (please, see the hardware compatibility lists at www.redhat.com).

The exact computer configuration depends on how many Virtual Private Servers you are going to run on the computer and what load these VPSs are going to produce. Thus, in order to choose the right configuration, please follow the recommendations below:
* CPUs. The more Virtual Private Servers you plan to run simultaneously, the more CPUs you need.
* Memory. The more memory you have, the more Virtual Private Servers you can run. The exact figure depends on the number and nature of applications you are planning to run in your Virtual Private Servers. However, on the average, at least 1 GB of RAM is recommended for every 20-30 Virtual Private Servers;
* Disk space. Each Virtual Private Server occupies 400–600 MB of hard disk space for system files in addition to the user data inside the Virtual Private Server (for example, web site content). You should consider it when planning disk partitioning and the number of Virtual Private Servers to run.

A typical 2–way Dell PowerEdge 1650 1u–mountable server with 1 GB of RAM and 36 GB of hard drives is suitable for hosting 30 Virtual Private Servers.

==== Software Compatibility ====

The Hardware Node should run either Red Hat Enterprise Linux 6 or 5, or CentOS 6 or 5, or Scientific Linux 6 or 5. The detailed instructions on installing these operating systems for the best performance of OpenVZ are provided in the next sections.

This requirement does not restrict the ability of OpenVZ to provide other Linux versions as an operating system for Virtual Private Servers. The Linux distribution installed in a Virtual Private Server may differ from that of the host OS.

=== Network Requirements ===
The network pre-requisites enlisted in this subsection will help you avoid delays and problems with making OpenVZ for Linux up and running. You should take care in advance of the following:
* Local Area Network (LAN) for the Hardware Node;
* Internet connection for the Hardware Node;
* Valid IP address for the Hardware Node as well as other IP parameters (default gateway, network mask, DNS configuration);
* At least one valid IP address for each Virtual Private Server. The total number of addresses should be no less than the planned number of Virtual Private Servers. The addresses may be allocated in different IP networks;
* If a firewall is deployed, check that IP addresses allocated for Virtual Private Servers are open for access from the outside.

== Installing and Configuring Host Operating System on Hardware Node ==

This section explains how to install Fedora Core 4 on the Hardware Node and how to configure it for OpenVZ. If you are using another distribution, please consult the corresponding installation guides about the installation specifics.

=== Choosing System Type ===

Please follow the instructions from your Installation Guide when installing the OS on your Hardware Node. After the first several screens, you will be presented with a screen specifying the installation type. OpenVZ requires Server System to be installed, therefore select “Server” at the dialog shown in the figure below.

Figure 2: Fedora Core Installation - Choosing System Type
It is not recommended to install extra packages on the Hardware Node itself due to the all-importance of Hardware Node availability (see the [[#Hardware Node Availability Considerations]] subsection in this chapter). You will be able to run any necessary services inside dedicated Virtual Private Servers.

=== Disk Partitioning ===

On the Disk Partitioning Setup screen, select Manual partition with Disk Druid. Do not choose automatic partitioning since this type of partitioning will create a disk layout intended for systems running multiple services. In case of OpenVZ, all your services shall run inside Virtual Private Servers.

Figure 3: Fedora Core Installation - Choosing Manual Partitioning

Create the following partitions on the Hardware Node:
{| class="wikitable"
! Partition !! Description !! Typical size
|-
| / || Root partition containing all Hardware Node operating system files | 4–12 Gb
|-
| swap || Paging partition for the Linux operating system || 2 times RAM or RAM + 2GB depending on available HD space
|-
| /vz || Partition to host OpenVZ templates and Virtual Private Servers || all the remaining space on the hard disk
|}

Many of the historical specifications for partitioning are outdated in an age where all hard drives are well above 20GB. So all minimums can be increased without any impact if you have plenty of drive space. It is suggested to use the ext3 or ext4 file system for the /vz partition. This partition is used for holding all data of the Virtual Private Servers existing on the Hardware Node. Allocate as much disk space as possible to this partition. It is not recommended to use the reiserfs file system as it is proved to be less stable than the ext3, and stability is of paramount importance for OpenVZ-based computers.

The root partition will host the operating system files. Fresh CentOS 6 install with basic server packages + OpenVZ kernel can occupy up to approximately 2 GB of disk space, so 4 GB is a good minimal size of the root partition. If you have plenty of drive space and think you may add additional software to the Node such as monitoring software then consider using more. Historically, the recommended size of the swap partition has been two times the size of physical RAM installed. Now, with minimum server RAM often above 2GB a more reasonable specification might be RAM + 2GB if RAM is above 2GB and HD space is limited.

=== Finishing OS Installation ===
After the proper partitioning of your hard drive(s), proceed in accordance with your OS Installation Guide.
While on the Network Configuration screen, you should ensure the correctness of the Hardware Node’s IP address, host name, DNS, and default gateway information. If you are using DHCP, make sure that it is properly configured. If necessary, consult your network administrator.
On the Firewall Configuration screen, choose No firewall. Option Enable SELinux should be set to Disabled.

Fedora Core Installation - Disabling Firewall and SELinux
After finishing the installation and rebooting your computer, you are ready to install OpenVZ on your system.

== Installing OpenVZ Software ==

=== Downloading and Installing OpenVZ Kernel ===

First of all, you should download the kernel binary RPM from http://openvz.org/download/kernel/. You need only one kernel RPM, so please choose the appropriate kernel binary depending on your hardware:

if you use Red Hat Enterprise 5, or Centos 5, or Scientific Linux 5:
* If there is more than one CPU available on your Hardware Node (or a CPU with hyperthreading), select the vzkernel-smp RPM.
* If there is more than 4 Gb of RAM available, select the vzkernel-enterprise RPM.
* Otherwise, select the uniprocessor kernel RPM (vzkernel-version).

if you use Red Hat Enterprise 6, or Centos 6, or Scientific Linux 6:
*select the uniprocessor kernel RPM (vzkernel-version).

Next, you shall install the kernel RPM of your choice on your Hardware Node by issuing the following command:
# rpm -ihv vzkernel-name*.rpm

{{Note|You should not use the rpm –U command (where -U stands for "upgrade"); otherwise, all the kernels currently installed on the Node will be removed.}}

=== Configuring Boot Loader ===

In case you use the GRUB loader, it will be configured automatically. You should only make sure that the lines below are present in the /boot/grub/grub.conf file on the Node:

title Fedora Core (2.6.8-022stab029.1)
root (hd0,0)
kernel /vmlinuz-2.6.8-022stab029.1 ro root=/dev/sda5 quiet rhgb
initrd /initrd-2.6.8-022stab029.1.img

However, we recommend that you configure this file in the following way:
* Change Fedora Core to OpenVZ (just for clarity, so the OpenVZ kernels will not be mixed up with non OpenVZ ones).
* Remove all extra arguments from the kernel line, leaving only the root=... parameter.

At the end, the modified grub.conf file should look as follows:
title OpenVZ (2.6.8-022stab029.1)
root (hd0,0)
kernel /vmlinuz-2.6.8-022stab029.1 ro root=/dev/sda5
initrd /initrd-2.6.8-022stab029.1.img

=== Setting sysctl parameters ===

There are a number of kernel limits that should be set for OpenVZ to work correctly. OpenVZ is shipped with a tuned /etc/sysctl.conf file. Below are the contents of the relevant part of /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>

Please edit the file as described. To apply the changes issue the following command:

# sysctl -p

Alternatively, the changes will be applied upon the following reboot.

It is also worth mentioning that normally you should have forwarding (net.ipv4.ip_forward) turned on since the Hardware Node forwards the packets destined to or originating from the Virtual Private Servers.

After that, you should reboot your computer and choose "OpenVZ" on the boot loader menu.

=== Downloading and Installing OpenVZ Packages ===
After you have successfully installed and booted the OpenVZ kernel, you can proceed with installing the user-level tools for OpenVZ.
You should install the following OpenVZ packages:
* vzctl: this package is used to perform different tasks on the OpenVZ Virtual Private Servers (create, destroy, start, stop, set parameters etc.).
* vzquota: this package is used to manage the VPS quotas.

You can download the corresponding binary RPMs from http://openvz.org/download/utils/.

On the next step, you should install these utilities by using the following command:
# rpm –Uhv vzctl*.rpm vzquota*.rpm

{{Note|During the packages installation, you may be presented with a message telling you that rpm has found unresolved dependencies. In this case you have to resolve these dependencies first and then repeat the installation.}}

Now you can launch OpenVZ. To this effect, execute the following command:

# /etc/init.d/vz start

This will load all the needed OpenVZ kernel modules. During the next reboot, this script will be executed automatically.

=== Installing OS Templates ===

Template is a set of package files to be installed into a Container. Operating system templates are used to create new Containers with a pre-installed operating system. Therefore, you are bound to download at least one OS template and put it into <code>/vz/template/cache/</code> directory on the Hardware Node.

Links to all available OS templates at listed at [[Download/template/precreated]].

For example, this is how to download the CentOS 5 OS template:
<pre>
# cd /vz/template/cache
# wget http://download.openvz.org/template/precreated/centos-5-x86.tar.gz
</pre>

<noinclude>{{UG/Footer}}</noinclude>

User Guide/Installation and Preliminary Operations

2012-04-04T18:14:40Z

Paparaciz: formatting fix

<noinclude>{{UG/Header}}</noinclude>
The current chapter provides exhaustive information on the process of installing and deploying your OpenVZ system including the pre-requisites and the stages you shall pass.

== Installation Requirements ==
After deciding on the structure of your OpenVZ system, you should make sure that all the Hardware Nodes where you are going to deploy OpenVZ for Linux meet the following system (hardware and software) and network requirements.

=== System Requirements ===
This section focuses on the hardware and software requirements for the OpenVZ for Linux software product.

==== Hardware Compatibility ====
The Hardware Node requirements for the standard 32-bit edition of OpenVZ are the following:
* IBM PC-compatible computer;
* Intel Celeron, Pentium II, Pentium III, Pentium 4, Xeon, or AMD Athlon CPU;
* At least 128 MB of RAM;
* Hard drive(s) with at least 4 GB of free disk space;
* Network card (either Intel EtherExpress100 (i82557-, i82558- or i82559-based) or 3Com (3c905 or 3c905B or 3c595) or RTL8139-based are recommended).

The computer should satisfy the Red Hat Enterprise Linux or Fedora Core hardware requirements (please, see the hardware compatibility lists at www.redhat.com).

The exact computer configuration depends on how many Virtual Private Servers you are going to run on the computer and what load these VPSs are going to produce. Thus, in order to choose the right configuration, please follow the recommendations below:
* CPUs. The more Virtual Private Servers you plan to run simultaneously, the more CPUs you need.
* Memory. The more memory you have, the more Virtual Private Servers you can run. The exact figure depends on the number and nature of applications you are planning to run in your Virtual Private Servers. However, on the average, at least 1 GB of RAM is recommended for every 20-30 Virtual Private Servers;
* Disk space. Each Virtual Private Server occupies 400–600 MB of hard disk space for system files in addition to the user data inside the Virtual Private Server (for example, web site content). You should consider it when planning disk partitioning and the number of Virtual Private Servers to run.

A typical 2–way Dell PowerEdge 1650 1u–mountable server with 1 GB of RAM and 36 GB of hard drives is suitable for hosting 30 Virtual Private Servers.

==== Software Compatibility ====

The Hardware Node should run either Red Hat Enterprise Linux 6 or 5, or CentOS 6 or 5, or Scientific Linux 6 or 5. The detailed instructions on installing these operating systems for the best performance of OpenVZ are provided in the next sections.

This requirement does not restrict the ability of OpenVZ to provide other Linux versions as an operating system for Virtual Private Servers. The Linux distribution installed in a Virtual Private Server may differ from that of the host OS.

=== Network Requirements ===
The network pre-requisites enlisted in this subsection will help you avoid delays and problems with making OpenVZ for Linux up and running. You should take care in advance of the following:
* Local Area Network (LAN) for the Hardware Node;
* Internet connection for the Hardware Node;
* Valid IP address for the Hardware Node as well as other IP parameters (default gateway, network mask, DNS configuration);
* At least one valid IP address for each Virtual Private Server. The total number of addresses should be no less than the planned number of Virtual Private Servers. The addresses may be allocated in different IP networks;
* If a firewall is deployed, check that IP addresses allocated for Virtual Private Servers are open for access from the outside.

== Installing and Configuring Host Operating System on Hardware Node ==

This section explains how to install Fedora Core 4 on the Hardware Node and how to configure it for OpenVZ. If you are using another distribution, please consult the corresponding installation guides about the installation specifics.

=== Choosing System Type ===

Please follow the instructions from your Installation Guide when installing the OS on your Hardware Node. After the first several screens, you will be presented with a screen specifying the installation type. OpenVZ requires Server System to be installed, therefore select “Server” at the dialog shown in the figure below.

Figure 2: Fedora Core Installation - Choosing System Type
It is not recommended to install extra packages on the Hardware Node itself due to the all-importance of Hardware Node availability (see the [[#Hardware Node Availability Considerations]] subsection in this chapter). You will be able to run any necessary services inside dedicated Virtual Private Servers.

=== Disk Partitioning ===

On the Disk Partitioning Setup screen, select Manual partition with Disk Druid. Do not choose automatic partitioning since this type of partitioning will create a disk layout intended for systems running multiple services. In case of OpenVZ, all your services shall run inside Virtual Private Servers.

Figure 3: Fedora Core Installation - Choosing Manual Partitioning

Create the following partitions on the Hardware Node:
{| class="wikitable"
! Partition !! Description !! Typical size
|-
| / || Root partition containing all Hardware Node operating system files | 4–12 Gb
|-
| swap || Paging partition for the Linux operating system || 2 times RAM or RAM + 2GB depending on available HD space
|-
| /vz || Partition to host OpenVZ templates and Virtual Private Servers || all the remaining space on the hard disk
|}

Many of the historical specifications for partitioning are outdated in an age where all hard drives are well above 20GB. So all minimums can be increased without any impact if you have plenty of drive space. It is suggested to use the ext3 or ext4 file system for the /vz partition. This partition is used for holding all data of the Virtual Private Servers existing on the Hardware Node. Allocate as much disk space as possible to this partition. It is not recommended to use the reiserfs file system as it is proved to be less stable than the ext3, and stability is of paramount importance for OpenVZ-based computers.

The root partition will host the operating system files. Fresh CentOS 6 install with basic server packages + OpenVZ kernel can occupy up to approximately 2 GB of disk space, so 4 GB is a good minimal size of the root partition. If you have plenty of drive space and think you may add additional software to the Node such as monitoring software then consider using more. Historically, the recommended size of the swap partition has been two times the size of physical RAM installed. Now, with minimum server RAM often above 2GB a more reasonable specification might be RAM + 2GB if RAM is above 2GB and HD space is limited.

=== Finishing OS Installation ===
After the proper partitioning of your hard drive(s), proceed in accordance with your OS Installation Guide.
While on the Network Configuration screen, you should ensure the correctness of the Hardware Node’s IP address, host name, DNS, and default gateway information. If you are using DHCP, make sure that it is properly configured. If necessary, consult your network administrator.
On the Firewall Configuration screen, choose No firewall. Option Enable SELinux should be set to Disabled.

Fedora Core Installation - Disabling Firewall and SELinux
After finishing the installation and rebooting your computer, you are ready to install OpenVZ on your system.

== Installing OpenVZ Software ==

=== Downloading and Installing OpenVZ Kernel ===

First of all, you should download the kernel binary RPM from http://openvz.org/download/kernel/. You need only one kernel RPM, so please choose the appropriate kernel binary depending on your hardware:

if you use Red Hat Enterprise 5, or Centos 5, or Scientific Linux 5:
* If there is more than one CPU available on your Hardware Node (or a CPU with hyperthreading), select the vzkernel-smp RPM.
* If there is more than 4 Gb of RAM available, select the vzkernel-enterprise RPM.
* Otherwise, select the uniprocessor kernel RPM (vzkernel-version).

if you use Red Hat Enterprise 6, or Centos 6, or Scientific Linux 6:
*select the uniprocessor kernel RPM (vzkernel-version).

Next, you shall install the kernel RPM of your choice on your Hardware Node by issuing the following command:
# rpm -ihv vzkernel-name*.rpm

{{Note|You should not use the rpm –U command (where -U stands for "upgrade"); otherwise, all the kernels currently installed on the Node will be removed.}}

=== Configuring Boot Loader ===

In case you use the GRUB loader, it will be configured automatically. You should only make sure that the lines below are present in the /boot/grub/grub.conf file on the Node:

title Fedora Core (2.6.8-022stab029.1)
root (hd0,0)
kernel /vmlinuz-2.6.8-022stab029.1 ro root=/dev/sda5 quiet rhgb
initrd /initrd-2.6.8-022stab029.1.img

However, we recommend that you configure this file in the following way:
* Change Fedora Core to OpenVZ (just for clarity, so the OpenVZ kernels will not be mixed up with non OpenVZ ones).
* Remove all extra arguments from the kernel line, leaving only the root=... parameter.

At the end, the modified grub.conf file should look as follows:
title OpenVZ (2.6.8-022stab029.1)
root (hd0,0)
kernel /vmlinuz-2.6.8-022stab029.1 ro root=/dev/sda5
initrd /initrd-2.6.8-022stab029.1.img

=== Setting sysctl parameters ===

There are a number of kernel limits that should be set for OpenVZ to work correctly. OpenVZ is shipped with a tuned /etc/sysctl.conf file. Below are the contents of the relevant part of /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>

Please edit the file as described. To apply the changes issue the following command:

# sysctl -p

Alternatively, the changes will be applied upon the following reboot.

It is also worth mentioning that normally you should have forwarding (net.ipv4.ip_forward) turned on since the Hardware Node forwards the packets destined to or originating from the Virtual Private Servers.

After that, you should reboot your computer and choose "OpenVZ" on the boot loader menu.

=== Downloading and Installing OpenVZ Packages ===
After you have successfully installed and booted the OpenVZ kernel, you can proceed with installing the user-level tools for OpenVZ.
You should install the following OpenVZ packages:
* vzctl: this package is used to perform different tasks on the OpenVZ Virtual Private Servers (create, destroy, start, stop, set parameters etc.).
* vzquota: this package is used to manage the VPS quotas.
* vzpkg: this package is used to work with OpenVZ templates.

You can download the corresponding binary RPMs from http://openvz.org/download/utils/.

On the next step, you should install these utilities by using the following command:
# rpm –Uhv vzctl*.rpm vzquota*.rpm vzpkg*.rpm

{{Note|During the packages installation, you may be presented with a message telling you that rpm has found unresolved dependencies. In this case you have to resolve these dependencies first and then repeat the installation.}}

Now you can launch OpenVZ. To this effect, execute the following command:

# /etc/init.d/vz start

This will load all the needed OpenVZ kernel modules. During the next reboot, this script will be executed automatically.

=== Installing OS Templates ===

Template is a set of package files to be installed into a Container. Operating system templates are used to create new Containers with a pre-installed operating system. Therefore, you are bound to download at least one OS template and put it into <code>/vz/template/cache/</code> directory on the Hardware Node.

Links to all available OS templates at listed at [[Download/template/precreated]].

For example, this is how to download the CentOS 5 OS template:
<pre>
# cd /vz/template/cache
# wget http://download.openvz.org/template/precreated/centos-5-x86.tar.gz
</pre>

<noinclude>{{UG/Footer}}</noinclude>

User Guide/Installation and Preliminary Operations

2012-04-04T18:12:37Z

Paparaciz: separate el5 and el6 kernel versions

<noinclude>{{UG/Header}}</noinclude>
The current chapter provides exhaustive information on the process of installing and deploying your OpenVZ system including the pre-requisites and the stages you shall pass.

== Installation Requirements ==
After deciding on the structure of your OpenVZ system, you should make sure that all the Hardware Nodes where you are going to deploy OpenVZ for Linux meet the following system (hardware and software) and network requirements.

=== System Requirements ===
This section focuses on the hardware and software requirements for the OpenVZ for Linux software product.

==== Hardware Compatibility ====
The Hardware Node requirements for the standard 32-bit edition of OpenVZ are the following:
* IBM PC-compatible computer;
* Intel Celeron, Pentium II, Pentium III, Pentium 4, Xeon, or AMD Athlon CPU;
* At least 128 MB of RAM;
* Hard drive(s) with at least 4 GB of free disk space;
* Network card (either Intel EtherExpress100 (i82557-, i82558- or i82559-based) or 3Com (3c905 or 3c905B or 3c595) or RTL8139-based are recommended).

The computer should satisfy the Red Hat Enterprise Linux or Fedora Core hardware requirements (please, see the hardware compatibility lists at www.redhat.com).

The exact computer configuration depends on how many Virtual Private Servers you are going to run on the computer and what load these VPSs are going to produce. Thus, in order to choose the right configuration, please follow the recommendations below:
* CPUs. The more Virtual Private Servers you plan to run simultaneously, the more CPUs you need.
* Memory. The more memory you have, the more Virtual Private Servers you can run. The exact figure depends on the number and nature of applications you are planning to run in your Virtual Private Servers. However, on the average, at least 1 GB of RAM is recommended for every 20-30 Virtual Private Servers;
* Disk space. Each Virtual Private Server occupies 400–600 MB of hard disk space for system files in addition to the user data inside the Virtual Private Server (for example, web site content). You should consider it when planning disk partitioning and the number of Virtual Private Servers to run.

A typical 2–way Dell PowerEdge 1650 1u–mountable server with 1 GB of RAM and 36 GB of hard drives is suitable for hosting 30 Virtual Private Servers.

==== Software Compatibility ====

The Hardware Node should run either Red Hat Enterprise Linux 6 or 5, or CentOS 6 or 5, or Scientific Linux 6 or 5. The detailed instructions on installing these operating systems for the best performance of OpenVZ are provided in the next sections.

This requirement does not restrict the ability of OpenVZ to provide other Linux versions as an operating system for Virtual Private Servers. The Linux distribution installed in a Virtual Private Server may differ from that of the host OS.

=== Network Requirements ===
The network pre-requisites enlisted in this subsection will help you avoid delays and problems with making OpenVZ for Linux up and running. You should take care in advance of the following:
* Local Area Network (LAN) for the Hardware Node;
* Internet connection for the Hardware Node;
* Valid IP address for the Hardware Node as well as other IP parameters (default gateway, network mask, DNS configuration);
* At least one valid IP address for each Virtual Private Server. The total number of addresses should be no less than the planned number of Virtual Private Servers. The addresses may be allocated in different IP networks;
* If a firewall is deployed, check that IP addresses allocated for Virtual Private Servers are open for access from the outside.

== Installing and Configuring Host Operating System on Hardware Node ==

This section explains how to install Fedora Core 4 on the Hardware Node and how to configure it for OpenVZ. If you are using another distribution, please consult the corresponding installation guides about the installation specifics.

=== Choosing System Type ===

Please follow the instructions from your Installation Guide when installing the OS on your Hardware Node. After the first several screens, you will be presented with a screen specifying the installation type. OpenVZ requires Server System to be installed, therefore select “Server” at the dialog shown in the figure below.

Figure 2: Fedora Core Installation - Choosing System Type
It is not recommended to install extra packages on the Hardware Node itself due to the all-importance of Hardware Node availability (see the [[#Hardware Node Availability Considerations]] subsection in this chapter). You will be able to run any necessary services inside dedicated Virtual Private Servers.

=== Disk Partitioning ===

On the Disk Partitioning Setup screen, select Manual partition with Disk Druid. Do not choose automatic partitioning since this type of partitioning will create a disk layout intended for systems running multiple services. In case of OpenVZ, all your services shall run inside Virtual Private Servers.

Figure 3: Fedora Core Installation - Choosing Manual Partitioning

Create the following partitions on the Hardware Node:
{| class="wikitable"
! Partition !! Description !! Typical size
|-
| / || Root partition containing all Hardware Node operating system files | 4–12 Gb
|-
| swap || Paging partition for the Linux operating system || 2 times RAM or RAM + 2GB depending on available HD space
|-
| /vz || Partition to host OpenVZ templates and Virtual Private Servers || all the remaining space on the hard disk
|}

Many of the historical specifications for partitioning are outdated in an age where all hard drives are well above 20GB. So all minimums can be increased without any impact if you have plenty of drive space. It is suggested to use the ext3 or ext4 file system for the /vz partition. This partition is used for holding all data of the Virtual Private Servers existing on the Hardware Node. Allocate as much disk space as possible to this partition. It is not recommended to use the reiserfs file system as it is proved to be less stable than the ext3, and stability is of paramount importance for OpenVZ-based computers.

The root partition will host the operating system files. Fresh CentOS 6 install with basic server packages + OpenVZ kernel can occupy up to approximately 2 GB of disk space, so 4 GB is a good minimal size of the root partition. If you have plenty of drive space and think you may add additional software to the Node such as monitoring software then consider using more. Historically, the recommended size of the swap partition has been two times the size of physical RAM installed. Now, with minimum server RAM often above 2GB a more reasonable specification might be RAM + 2GB if RAM is above 2GB and HD space is limited.

=== Finishing OS Installation ===
After the proper partitioning of your hard drive(s), proceed in accordance with your OS Installation Guide.
While on the Network Configuration screen, you should ensure the correctness of the Hardware Node’s IP address, host name, DNS, and default gateway information. If you are using DHCP, make sure that it is properly configured. If necessary, consult your network administrator.
On the Firewall Configuration screen, choose No firewall. Option Enable SELinux should be set to Disabled.

Fedora Core Installation - Disabling Firewall and SELinux
After finishing the installation and rebooting your computer, you are ready to install OpenVZ on your system.

== Installing OpenVZ Software ==

=== Downloading and Installing OpenVZ Kernel ===

First of all, you should download the kernel binary RPM from http://openvz.org/download/kernel/. You need only one kernel RPM, so please choose the appropriate kernel binary depending on your hardware:

* if you use Red Hat Enterprise 5, or Centos 5, or Scientific Linux 5:
* If there is more than one CPU available on your Hardware Node (or a CPU with hyperthreading), select the vzkernel-smp RPM.
* If there is more than 4 Gb of RAM available, select the vzkernel-enterprise RPM.
* Otherwise, select the uniprocessor kernel RPM (vzkernel-version).

* if you use Red Hat Enterprise 6, or Centos 6, or Scientific Linux 6:
*select the uniprocessor kernel RPM (vzkernel-version).

Next, you shall install the kernel RPM of your choice on your Hardware Node by issuing the following command:
# rpm -ihv vzkernel-name*.rpm

{{Note|You should not use the rpm –U command (where -U stands for "upgrade"); otherwise, all the kernels currently installed on the Node will be removed.}}

=== Configuring Boot Loader ===

In case you use the GRUB loader, it will be configured automatically. You should only make sure that the lines below are present in the /boot/grub/grub.conf file on the Node:

title Fedora Core (2.6.8-022stab029.1)
root (hd0,0)
kernel /vmlinuz-2.6.8-022stab029.1 ro root=/dev/sda5 quiet rhgb
initrd /initrd-2.6.8-022stab029.1.img

However, we recommend that you configure this file in the following way:
* Change Fedora Core to OpenVZ (just for clarity, so the OpenVZ kernels will not be mixed up with non OpenVZ ones).
* Remove all extra arguments from the kernel line, leaving only the root=... parameter.

At the end, the modified grub.conf file should look as follows:
title OpenVZ (2.6.8-022stab029.1)
root (hd0,0)
kernel /vmlinuz-2.6.8-022stab029.1 ro root=/dev/sda5
initrd /initrd-2.6.8-022stab029.1.img

=== Setting sysctl parameters ===

There are a number of kernel limits that should be set for OpenVZ to work correctly. OpenVZ is shipped with a tuned /etc/sysctl.conf file. Below are the contents of the relevant part of /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>

Please edit the file as described. To apply the changes issue the following command:

# sysctl -p

Alternatively, the changes will be applied upon the following reboot.

It is also worth mentioning that normally you should have forwarding (net.ipv4.ip_forward) turned on since the Hardware Node forwards the packets destined to or originating from the Virtual Private Servers.

After that, you should reboot your computer and choose "OpenVZ" on the boot loader menu.

=== Downloading and Installing OpenVZ Packages ===
After you have successfully installed and booted the OpenVZ kernel, you can proceed with installing the user-level tools for OpenVZ.
You should install the following OpenVZ packages:
* vzctl: this package is used to perform different tasks on the OpenVZ Virtual Private Servers (create, destroy, start, stop, set parameters etc.).
* vzquota: this package is used to manage the VPS quotas.
* vzpkg: this package is used to work with OpenVZ templates.

You can download the corresponding binary RPMs from http://openvz.org/download/utils/.

On the next step, you should install these utilities by using the following command:
# rpm –Uhv vzctl*.rpm vzquota*.rpm vzpkg*.rpm

{{Note|During the packages installation, you may be presented with a message telling you that rpm has found unresolved dependencies. In this case you have to resolve these dependencies first and then repeat the installation.}}

Now you can launch OpenVZ. To this effect, execute the following command:

# /etc/init.d/vz start

This will load all the needed OpenVZ kernel modules. During the next reboot, this script will be executed automatically.

=== Installing OS Templates ===

Template is a set of package files to be installed into a Container. Operating system templates are used to create new Containers with a pre-installed operating system. Therefore, you are bound to download at least one OS template and put it into <code>/vz/template/cache/</code> directory on the Hardware Node.

Links to all available OS templates at listed at [[Download/template/precreated]].

For example, this is how to download the CentOS 5 OS template:
<pre>
# cd /vz/template/cache
# wget http://download.openvz.org/template/precreated/centos-5-x86.tar.gz
</pre>

<noinclude>{{UG/Footer}}</noinclude>

VPN via the TUN/TAP device

2012-01-10T08:55:47Z

Paparaciz: spam link by 119.73.78.158

This article describes how to use VPN via the TUN/TAP device inside a [[container]].

== Kernel TUN/TAP support ==
OpenVZ supports VPN inside a container via kernel TUN/TAP module and device.
To allow container #101 to use the TUN/TAP device the following should be done:

Make sure the '''tun''' module has been already loaded on the [[hardware node]]:
lsmod | grep tun

If it is not there, use the following command to load '''tun''' module:
modprobe tun

To make sure that '''tun''' module will be automatically loaded on every reboot you can also add it or into <code>/etc/modules.conf</code> (on RHEL see <code>/etc/sysconfig/modules/</code> directory).

== Granting container an access to TUN/TAP ==
Allow your container to use the tun/tap device by running the following commands on the host node:

vzctl set 101 --devnodes net/tun:rw --save

== Configuring VPN inside container ==
After the configuration steps above are done it is possible to use VPN software working with TUN/TAP inside
container just like on a usual standalone Linux box.

The following software can be used for VPN with TUN/TAP:
* Tinc (http://tinc-vpn.org)
* OpenVPN (http://openvpn.net)
* Virtual TUNnel (http://vtun.sourceforge.net)

== Reaching hosts behind VPN container ==
In order to reach hosts behind VPN container you must configure it to use a VETH interface instead a VENET one, at least with an OpenVPN server.

With a VENET interface you will only reach the VPN container.

To use a VETH device follow [[Veth]] article.

If you insist on using a VENET interface and need to reach hosts behind the OpenVPN VE then you can use source NAT. You need to mangle source packets so that they appear to originate from the OpenVPN server VE.

== Tinc problems ==

Using the default venet0:0 interface on the container, tinc seems to have problems as it complains the port 655 is already used on 0.0.0.0.

Netstat shows that the port 655 is available:

<pre>
root@132 / [3]# netstat -l
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 localhost.localdom:8001 *:* LISTEN
tcp 0 0 *:2223 *:* LISTEN
tcp6 0 0 [::]:2223 [::]:* LISTEN
udp6 0 0 [::]:talk [::]:*
udp6 0 0 [::]:ntalk [::]:*
Active UNIX domain sockets (only servers)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ACC ] STREAM LISTENING 4831020 /var/run/uml-utilities/uml_switch.ctl
</pre>

Starting the Tincd daemon where it complains that port 655 is not available:

<pre>
root@132 / [4]# tincd -n myvpn
root@132 / [5]# tail -f /var/log/syslog
Jul 26 14:08:01 132 /USR/SBIN/CRON[15159]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 26 14:37:42 132 -- MARK --
Jul 26 14:57:42 132 -- MARK --
Jul 26 15:08:01 132 /USR/SBIN/CRON[15178]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 26 15:11:23 132 tinc.myvpn[15139]: Got TERM signal
Jul 26 15:11:23 132 tinc.myvpn[15139]: Terminating
Jul 26 15:11:37 132 tinc.myvpn[15191]: tincd 1.0.8 (Aug 14 2007 13:51:23) starting, debug level 0
Jul 26 15:11:37 132 tinc.myvpn[15191]: /dev/net/tun is a Linux tun/tap device (tun mode)
Jul 26 15:11:37 132 tinc.myvpn[15191]: Can't bind to 0.0.0.0 port 655/tcp: Address already in use
Jul 26 15:11:37 132 tinc.myvpn[15191]: Ready
^C
root@132 / [6]#
</pre>

An echo to Bindv6only (see [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=440150 discussion here]) seems to resolve the problem:

<pre>
root@132 / [12]# echo 1 > /proc/sys/net/ipv6/bindv6only
</pre>

Or put in your /etc/sysctl.conf file:

<pre>
net.ipv6.bindv6only = 1
</pre>

Then apply the changes with:

<pre>
root@132 / [14]# sysctl -p
</pre>

== The tunctl problem ==
Unfortunately, you are limited to [http://forum.openvz.org/index.php?t=msg&th=4280&goto=22066&#msg_22066 non-persistent tunnels inside the VEs]:

<pre>
# tunctl
enabling TUNSETPERSIST: Operation not permitted
</pre>

Get a patched tunctl [https://github.com/xl0/uml-utilities here], and run it with the -n option. It will create a non-persistent tun device and sleep instead of terminating, to keep the device from deletion. To remove the tunnel, kill the tunctl process.

== Troubleshooting ==
If NAT is needed within the VE, this error will occur on attempts to use NAT:

# iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o venet0 -j MASQUERADE
iptables v1.4.3.2: can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.

The solution is given here:

http://kb.parallels.com/en/5228

Also see page 69-70 of:

http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf

Note that the above steps do not solve the problem if a gentoo VE sits on a Centos HN; it's still an unsolved mystery.

== External links ==
* [http://vtun.sourceforge.net Virtual TUNnel]
* [http://openvpn.net OpenVPN]
* [http://tinc-vpn.org Tinc]
* [http://openvpn.net/index.php/access-server/howto-openvpn-as/186-how-to-run-access-server-on-a-vps-container.html How to run OpenVPN Access Server in OpenVZ]
* [http://kb.parallels.com/en/696 Parallels KB#696: Is VPN via the TUN/TAP device supported inside a Container?]
[[Category: HOWTO]]
[[Category: Networking]]

VPN via the TUN/TAP device

2012-01-10T08:55:11Z

Paparaciz: spam link by 173.234.235.73

This article describes how to use VPN via the TUN/TAP device inside a [[container]].

== Kernel TUN/TAP support ==
OpenVZ supports VPN inside a container via kernel TUN/TAP module and device.
To allow container #101 to use the TUN/TAP device the following should be done:

Make sure the '''tun''' module has been already loaded on the [[hardware node]]:
lsmod | grep tun

If it is not there, use the following command to load '''tun''' module:
modprobe tun

To make sure that '''tun''' module will be automatically loaded on every reboot you can also add it or into <code>/etc/modules.conf</code> (on RHEL see <code>/etc/sysconfig/modules/</code> directory).

== Granting container an access to TUN/TAP ==
Allow your container to use the tun/tap device by running the following commands on the host node:

vzctl set 101 --devnodes net/tun:rw --save

== Configuring VPN inside container ==
After the configuration steps above are done it is possible to use VPN software working with TUN/TAP inside
container just like on a usual standalone Linux box.

The following software can be used for VPN with TUN/TAP:
* Tinc (http://tinc-vpn.org)
* OpenVPN (http://openvpn.net)
* Virtual TUNnel (http://vtun.sourceforge.net)

== Reaching hosts behind VPN container ==
In order to reach hosts behind VPN container you must configure it to use a VETH interface instead a VENET one, at least with an OpenVPN server.

With a VENET interface you will only reach the VPN container.

To use a VETH device follow [[Veth]] article.

If you insist on using a VENET interface and need to reach hosts behind the OpenVPN VE then you can use source NAT. You need to mangle source packets so that they appear to originate from the OpenVPN server VE.

== Tinc problems ==

Using the default venet0:0 interface on the container, tinc seems to have problems as it complains the port 655 is already used on 0.0.0.0.

Netstat shows that the port 655 is available:

<pre>
root@132 / [3]# netstat -l
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 localhost.localdom:8001 *:* LISTEN
tcp 0 0 *:2223 *:* LISTEN
tcp6 0 0 [::]:2223 [::]:* LISTEN
udp6 0 0 [::]:talk [::]:*
udp6 0 0 [::]:ntalk [::]:*
Active UNIX domain sockets (only servers)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ACC ] STREAM LISTENING 4831020 /var/run/uml-utilities/uml_switch.ctl
</pre>

Starting the Tincd daemon where it complains that port 655 is not available:

<pre>
root@132 / [4]# tincd -n myvpn
root@132 / [5]# tail -f /var/log/syslog
Jul 26 14:08:01 132 /USR/SBIN/CRON[15159]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 26 14:37:42 132 -- MARK --
Jul 26 14:57:42 132 -- MARK --
Jul 26 15:08:01 132 /USR/SBIN/CRON[15178]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 26 15:11:23 132 tinc.myvpn[15139]: Got TERM signal
Jul 26 15:11:23 132 tinc.myvpn[15139]: Terminating
Jul 26 15:11:37 132 tinc.myvpn[15191]: tincd 1.0.8 (Aug 14 2007 13:51:23) starting, debug level 0
Jul 26 15:11:37 132 tinc.myvpn[15191]: /dev/net/tun is a Linux tun/tap device (tun mode)
Jul 26 15:11:37 132 tinc.myvpn[15191]: Can't bind to 0.0.0.0 port 655/tcp: Address already in use
Jul 26 15:11:37 132 tinc.myvpn[15191]: Ready
^C
root@132 / [6]#
</pre>

An echo to Bindv6only (see [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=440150 discussion here]) seems to resolve the problem:

<pre>
root@132 / [12]# echo 1 > /proc/sys/net/ipv6/bindv6only
</pre>

Or put in your /etc/sysctl.conf file:

<pre>
net.ipv6.bindv6only = 1
</pre>

Then apply the changes with:

<pre>
root@132 / [14]# sysctl -p
</pre>

== The tunctl problem ==
Unfortunately, you are limited to [http://forum.openvz.org/index.php?t=msg&th=4280&goto=22066&#msg_22066 non-persistent tunnels inside the VEs]:

<pre>
# tunctl
enabling TUNSETPERSIST: Operation not permitted
</pre>

Get a patched tunctl [https://github.com/xl0/uml-utilities here], and run it with the -n option. It will create a non-persistent tun device and sleep instead of terminating, to keep the device from deletion. To remove the tunnel, kill the tunctl process.

== Troubleshooting ==
If NAT is needed within the VE, this error will occur on attempts to use NAT:

# iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o venet0 -j MASQUERADE
iptables v1.4.3.2: can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.

The solution is given here:

http://kb.parallels.com/en/5228

Also see page 69-70 of:

http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf

Note that the above steps do not solve the problem if a gentoo VE sits on a Centos HN; it's still an unsolved mystery.

== External links ==
* [http://vtun.sourceforge.net Virtual TUNnel]
* [http://openvpn.net OpenVPN]
* [http://tinc-vpn.org Tinc]
* [http://www.purevpn.com/ buy vpn online]
* [http://openvpn.net/index.php/access-server/howto-openvpn-as/186-how-to-run-access-server-on-a-vps-container.html How to run OpenVPN Access Server in OpenVZ]
* [http://kb.parallels.com/en/696 Parallels KB#696: Is VPN via the TUN/TAP device supported inside a Container?]
[[Category: HOWTO]]
[[Category: Networking]]

Migration from one HN to another

2010-11-24T09:02:13Z

Paparaciz: migration from bigger kernel version to smaller not possible

{{wikify}}

The vzmigrate script is used to migrate a [[container]] from one [[Hardware Node]] to another.

== Setting up SSH keys ==

You first have to setup SSH to permit the old HN to be able to login to the new HN without a password prompt. Run the following on the old HN.

<pre>[root@OpenVZ ~]# ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Created directory '/root/.ssh'.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
74:7a:3e:7f:27:2f:42:bb:52:4c:ad:55:31:6f:79:f2 root@OpenVZ.ics.local
[root@OpenVZ ~]# cd .ssh/
[root@OpenVZ .ssh]# ls -al
total 20
drwx------ 2 root root 4096 Aug 11 09:41 .
drwxr-x--- 5 root root 4096 Aug 11 09:40 ..
-rw------- 1 root root 887 Aug 11 09:41 id_rsa
-rw-r--r-- 1 root root 231 Aug 11 09:41 id_rsa.pub
[root@OpenVZ .ssh]# scp id_rsa.pub root@10.1.5.6:./id_rsa.pub
The authenticity of host '10.1.5.6 (10.1.5.6)' can't be established.
RSA key fingerprint is 3f:2a:26:15:e4:37:e2:06:b8:4d:20:ee:3a:dc:c1:69.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.1.5.6' (RSA) to the list of known hosts.
root@10.1.5.6's password:
id_rsa.pub 100% 231 0.2KB/s 00:00</pre>

Run the following on the new HN.

<pre>[root@Char ~]# cd .ssh/
[root@Char .ssh]# touch authorized_keys2
[root@Char .ssh]# chmod 600 authorized_keys2
[root@Char .ssh]# cat ../id_rsa.pub >> authorized_keys2
[root@Char .ssh]# rm ../id_rsa.pub
rm: remove regular file `../id_rsa.pub'? y</pre>

Run the following on the old HN.

<pre>[root@OpenVZ .ssh]# ssh -2 -v root@10.1.5.6
OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to 10.1.5.6 [10.1.5.6] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/id_rsa type 1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3
debug1: match: OpenSSH_4.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.9p1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host '10.1.5.6' is known and matches the RSA host key.
debug1: Found key in /root/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Next authentication method: gssapi-with-mic
debug1: An invalid name was supplied
Cannot determine realm for numeric host address

debug1: An invalid name was supplied
Cannot determine realm for numeric host address

debug1: Next authentication method: publickey
debug1: Offering public key: /root/.ssh/id_rsa
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Offering public key: /root/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 149
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
Last login: Thu Aug 9 16:41:30 2007 from 10.1.5.20
[root@Char ~]# exit</pre>

== Prerequisites ==

Make sure:
* you have at least one good backup of the virtual machine you intend to migrate
* rsync is installed on the target host
* In general you cannot migrate from bigger kernel versions to smaller ones

== vzmigrate usage ==

Now that the vzmigrate script will function, a little bit on vzmigrate.

<pre>This program is used for container migration to another node
Usage:
vzmigrate [-r yes|no] [--ssh=<options>] [--keep-dst] [--online] [-v]
destination_address <CTID>
Options:
-r, --remove-area yes|no
Whether to remove container on source HN for successfully migrated container.
--ssh=<ssh options>
Additional options that will be passed to ssh while establishing
connection to destination HN. Please be careful with options
passed, DO NOT pass destination hostname.
--keep-dst
Do not clean synced destination container private area in case of some
error. It makes sense to use this option on big container migration to
avoid syncing container private area again in case some error
(on container stop for example) occurs during first migration attempt.
--online
Perform online (zero-downtime) migration: during the migration the
container hangs for a while and after the migration it continues working
as though nothing has happened.
-v
Verbose mode. Causes vzmigrate to print debugging messages about
its progress (including some time statistics).</pre>

=== Example ===
Here is an example of migrating container 101 from the current HN to one at 10.1.5.6:

<pre>[root@OpenVZ .ssh]# vzmigrate 10.1.5.6 101
OPT:10.1.5.6
Starting migration of container 101 on 10.1.5.6
Preparing remote node
Initializing remote quota
Syncing private
Syncing 2nd level quota
Turning quota off
Cleanup</pre>

== Migrate all running containers ==

Here's a simple shell script that will migrate each container one after another. Just pass the destination host node as the single argument to the script. Feel free to add the -v flag to the vzmigrate flags if you'd like to see it execute with the verbose option:

for CT in $(vzlist -H -o veid); do vzmigrate --remove-area no --keep-dst $1 $CT; done

== Additional Information ==

You can also use this guide to migrate from OpenVZ to Proxmox VE

[[Category:HOWTO]]

Talk:Download/kernel/rhel4/023stab052.4/changes

2010-10-09T16:11:14Z

Paparaciz: Created page with 'you forgot to revert edits by spammer'

you forgot to revert edits by spammer

News/events/past

2010-06-08T17:34:46Z

Paparaciz: Undo revision 8715 by 207.68.153.156 (Talk)

{{Note|this page lists events that has happened already, kept here just for historical reasons. For future events, see [[News/events]].}}
__TOC__
 
== Linux Foundation Collaboration Summit ==
[[File:Linux foundation collaboration summit-logo.png|left]]
''San Francisco, CA, Apr 14-16 2010'' 

Kir Kolyshkin will deliver a talk titled "Containers and Namespaces in the Linux Kernel" during the Virtualization track.

 
== Southern California Linux Expo aka SCALE 8x ==
''Los Angeles, CA, Feb 19-21 2009'' 
[[File:SCALE8x.gif|left]]

Kir Kolyshkin will be there presenting an OpenVZ booth.

 
== Utah Open Source Conference 2009 ==
''Sandy, Utah, USA, 8-10 Oct, 2009'' 
[[Image:UTOCS2009.png|left]]
Scott Dowdle will host an OpenVZ booth, plus will also be giving a presentation entitled [http://2009.utosc.com/presentation/52/ Introduction to OS Virtualization, Containers, and OpenVZ].

 
== LinuxTag 2009 ==
''Berlin, Germany, June 24-27, 2009'' 
[[Image:LinuxTag.gif|left]]
OpenVZ project will have a booth at this year's LinuxTag -- one of the biggest and greatest Linux shows in Germany.

 
== Linux Symposium 2009 ==
''Montreal, Canada, July 13-17 2009'' 
[[Image:Linux symposium 09.png|left]]
It's a third time OpenVZ takes part in Linux Symposium, and a first time it's being held in Montreal! The project will present a [http://www.linuxsymposium.org/2009/view_abstract.php?content_key=31 tutorial on installing/using OpenVZ], and [http://www.linuxsymposium.org/2009/view_abstract.php?content_key=32 a BoF for OpenVZ users and developers].
 
<hr color="#ddcef2"/>

== Southern California Linux Expo 2008 ==
[[Image:Scale7x.gif|left]]
''Los Angeles, USA, February 20-22, 2009''

OpenVZ project will have a booth, plus Kir Kolyshkin will deliver [http://scale7x.socallinuxexpo.org/conference-info/speakers/kir-kolyshkin a talk] titled "Recent Advances in the Linux Kernel Resource Management"
 
<hr color="#ddcef2"/>

[[Image:LinuxWorld logo.gif|left|180px]]
== LinuxWorld Expo ==
''San Francisco, California, USA, August 5-7, 2008''

OpenVZ project will have a booth at the .org Pavilion at the upcoming [http://www.linuxworldexpo.com/live/12 LinuxWorld Conference and Expo 2008]. Plus, project leader Kir Kolyshkin will deliver [http://www.linuxworldexpo.com/live/12/conference//tracks/tracksessions/Virtualization/QMONYB00BHXK a talk titled "Containers, Virtualization, and Live Migration"].
 
<hr color="#ddcef2"/>

[[Image: Scale6x.gif|left|100px]]
== Southern California Linux Expo ==
''Los Angeles, USA, February 8-10, 2008''

OpenVZ will have a booth at the show, plus Kir Kolyshkin and Andrey Mirkin will present a talk titled "Containers Checkpointing and Live Migration".

For more details, check [http://socallinuxexpo.com/ socallinuxexpo.com].
 
<hr color="#ddcef2"/>

[[Image:FLoridaLinuxshow2.jpg|left|100px]]
== Florida Linux Show ==
''Jacksonville, FL, USA, February 11, 2008''

Kir Kolyshkin will present an introductory talk about OpenVZ.

For more details, check [http://www.floridalinuxshow.com/ floridalinuxshow.com].
 
<hr color="#ddcef2"/>

[[Image:Linuxfestnorthwest.jpg|left|100px]]
== LinuxFest Northwest ==
'' Bellingham, WA, USA, April 26 and 27, 2008''

Scott Dowdle is signed up to give a presentation on OpenVZ and OS virtualization.

Check [http://linuxfestnorthwest.org/ linuxfestnorthwest.org] for more details.
 
<hr color="#ddcef2"/>

[[Image:Linux Symposium 2008.gif|left|180px]]
== Linux Symposium and Containers mini-summit==
''Ottawa, Canada, July 23-26, 2008''

[[Containers/Mini-summit 2008|Containers mini-summit]] will take place 22nd of July 2008, just before the conference. See [[Containers/Mini-summit 2008]] for more info.

At the Linux Symposium, our kernel developer [http://www.linuxsymposium.org/2008/view_bio.php?id=3175 Andrey Mirkin] will present [http://www.linuxsymposium.org/2008/view_abstract.php?content_key=17 a talk titled "Containers Checkpointing and Live Migration"].
 
<hr color="#ddcef2"/>

[[Image:LinuxWorld logo.gif|left|180px]]
== LinuxWorld Expo ==
''San Francisco, California, USA, August 5-7, 2008''

OpenVZ project will have a booth at the .org Pavilion at the upcoming [http://www.linuxworldexpo.com/live/12 LinuxWorld Conference and Expo 2008]. Plus, project leader Kir Kolyshkin will deliver [http://www.linuxworldexpo.com/live/12/conference//tracks/tracksessions/Virtualization/QMONYB00BHXK a talk titled "Containers, Virtualization, and Live Migration"].

User talk:207.68.153.156

2010-06-08T17:05:21Z

Paparaciz:

seo spam in News/events/past

User talk:207.68.153.156

2010-06-08T17:03:50Z

Paparaciz: Created page with 'seo spam'

seo spam