OpenVZ Virtuozzo Containers Wiki - User contributions [en]

User talk:Fayette

2010-11-04T10:37:30Z

Fayette: /* Ubuntu Lucid */

== Ubuntu Lucid ==
* (from comment in [[Ubuntu Lucid]] page) Why zlib1g-dev package is needed? There is some strange if you have obtained a 2.6.32.14-ovz32 kernel, when with the guide you should be compiling at least for 2.6.32.22-openvz. Have you seen the updated guide? --[[User:Narcisgarcia|Narcis Garcia]] 10:06, 4 November 2010 (UTC)

* I can't say why it was needed other than the compile failed with a missing zlib.h, if I recall correctly. I followed the instructions on the web site. I can't say for sure how I arrived at 2.6.32.14 but I recall having some difficulty locating the kernel source. I will go back and see if I can find a newer kernel and try again. Thanks, Jim.

Ubuntu Lucid

2010-11-04T09:49:22Z

Fayette: Added a dependency and results.

There is a guide to install and run OpenVZ in Ubuntu GNU/Linux 10.04 LTS (Lucid Lynx), when the patch for Linux 2.6.32 is not yet completely stable:

[https://help.ubuntu.com/community/OpenVZ#10.04%20LTS%20(Lucid) https://help.ubuntu.com/community/OpenVZ#10.04 LTS (Lucid)]

Note: there is at least one missing dependency. Be sure zlib1g-dev is installed before you attempt to build an OpenVZ kernel using this guide.

uname -a
Linux chinaberry 2.6.32.14-ovz32 #1 SMP Sat Oct 30 09:22:38 EDT 2010 i686 GNU/Linux

It's working for me.

[[Category:Debian]]
[[Category:Ubuntu]]

Locales inside VE

2010-11-04T09:38:09Z

Fayette: Added one more fix

== Problem description ==

After creating a VE (e.g. using centos-4-i386-default template)
running perl (any perl script), results in the warning message:

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LANG = "en_US"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C")

Another common problem is with PostgreSQL, if it won't start up and you see something like this in your <pgsql_data_dir>/serverlog:

invalid value for parameter "lc_messages": "en_US.UTF-8"

== Resolution ==

Some of templates have removed locales inside, since locales take really much space (~20Mb)
while not needed in most cases (except for the default "C" locale).

So in this example '''/usr/lib/locale/en_US/LC_TIME''' and other files are missing.

== Fix 1 ==

reinstall glibc-common package using the command:
# rpm -ihv --force glibc-common.rpm

== Fix 2 ==

Or '''disable''' overriding of LC_* variables in '''/etc/ssh/sshd_config''':

# Allow client to pass locale environment variables
AcceptEnv LANG LC_*

to

#AcceptEnv LANG LC_*

so the default LC will be used.

== Fix 3 ==

To fix this permanently for all new vzs you create, edit your '''/vz/templates/<distro>/<version>/<platform>/.rpmmacros''' and change the line %_install_langs C
to include the language(s) you want, for example:

%_install_langs C:pt_PT:pt_PT.UTF-8:en_US:en_US.UTF-8

or simply

%_install_langs all

After this you will need to rebuild your [[OS template cache]], for example:

vzpkgcache -r centos-4-i386-vmirth
vzpkgcache centos-4-i386-vmirth

[[Category: Troubleshooting]]
[[Category: Templates]]

== Fix 4 (working on Ubuntu 8.04) ==

Simply install this package:

aptitude install language-pack-en-base

== Fix 5 (works on Debian-like systems) ==

Generate the locale:
dpkg-reconfigure locales
select the one missing and generate.

== Fix 6 (should work on recent Debian and Ubuntu distros) ==

export LANGUAGE=en_US.UTF-8
export LANG=en_US.UTF-8
export LC_ALL=en_US.UTF-8
locale-gen en_US.UTF-8
dpkg-reconfigure locales

Obviously change the en_US to your preferred language.

[[Category: Troubleshooting]]
[[Category: Templates]]

Control panels

2009-09-17T14:55:39Z

Fayette: /* Proprietary / non-free */

This page contains links to different control panels for OpenVZ, written by third parties. If you know the project that's missing here, please add it.

== Free software / Open source (in alphabetical order) ==
* fosvm (Free Open Source Virtual Machine manager): [http://fosvm.sourceforge.net/ homepage] | Uses php and bash scripts, monitors bandwidth, Version 0.02a. Last updated 2009-05-15.
* Proxmox Virtual Environment: [http://pve.proxmox.com Proxmox VE Wiki] - including bare-metal ISO installer
* [http://solukom.com/software/slkvm slkvm]: console scripts to handle vz virtualization in a two node cluster.
* unxsVZ OpenVZ Infrastructure Manager: [http://openisp.net/openisp/unxsVZ unxsVZ Trac Wiki] | Includes autonomic UBC adjusting and per container traffic graphs. Supports hot-spare clones and mount/umount conf file templates. Very active development. Last change to public svn code base June 20, 2009.
* Webmin: [http://www.webmin.com/ homepage] | [http://www.webmin.com/cgi-bin/search_third.cgi?search=OpenVZ OpenVZ plugin] | Version 1.0, last updated 2006-02-07
* WebVZ: [http://webvz.sourceforge.net/ homepage] Uses Ruby on Rails which makes it a poor choice for Debian, Ubuntu and other .deb style distros. In the comments section of http://www.howtoforge.com/install-webvz-2.0-on-debian-etch-to-administrate-openvz there is a suggestion of how to get this one running under Ubuntu Hardy. The authors like it.

== Proprietary / non-free ==
* Panenthe: [http://www.panenthe.com/ homepage (English)] • [http://www.panenthe.com/products/panenthe-media/cat_id=4/ Screen shots]
* vePortal: [http://www.veportal.com/ homepage (English)] • [http://www.veportal.com/index.php?cmd=screenshots Screen shots]
* FluidVM: [http://www.fluidvm.com Home Page]
* VZ-Manager: [http://vzmanager.de/ homepage (German)]
* vzAdmin: [http://www.vzAdmin.info/ homepage (German)]
* Aventurin{e}: [http://www.aventurin.net/ homepage (English)]
* SolusVM [http://www.solusvm.com homepage], Appears to be reasonably priced. Advertised as $10 per node.
*vcPanel :[http://vcpanel.net Home Page], The first centralized VPS control panel for managing VPS around the globe [http://vcpanel.net/Demo Demo]

== Frozen projects ==
* VZAdmin: [http://www.ronny-goerner.de/ homepage] ''seems not available now''
* WVZ: [http://homaly.dunanet.hu/wvz/ homepage] ''seems frozen''
* New OpenVZ Web Based Control Panel by rsailor: {{forum|230}} ''seems not available now''
* EasyVZ: [http://easyvz.sourceforge.net/ screenshots] | [http://sourceforge.net/projects/easyvz sf.net project page] (little bit outdated, but working and free. Last update Feb 2007) (requires Unix/Linux)
* Mwamko: [http://mwamko.devjavu.com/ homepage] Last activity May 2007
* RoboVZ: [http://sharesource.org/project/robovz homepage] {{forum|2559}} Lots of promises since announced in May 2007, nothing usable yet. Possibly GPL license. No activity in 2 years, calling it frozen.
* HyperVM: [http://lxlabs.com/software/hypervm/ homepage] - No longer being developed after the sole developer sadly committed suicide in June 09.
* Vtonf: [http://www.vtonf.com/ homepage] | According to the documentation only runs on CentOS 4.5 or higher. Last change April 2008 - No longer supported. Does not work on CentOS 5+. Web page is no longer valid. Consider this one dead.
* WIVZ/GIVZ: [http://source.icenetx.net/ homepage] Release scheduled for October 2008 - never released. Unknown license.

== In development ==
* VS-Admin: [http://www.veportal.com/ homepage] Beta testers wanted (19-06-2009) - Project Changed to vePortal.
* speedCP [http://blog.vpsspeed.com/tag/speedcp homepage] Developed by an in-house team from VPSSpeed.com - Private licensing on request.
* SolusVM [http://www.solusvm.com homepage] In development - Initial release release scheduled for August 21st 2009. Released August 14th 1009.
* VZWave [http://www.vzwave.com homepage] In development - release expected July 09.
* DTC-Xen [http://www.gplhost.com/software-dtc-xen.html homepage] - Currently being ported to OpenVZ by its main developers.
* vpsAdmin [http://www.vpsadmin.org/ homepage] - In development - available from mercurial repository, GPLv3 license, stable release scheduled for October 1, 2009

Control panels

2009-09-17T14:53:50Z

Fayette: /* In development */

This page contains links to different control panels for OpenVZ, written by third parties. If you know the project that's missing here, please add it.

== Free software / Open source (in alphabetical order) ==
* fosvm (Free Open Source Virtual Machine manager): [http://fosvm.sourceforge.net/ homepage] | Uses php and bash scripts, monitors bandwidth, Version 0.02a. Last updated 2009-05-15.
* Proxmox Virtual Environment: [http://pve.proxmox.com Proxmox VE Wiki] - including bare-metal ISO installer
* [http://solukom.com/software/slkvm slkvm]: console scripts to handle vz virtualization in a two node cluster.
* unxsVZ OpenVZ Infrastructure Manager: [http://openisp.net/openisp/unxsVZ unxsVZ Trac Wiki] | Includes autonomic UBC adjusting and per container traffic graphs. Supports hot-spare clones and mount/umount conf file templates. Very active development. Last change to public svn code base June 20, 2009.
* Webmin: [http://www.webmin.com/ homepage] | [http://www.webmin.com/cgi-bin/search_third.cgi?search=OpenVZ OpenVZ plugin] | Version 1.0, last updated 2006-02-07
* WebVZ: [http://webvz.sourceforge.net/ homepage] Uses Ruby on Rails which makes it a poor choice for Debian, Ubuntu and other .deb style distros. In the comments section of http://www.howtoforge.com/install-webvz-2.0-on-debian-etch-to-administrate-openvz there is a suggestion of how to get this one running under Ubuntu Hardy. The authors like it.

== Proprietary / non-free ==
* Panenthe: [http://www.panenthe.com/ homepage (English)] • [http://www.panenthe.com/products/panenthe-media/cat_id=4/ Screen shots]
* vePortal: [http://www.veportal.com/ homepage (English)] • [http://www.veportal.com/index.php?cmd=screenshots Screen shots]
* FluidVM: [http://www.fluidvm.com Home Page]
* VZ-Manager: [http://vzmanager.de/ homepage (German)]
* vzAdmin: [http://www.vzAdmin.info/ homepage (German)]
* Aventurin{e}: [http://www.aventurin.net/ homepage (English)]
* SolusVM [http://www.solusvm.com homepage]
*vcPanel :[http://vcpanel.net Home Page], The first centralized VPS control panel for managing VPS around the globe [http://vcpanel.net/Demo Demo]

== Frozen projects ==
* VZAdmin: [http://www.ronny-goerner.de/ homepage] ''seems not available now''
* WVZ: [http://homaly.dunanet.hu/wvz/ homepage] ''seems frozen''
* New OpenVZ Web Based Control Panel by rsailor: {{forum|230}} ''seems not available now''
* EasyVZ: [http://easyvz.sourceforge.net/ screenshots] | [http://sourceforge.net/projects/easyvz sf.net project page] (little bit outdated, but working and free. Last update Feb 2007) (requires Unix/Linux)
* Mwamko: [http://mwamko.devjavu.com/ homepage] Last activity May 2007
* RoboVZ: [http://sharesource.org/project/robovz homepage] {{forum|2559}} Lots of promises since announced in May 2007, nothing usable yet. Possibly GPL license. No activity in 2 years, calling it frozen.
* HyperVM: [http://lxlabs.com/software/hypervm/ homepage] - No longer being developed after the sole developer sadly committed suicide in June 09.
* Vtonf: [http://www.vtonf.com/ homepage] | According to the documentation only runs on CentOS 4.5 or higher. Last change April 2008 - No longer supported. Does not work on CentOS 5+. Web page is no longer valid. Consider this one dead.
* WIVZ/GIVZ: [http://source.icenetx.net/ homepage] Release scheduled for October 2008 - never released. Unknown license.

== In development ==
* VS-Admin: [http://www.veportal.com/ homepage] Beta testers wanted (19-06-2009) - Project Changed to vePortal.
* speedCP [http://blog.vpsspeed.com/tag/speedcp homepage] Developed by an in-house team from VPSSpeed.com - Private licensing on request.
* SolusVM [http://www.solusvm.com homepage] In development - Initial release release scheduled for August 21st 2009. Released August 14th 1009.
* VZWave [http://www.vzwave.com homepage] In development - release expected July 09.
* DTC-Xen [http://www.gplhost.com/software-dtc-xen.html homepage] - Currently being ported to OpenVZ by its main developers.
* vpsAdmin [http://www.vpsadmin.org/ homepage] - In development - available from mercurial repository, GPLv3 license, stable release scheduled for October 1, 2009

Control panels

2009-09-17T14:43:16Z

Fayette: /* Frozen projects */ Marked vtonf as a dead project.

This page contains links to different control panels for OpenVZ, written by third parties. If you know the project that's missing here, please add it.

== Free software / Open source (in alphabetical order) ==
* fosvm (Free Open Source Virtual Machine manager): [http://fosvm.sourceforge.net/ homepage] | Uses php and bash scripts, monitors bandwidth, Version 0.02a. Last updated 2009-05-15.
* Proxmox Virtual Environment: [http://pve.proxmox.com Proxmox VE Wiki] - including bare-metal ISO installer
* [http://solukom.com/software/slkvm slkvm]: console scripts to handle vz virtualization in a two node cluster.
* unxsVZ OpenVZ Infrastructure Manager: [http://openisp.net/openisp/unxsVZ unxsVZ Trac Wiki] | Includes autonomic UBC adjusting and per container traffic graphs. Supports hot-spare clones and mount/umount conf file templates. Very active development. Last change to public svn code base June 20, 2009.
* Webmin: [http://www.webmin.com/ homepage] | [http://www.webmin.com/cgi-bin/search_third.cgi?search=OpenVZ OpenVZ plugin] | Version 1.0, last updated 2006-02-07
* WebVZ: [http://webvz.sourceforge.net/ homepage] Uses Ruby on Rails which makes it a poor choice for Debian, Ubuntu and other .deb style distros. In the comments section of http://www.howtoforge.com/install-webvz-2.0-on-debian-etch-to-administrate-openvz there is a suggestion of how to get this one running under Ubuntu Hardy. The authors like it.

== Proprietary / non-free ==
* Panenthe: [http://www.panenthe.com/ homepage (English)] • [http://www.panenthe.com/products/panenthe-media/cat_id=4/ Screen shots]
* vePortal: [http://www.veportal.com/ homepage (English)] • [http://www.veportal.com/index.php?cmd=screenshots Screen shots]
* FluidVM: [http://www.fluidvm.com Home Page]
* VZ-Manager: [http://vzmanager.de/ homepage (German)]
* vzAdmin: [http://www.vzAdmin.info/ homepage (German)]
* Aventurin{e}: [http://www.aventurin.net/ homepage (English)]
* SolusVM [http://www.solusvm.com homepage]
*vcPanel :[http://vcpanel.net Home Page], The first centralized VPS control panel for managing VPS around the globe [http://vcpanel.net/Demo Demo]

== Frozen projects ==
* VZAdmin: [http://www.ronny-goerner.de/ homepage] ''seems not available now''
* WVZ: [http://homaly.dunanet.hu/wvz/ homepage] ''seems frozen''
* New OpenVZ Web Based Control Panel by rsailor: {{forum|230}} ''seems not available now''
* EasyVZ: [http://easyvz.sourceforge.net/ screenshots] | [http://sourceforge.net/projects/easyvz sf.net project page] (little bit outdated, but working and free. Last update Feb 2007) (requires Unix/Linux)
* Mwamko: [http://mwamko.devjavu.com/ homepage] Last activity May 2007
* RoboVZ: [http://sharesource.org/project/robovz homepage] {{forum|2559}} Lots of promises since announced in May 2007, nothing usable yet. Possibly GPL license. No activity in 2 years, calling it frozen.
* HyperVM: [http://lxlabs.com/software/hypervm/ homepage] - No longer being developed after the sole developer sadly committed suicide in June 09.
* Vtonf: [http://www.vtonf.com/ homepage] | According to the documentation only runs on CentOS 4.5 or higher. Last change April 2008 - No longer supported. Does not work on CentOS 5+. Web page is no longer valid. Consider this one dead.
* WIVZ/GIVZ: [http://source.icenetx.net/ homepage] Release scheduled for October 2008 - never released. Unknown license.

== In development ==
* VS-Admin: [http://www.veportal.com/ homepage] Beta testers wanted (19-06-2009) - Project Changed to vePortal.
* speedCP [http://blog.vpsspeed.com/tag/speedcp homepage] Developed by an in-house team from VPSSpeed.com - Private licensing on request.
* SolusVM [http://www.solusvm.com homepage] In development - Initial release release scheduled for August 21st 2009.
* VZWave [http://www.vzwave.com homepage] In development - release expected July 09.
* DTC-Xen [http://www.gplhost.com/software-dtc-xen.html homepage] - Currently being ported to OpenVZ by its main developers.
* vpsAdmin [http://www.vpsadmin.org/ homepage] - In development - available from mercurial repository, GPLv3 license, stable release scheduled for October 1, 2009

OS template cache preparation

2009-04-07T23:22:05Z

Fayette: /* Alternative: use precreated template cache */

This article describes the procedure of an OS template cache creation. It assumes you already have OpenVZ installed and running. The steps needed to achieve it are documented in the [[Quick installation]] document.

== Terminology ==

Please make sure you understand the following terms.

{{:OS template}}
{{:OS template metadata}}
{{:OS template cache}}

== Creating an OS template cache ==
You can create an [[OS template cache]] using template utilities and [[OS template metadata]] right on your [[hardware node]]. The process is automated and will take from about 10 minutes to a few hours, depending on the network speed, and the result will be most up-to-date template cache.

=== Installing template utilities ===

You have to install a few packages in order to be able to create/update OS template cache(s).

==== Using yum ====
<pre>
# yum install vzpkg vzyum vzrpm43-python vzrpm44-python vzctl-lib
</pre>

==== Using rpm ====
Packages are available from [http://openvz.org/download/template/utils/ Download » Templates » Utilities]. You need both <tt>vzpkg</tt> and <tt>vzyum</tt> packages, as well as one or both <tt>vzrpm43</tt>/<tt>vzrpm44</tt> (including their <tt>-python</tt> counterparts), depending on the OS templates being used.

Install these utilities using rpm:

<pre>
# rpm -ihv vzpkg*.rpm vzyum*.rpm vzrpm44*.rpm
</pre>

In Red Hat Enterprise Linux, to install <tt>vzyum</tt> you will need <tt>[http://rpmfind.net/linux/rpm2html/search.php?query=python-elementtree&system=redhat python-elementtree]</tt>, <tt>[http://rpmfind.net/linux/rpm2html/search.php?query=python-sqlite&system=redhat python-sqlite]</tt>, and <tt>[http://rpmfind.net/linux/rpm2html/search.php?query=python-urlgrabber&system=redhat python-urlgrabber]</tt>. These packages might have dependencies of their own. For example, <tt>python-sqlite</tt> needs <tt>[http://rpmfind.net/linux/rpm2html/search.php?query=sqlite&system=redhat sqlite]</tt>.

=== Installing OS template metadata ===

To create an [[OS template cache]], you need to get the [[OS template metadata|metadata]] for the chosen OS template(s).

==== Using yum ====
To see which templates are available, run
<pre>
# yum search vztmpl
</pre>

To install some of the templates, run
<pre>
# yum install vztmpl-XXX [...]
</pre>

==== Using rpm ====
Get the chosen <tt>vztmpl-*</tt> packages from [http://openvz.org/download/template/metadata/ Downloads » Templates » Metadata] (or directly from [http://download.openvz.org/template/metadata/ download.openvz.org/template/metadata] or one of the [[Download mirrors|mirrors]] and install them:

<pre>
# rpm -ihv vztmpl-*.rpm
</pre>

=== Running <tt>vzpkgcache</tt> ===

Run the <tt>vzpkgcache</tt> utility; see the vzpkgcache(8) man page for details. It will create or update the caches of all the templates for which the corresponding metadata exist.

# vzpkgcache centos-4-i386-minimal

== Alternative: use precreated template cache ==

As an alternative to creating a cache using template metadata, you can use precreated template cache taken from [http://openvz.org/download/template/cache Downloads » Templates » Precreated], or directly from [http://download.openvz.org/template/precreated/ download.openvz.org/template/precreated], or from one of the [[Download mirrors|mirrors]].

Precreated templates can be easily updated using the following algorithm:
# create temporary [[container]] based on template
# update [[container]] using OS-specific tools (yum, apt or similar)
# pack [[container]] as a new template
Examples of this procedure are described in details at [[Updating Ubuntu template]], [[Updating Debian template]], [[Fedora template update]]

In order to use precreated template cache files, download files for chosen OS distributions and place them as-is (no unpacking needed) to the <tt>/vz/template/cache</tt> directory.

'''NOTE:''' On Ubuntu and probably recent Debian distros, the path is <tt>/var/lib/vz/template/cache</tt> if you installed OpenVZ from the repositories.

'''NOTE:''' If you use precreated CentOS-4 templates and wish to install software using vzyum, you will probably run into error like this:

[root@localhost tmp]# vzyum CTID install mypackage
[root@localhost tmp]# ERROR: No such OS template: install

This might apply to Fedora also. To fix this problem, install the appropriate [[OS template metadata]] on the OpenVZ host, for example

yum install vztmpl-centos-4

[Unverified note] : After creating a new OSTemplate cache called "centos4-i386-[ASINGLEWORD].tar.gz from a Container (on which vzyum worked) based on centos4-i386-default.tar.gz, vzyum failed to work (showing "No such OS template: install").

Here is the "solution" I worked out :
The new OSTemplate should be named "centos4-i386-[ASINGLEWORD].tar.gz", and in /vz/template/centos/4/i386/config you should copy the default.list to [ASINGLEWORD].list. vzyum then works (for me!). I have tried to verify this by creating templates with [MULTIPLEWORDS], which fail, and by creating templates without a corresponding [ASINGLEWORLD].conf file, which also fail - indicating that using a single word seems to be important (no hyphens etc). Good luck.

== Next step ==

Follow on to the [[container creation]] article.

[[Category: Installation]]
[[Category: Templates]]

Ubuntu template

2009-04-07T11:12:31Z

Fayette: Warning that dapper isn't supported any longer. This page should be deleted or updated.

'''
== Warning. Dapper is no longer supported and the repositories are no longer available. Do not install the dapper template unless you have a copy of the repository. ==
'''

The ubuntu template is an OpenVZ [[OS template]] that allows you to run ubuntu dapper in your [[container]], as opposed to the normal Debian stable or Fedora.
''Please note, that this package is really minimal, you must even install your own language pack!''

==Why would I want to use ubuntu template?==
The ubuntu template includes more up-to-date software. For example, it allows you to install apache 2.0.55, php 5, mysql 5, apache mono and more. Also, if you are used to using ubuntu as a Linux distribution for your desktop, you would be more familiar with it, as they use the same exact packages and repositories. Also, you can just follow the [http://wiki.ubuntu.com Ubuntu wiki] easily to install your software, as ubuntu has really good documentation. In addition, ubuntu dapper LTS has a 5 year time period of support.

==How do I get it?==
You may download it from one of the following places:
* [http://download.openvz.org/contrib/template/precreated/ubuntu-6.06-i386-minimal.tar.gz download.openvz.org]
* One of the [[download mirrors]]

You must place this file in <tt>/vz/template/cache/</tt> directory on your [[hardware node]].

==How do I create a container that uses this template?==
All you have to do is simply create a normal container but specify ubuntu-6.06-i386-minimal as the template. For example:
<pre> vzctl create 1002 --ostemplate ubuntu-6.06-i386-minimal </pre>

''Please note that in order to get the correct network settings and more, you must copy the debian configuration file(debian.conf) to ubuntu.conf. This is because Openvz does not yet reconize that ubuntu is its own os, and falls back to another linux distribution. Usually this file is located in /etc/vz/dists but can very depending on your distribution. For CentOS/Fedora this will be located in /etc/sysconfig/vz-scripts/dists. See {{bug|190}}.''

==How do I set it up?==
You can either do those modifications on already existing container, or, if you want these changes to be incorporated into your template, create a temporary container, do these changes, stop the container and tar the result into the same template file.

Well, the first thing you *must* do is install a language pack. You can do this by typing in
<pre> apt-get install language-pack-en </pre>

<pre>
Bug alert: I (Shane Hathaway) got the following error when I tried to install language-pack-en.

debconf: apt-extracttemplates failed: Bad file descriptordpkg: dpkg - error: PATH is not set.

I patched the problem by typing "export PATH". Even though the path is set, for some
reason it is not exported by default. I also added "export PATH" to /etc/profile .
</pre>

Then you should create another user. To do this, just type in <pre> adduser bob </pre>
You will probably want to install some other basic utilities: <pre>apt-get install man traceroute wget</pre>
Then all you have to do is follow the ubuntu tutorials [https://wiki.ubuntu.com/ApacheMySQLPHP here].

==Packages already installed==
*Basic debootstrap system
*nano
*ssh/sshd
*quota

==How was this template created?==
This package was created using debootstrap, and using the ubuntu dapper repositories. There were some hacks that needed to be done to the enviorment to get it working correctly, mainly for networking. The system was bootstrapped on a real ubuntu dapper system with ovzkernel-2.6.8. I checked it with my own server and then my webhosts, and it works correctly.

==Network issues==
If the template seems to have no working network it most probably needs more time to bring up the interfaces. The issue is, that
<pre>
/etc/network/if-up.d/ntpdate
</pre>
wants to set the clock during network start and runs into a very long timeout. Since ntpdate is not needed at all inside a container this script can simply be deleted. And Magic - the container starts up as fast as I would expect it to and all network interfaces are up and running at once.

==Bugs==
Any problems with this template? Post either on the [[Talk: {{PAGENAME}}|discussion page]] or on the forums. Or post on my userpage [[User_talk:Dmb]].

== See also ==
* [[Debian template creation]] howto.

== External links ==
* [http://ubuntu.com/ Ubuntu web site]
* [http://wiki.ubuntu.com/ Ubuntu wiki]

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

Install yum

2009-04-06T23:48:56Z

Fayette: A little grammatical correction.

''This article is specific to CentOS, however the packages required for yum here are the same on other flavors''

The scripts shown below install all the packages upon which yum depends for a 386 distro (Need separate 64 bit instructions)

'''Please note''' - that the version numbers of the packages WILL change as later releases come out, it is up to you to ensure that the packages used are the latest. If you find a package in this script has become deprecated, please update this page with the latest package so others do not have to search for it as well.
== CentOS 4 i386 ==
<pre>
rpm -Uvh http://mirror.centos.org/centos-4/4/os/i386/CentOS/RPMS/gmp-4.1.4-3.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-4/4/os/i386/CentOS/RPMS/readline-4.3-13.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-4/4/os/i386/CentOS/RPMS/python-2.3.4-14.7.el4.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-4/4/os/i386/CentOS/RPMS/libxml2-2.6.16-12.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-4/4/os/i386/CentOS/RPMS/libxml2-python-2.6.16-12.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-4/4/os/i386/CentOS/RPMS/expat-1.95.7-4.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-4/4/os/i386/CentOS/RPMS/python-elementtree-1.2.6-5.el4.centos.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-4/4/os/i386/CentOS/RPMS/sqlite-3.3.6-2.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-4/4/os/i386/CentOS/RPMS/python-sqlite-1.1.7-1.2.1.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-4/4/os/i386/CentOS/RPMS/elfutils-libelf-0.97.1-5.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-4/4/os/i386/CentOS/RPMS/elfutils-0.97.1-5.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-4/4/os/i386/CentOS/RPMS/rpm-4.3.3-26_nonptl.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-4/4/os/i386/CentOS/RPMS/rpm-python-4.3.3-26_nonptl.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-4/4/os/i386/CentOS/RPMS/python-urlgrabber-2.9.8-2.noarch.rpm
rpm -Uvh ftp://ftp.pbone.net/mirror/ftp.centos.org/4.6/os/alpha/CentOS/RPMS/centos-yumconf-4-4.5.noarch.rpm
rpm -Uvh http://mirror.centos.org/centos-4/4/os/i386/CentOS/RPMS/yum-metadata-parser-1.0-8.el4.centos.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-4/4/os/i386/CentOS/RPMS/yum-2.4.3-4.el4.centos.noarch.rpm
yum -y update
</pre>

Note: CentOS 4 i386 updated 10 November 2008

== CentOS 4 X86_64 ==
<pre>
rpm -Uvh http://mirror.centos.org/centos/4/os/x86_64/CentOS/RPMS/gmp-4.1.4-3.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/4/os/x86_64/CentOS/RPMS/readline-4.3-13.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/4/os/x86_64/CentOS/RPMS/python-2.3.4-14.7.el4.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/4/os/x86_64/CentOS/RPMS/libxml2-2.6.16-12.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/4/os/x86_64/CentOS/RPMS/libxml2-python-2.6.16-12.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/4/os/x86_64/CentOS/RPMS/expat-1.95.7-4.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/4/os/x86_64/CentOS/RPMS/python-elementtree-1.2.6-5.el4.centos.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/4/os/x86_64/CentOS/RPMS/sqlite-3.3.6-2.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/4/os/x86_64/CentOS/RPMS/python-sqlite-1.1.7-1.2.1.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/4/os/x86_64/CentOS/RPMS/elfutils-libelf-0.97.1-5.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/4/os/x86_64/CentOS/RPMS/elfutils-0.97.1-5.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/4/os/x86_64/CentOS/RPMS/rpm-4.3.3-26_nonptl.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/4/os/x86_64/CentOS/RPMS/rpm-python-4.3.3-26_nonptl.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/4/os/x86_64/CentOS/RPMS/python-urlgrabber-2.9.8-2.noarch.rpm
rpm -Uvh ftp://ftp.pbone.net/mirror/ftp.centos.org/4.6/os/alpha/CentOS/RPMS/centos-yumconf-4-4.5.noarch.rpm
rpm -Uvh http://mirror.centos.org/centos/4/os/x86_64/CentOS/RPMS/yum-metadata-parser-1.0-8.el4.centos.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/4/os/x86_64/CentOS/RPMS/yum-2.4.3-4.el4.centos.noarch.rpm
yum -y update
</pre>

Note: CentOS 4 X86_64 updated 15 December 2008

== CentOS 5 i386 ==
<pre>
rpm -Uvh http://mirror.centos.org/centos-5/5/os/i386/CentOS/elfutils-libs-0.125-3.el5.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-5/5/os/i386/CentOS/gmp-4.1.4-10.el5.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-5/5/os/i386/CentOS/readline-5.1-1.1.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-5/5/os/i386/CentOS/python-2.4.3-21.el5.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-5/5/os/i386/CentOS/python-iniparse-0.2.3-4.el5.noarch.rpm
rpm -Uvh http://mirror.centos.org/centos-5/5/os/i386/CentOS/libxml2-2.6.26-2.1.2.1.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-5/5/os/i386/CentOS/libxml2-python-2.6.26-2.1.2.1.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-5/5/os/i386/CentOS/expat-1.95.8-8.2.1.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-5/5/os/i386/CentOS/python-elementtree-1.2.6-5.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-5/5/os/i386/CentOS/sqlite-3.3.6-2.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-5/5/os/i386/CentOS/python-sqlite-1.1.7-1.2.1.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-5/5/os/i386/CentOS/elfutils-0.125-3.el5.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-5/5/os/i386/CentOS/rpm-python-4.4.2-48.el5.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-5/5/os/i386/CentOS/m2crypto-0.16-6.el5.2.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-5/5/os/i386/CentOS/python-urlgrabber-3.1.0-2.noarch.rpm
rpm -Uvh http://mirror.centos.org/centos-5/5/os/i386/CentOS/yum-metadata-parser-1.1.2-2.el5.i386.rpm
rpm -Uvh http://mirror.centos.org/centos-5/5/os/i386/CentOS/yum-3.2.8-9.el5.centos.1.noarch.rpm
yum -y update
</pre>
Note: Updated 8 July 2008

== CentOS 5 x86_64 ==
<pre>
rpm -Uvh http://mirror.centos.org/centos/5/os/x86_64/CentOS/gmp-4.1.4-10.el5.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/5/os/x86_64/CentOS/readline-5.1-1.1.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/5/os/x86_64/CentOS/python-2.4.3-21.el5.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/5/os/x86_64/CentOS/libxml2-2.6.26-2.1.2.1.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/5/os/x86_64/CentOS/libxml2-python-2.6.26-2.1.2.1.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/5/os/x86_64/CentOS/expat-1.95.8-8.2.1.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/5/os/x86_64/CentOS/python-elementtree-1.2.6-5.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/5/os/x86_64/CentOS/sqlite-3.3.6-2.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/5/os/x86_64/CentOS/python-sqlite-1.1.7-1.2.1.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/5/os/x86_64/CentOS/elfutils-libelf-0.125-3.el5.x86_64.rpm
rpm --nodeps -Uvh http://mirror.centos.org/centos/5/os/x86_64/CentOS/elfutils-0.125-3.el5.x86_64.rpm
rpm --nodeps -Uvh http://mirror.centos.org/centos/5/os/x86_64/CentOS/rpm-4.4.2-48.el5.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/5/os/x86_64/CentOS/rpm-python-4.4.2-48.el5.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/5/os/x86_64/CentOS/m2crypto-0.16-6.el5.2.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/5/os/x86_64/CentOS/python-urlgrabber-3.1.0-2.noarch.rpm
rpm -Uvh http://mirror.centos.org/centos/5/os/x86_64/CentOS/yum-metadata-parser-1.1.2-2.el5.x86_64.rpm
rpm -Uvh http://mirror.centos.org/centos/5/os/x86_64/CentOS/python-iniparse-0.2.3-4.el5.noarch.rpm
rpm -Uvh http://mirror.centos.org/centos/5/os/x86_64/CentOS/yum-3.2.8-9.el5.centos.1.noarch.rpm
yum -y update
</pre>
Note: Updated 28 Feb 2009

[[Category:HOWTO]]

Control panels

2009-04-06T23:36:38Z

Fayette:

This page contains links to different control panels for OpenVZ, written by third parties. If you know the project that's missing here, please add it.

== Free software / Open source (in alphabetical order) ==
* Proxmox Virtual Environment: [http://pve.proxmox.com Proxmox VE Wiki] - including bare-metal ISO installer
* Vtonf: [http://www.vtonf.com/ homepage] | According to the documentation only runs on Centos 4.5 or higher. Marked as beta, but works quite well. Last change April 2008
* Webmin: [http://www.webmin.com/ homepage] | [http://www.webmin.com/cgi-bin/search_third.cgi?search=OpenVZ OpenVZ plugin] | Version 1.0, last updated 2006-02-07
* WebVZ: [http://webvz.sourceforge.net/ homepage] Uses Ruby on Rails which makes it a poor choice for Debian, Ubuntu and other .deb style distros. In the comments section of http://www.howtoforge.com/install-webvz-2.0-on-debian-etch-to-administrate-openvz there is a suggestion of how to get this one running under Ubuntu Hardy. The authors like it.

== Proprietary / non-free ==
* FluidVM: [http://www.binarykarma.com Home Page] • [http://www.binarykarma.com/demo.php Demo Videos] • [http://www.binarykarma.com/fluidvm_screenshots.php Screen shots]
* VZ-Manager: [http://vzmanager.de/ homepage (German)]
* HyperVM: [http://lxlabs.com/software/hypervm/ homepage]
* vzAdmin: [http://www.vzAdmin.info/ homepage (German)]
* Aventurin{e}: [http://www.aventurin.net/ homepage (English)]

== Frozen projects ==
* VZAdmin: [http://www.ronny-goerner.de/ homepage] ''seems not available now''
* WVZ: [http://homaly.dunanet.hu/wvz/ homepage] ''seems frozen''
* New OpenVZ Web Based Control Panel by rsailor: {{forum|230}} ''seems not available now''
* EasyVZ: [http://easyvz.sourceforge.net/ screenshots] | [http://sourceforge.net/projects/easyvz sf.net project page] (little bit outdated, but working and free. Last update Feb 2007) (requires Unix/Linux)
* Mwamko: [http://mwamko.devjavu.com/ homepage] Last activity May 2007
* RoboVZ: [http://sharesource.org/project/robovz homepage] {{forum|2559}} Lots of promises since announced in May 2007, nothing usable yet. Possibly GPL license. No activity in 2 years, calling it frozen.

== In development ==
* WIVZ/GIVZ: [http://source.icenetx.net/ homepage] Release scheduled for October 2008. Unknow license. Link is currently broken as of 6 April 2009. It's probably defunct.

Control panels

2009-04-06T23:34:15Z

Fayette: /* In development */

This page contains links to different control panels for OpenVZ, written by third parties. If you know the project that's missing here, please add it.

== Free software / Open source (in alphabetical order) ==
* Proxmox Virtual Environment: [http://pve.proxmox.com Proxmox VE Wiki] - including bare-metal ISO installer
* Vtonf: [http://www.vtonf.com/ homepage] | According to the documentation only runs on Centos 4.5 or higher. Marked as beta, but works quite well. Last change April 2008
* Webmin: [http://www.webmin.com/ homepage] | [http://www.webmin.com/cgi-bin/search_third.cgi?search=OpenVZ OpenVZ plugin] | Version 1.0, last updated 2006-02-07
* WebVZ: [http://webvz.sourceforge.net/ homepage] Uses Ruby on Rails which makes it a poor choice for Debian, Ubuntu and other .deb style distros. In the comments section of http://www.howtoforge.com/install-webvz-2.0-on-debian-etch-to-administrate-openvz there is a suggestion of how to get this one running under Ubuntu Hardy. The authors like it.

== Proprietary / non-free ==
* FluidVM: [http://www.binarykarma.com Home Page] • [http://www.binarykarma.com/demo.php Demo Videos] • [http://www.binarykarma.com/fluidvm_screenshots.php Screen shots]
* VZ-Manager: [http://vzmanager.de/ homepage (German)]
* HyperVM: [http://lxlabs.com/software/hypervm/ homepage]
* vzAdmin: [http://www.vzAdmin.info/ homepage (German)]
* Aventurin{e}: [http://www.aventurin.net/ homepage (English)]

== Frozen projects ==
* VZAdmin: [http://www.ronny-goerner.de/ homepage] ''seems not available now''
* WVZ: [http://homaly.dunanet.hu/wvz/ homepage] ''seems frozen''
* New OpenVZ Web Based Control Panel by rsailor: {{forum|230}} ''seems not available now''
* EasyVZ: [http://easyvz.sourceforge.net/ screenshots] | [http://sourceforge.net/projects/easyvz sf.net project page] (little bit outdated, but working and free. Last update Feb 2007) (requires Unix/Linux)
* Mwamko: [http://mwamko.devjavu.com/ homepage] Last activity May 2007

== In development ==
* WIVZ/GIVZ: [http://source.icenetx.net/ homepage] Release scheduled for October 2008. Unknow license. Link is currently broken as of 6 April 2009
* RoboVZ: [http://sharesource.org/project/robovz homepage] {{forum|2559}} Lots of promises since announced in May 2007, nothing usable yet. Possibly GPL license.

Control panels

2009-04-06T23:32:14Z

Fayette: /* Frozen projects */

This page contains links to different control panels for OpenVZ, written by third parties. If you know the project that's missing here, please add it.

== Free software / Open source (in alphabetical order) ==
* Proxmox Virtual Environment: [http://pve.proxmox.com Proxmox VE Wiki] - including bare-metal ISO installer
* Vtonf: [http://www.vtonf.com/ homepage] | According to the documentation only runs on Centos 4.5 or higher. Marked as beta, but works quite well. Last change April 2008
* Webmin: [http://www.webmin.com/ homepage] | [http://www.webmin.com/cgi-bin/search_third.cgi?search=OpenVZ OpenVZ plugin] | Version 1.0, last updated 2006-02-07
* WebVZ: [http://webvz.sourceforge.net/ homepage] Uses Ruby on Rails which makes it a poor choice for Debian, Ubuntu and other .deb style distros. In the comments section of http://www.howtoforge.com/install-webvz-2.0-on-debian-etch-to-administrate-openvz there is a suggestion of how to get this one running under Ubuntu Hardy. The authors like it.

== Proprietary / non-free ==
* FluidVM: [http://www.binarykarma.com Home Page] • [http://www.binarykarma.com/demo.php Demo Videos] • [http://www.binarykarma.com/fluidvm_screenshots.php Screen shots]
* VZ-Manager: [http://vzmanager.de/ homepage (German)]
* HyperVM: [http://lxlabs.com/software/hypervm/ homepage]
* vzAdmin: [http://www.vzAdmin.info/ homepage (German)]
* Aventurin{e}: [http://www.aventurin.net/ homepage (English)]

== Frozen projects ==
* VZAdmin: [http://www.ronny-goerner.de/ homepage] ''seems not available now''
* WVZ: [http://homaly.dunanet.hu/wvz/ homepage] ''seems frozen''
* New OpenVZ Web Based Control Panel by rsailor: {{forum|230}} ''seems not available now''
* EasyVZ: [http://easyvz.sourceforge.net/ screenshots] | [http://sourceforge.net/projects/easyvz sf.net project page] (little bit outdated, but working and free. Last update Feb 2007) (requires Unix/Linux)
* Mwamko: [http://mwamko.devjavu.com/ homepage] Last activity May 2007

== In development ==
* WIVZ/GIVZ: [http://source.icenetx.net/ homepage] Release scheduled for October 2008. Unknow license.
* RoboVZ: [http://sharesource.org/project/robovz homepage] {{forum|2559}} Lots of promises since announced in May 2007, nothing usable yet. Possibly GPL license.

Control panels

2009-04-06T23:30:12Z

Fayette: /* Frozen projects */ Removed a frozen project whose link is broken.

This page contains links to different control panels for OpenVZ, written by third parties. If you know the project that's missing here, please add it.

== Free software / Open source (in alphabetical order) ==
* Proxmox Virtual Environment: [http://pve.proxmox.com Proxmox VE Wiki] - including bare-metal ISO installer
* Vtonf: [http://www.vtonf.com/ homepage] | According to the documentation only runs on Centos 4.5 or higher. Marked as beta, but works quite well. Last change April 2008
* Webmin: [http://www.webmin.com/ homepage] | [http://www.webmin.com/cgi-bin/search_third.cgi?search=OpenVZ OpenVZ plugin] | Version 1.0, last updated 2006-02-07
* WebVZ: [http://webvz.sourceforge.net/ homepage] Uses Ruby on Rails which makes it a poor choice for Debian, Ubuntu and other .deb style distros. In the comments section of http://www.howtoforge.com/install-webvz-2.0-on-debian-etch-to-administrate-openvz there is a suggestion of how to get this one running under Ubuntu Hardy. The authors like it.

== Proprietary / non-free ==
* FluidVM: [http://www.binarykarma.com Home Page] • [http://www.binarykarma.com/demo.php Demo Videos] • [http://www.binarykarma.com/fluidvm_screenshots.php Screen shots]
* VZ-Manager: [http://vzmanager.de/ homepage (German)]
* HyperVM: [http://lxlabs.com/software/hypervm/ homepage]
* vzAdmin: [http://www.vzAdmin.info/ homepage (German)]
* Aventurin{e}: [http://www.aventurin.net/ homepage (English)]

== Frozen projects ==
* VZAdmin: [http://www.ronny-goerner.de/ homepage] ''seems not available now''
* WVZ: [http://homaly.dunanet.hu/wvz/ homepage] ''seems frozen''
* New OpenVZ Web Based Control Panel by rsailor: {{forum|230}} ''seems not available now''
* EasyVZ: [http://easyvz.sourceforge.net/ screenshots] | [http://sourceforge.net/projects/easyvz sf.net project page] (little bit outdated, but working and free. Last update Feb 2007) (requires Unix/Linux)
* Mwamko: [http://mwamko.devjavu.com/ homepage]

== In development ==
* WIVZ/GIVZ: [http://source.icenetx.net/ homepage] Release scheduled for October 2008. Unknow license.
* RoboVZ: [http://sharesource.org/project/robovz homepage] {{forum|2559}} Lots of promises since announced in May 2007, nothing usable yet. Possibly GPL license.

Control panels

2009-04-06T23:28:45Z

Fayette: /* Frozen projects */

This page contains links to different control panels for OpenVZ, written by third parties. If you know the project that's missing here, please add it.

== Free software / Open source (in alphabetical order) ==
* Proxmox Virtual Environment: [http://pve.proxmox.com Proxmox VE Wiki] - including bare-metal ISO installer
* Vtonf: [http://www.vtonf.com/ homepage] | According to the documentation only runs on Centos 4.5 or higher. Marked as beta, but works quite well. Last change April 2008
* Webmin: [http://www.webmin.com/ homepage] | [http://www.webmin.com/cgi-bin/search_third.cgi?search=OpenVZ OpenVZ plugin] | Version 1.0, last updated 2006-02-07
* WebVZ: [http://webvz.sourceforge.net/ homepage] Uses Ruby on Rails which makes it a poor choice for Debian, Ubuntu and other .deb style distros. In the comments section of http://www.howtoforge.com/install-webvz-2.0-on-debian-etch-to-administrate-openvz there is a suggestion of how to get this one running under Ubuntu Hardy. The authors like it.

== Proprietary / non-free ==
* FluidVM: [http://www.binarykarma.com Home Page] • [http://www.binarykarma.com/demo.php Demo Videos] • [http://www.binarykarma.com/fluidvm_screenshots.php Screen shots]
* VZ-Manager: [http://vzmanager.de/ homepage (German)]
* HyperVM: [http://lxlabs.com/software/hypervm/ homepage]
* vzAdmin: [http://www.vzAdmin.info/ homepage (German)]
* Aventurin{e}: [http://www.aventurin.net/ homepage (English)]

== Frozen projects ==
* VZAdmin: [http://www.ronny-goerner.de/ homepage] ''seems not available now''
* WVZ: [http://homaly.dunanet.hu/wvz/ homepage] ''seems frozen''
* New OpenVZ Web Based Control Panel by rsailor: {{forum|230}} ''seems not available now''
* EasyVZ: [http://easyvz.sourceforge.net/ screenshots] | [http://sourceforge.net/projects/easyvz sf.net project page] (little bit outdated, but working and free. Last update Feb 2007) (requires Unix/Linux)
* Mwamko: [http://mwamko.devjavu.com/ homepage]
* OpenVZ Control panel for Windows(r): {{forum|1491}} | [http://downloads.qmailrocks.ru/vz/ downloads] ''unknown license''

== In development ==
* WIVZ/GIVZ: [http://source.icenetx.net/ homepage] Release scheduled for October 2008. Unknow license.
* RoboVZ: [http://sharesource.org/project/robovz homepage] {{forum|2559}} Lots of promises since announced in May 2007, nothing usable yet. Possibly GPL license.

Control panels

2009-04-06T23:23:34Z

Fayette: /* Free software / Open source (in alphabetical order) */

This page contains links to different control panels for OpenVZ, written by third parties. If you know the project that's missing here, please add it.

== Free software / Open source (in alphabetical order) ==
* Proxmox Virtual Environment: [http://pve.proxmox.com Proxmox VE Wiki] - including bare-metal ISO installer
* Vtonf: [http://www.vtonf.com/ homepage] | According to the documentation only runs on Centos 4.5 or higher. Marked as beta, but works quite well. Last change April 2008
* Webmin: [http://www.webmin.com/ homepage] | [http://www.webmin.com/cgi-bin/search_third.cgi?search=OpenVZ OpenVZ plugin] | Version 1.0, last updated 2006-02-07
* WebVZ: [http://webvz.sourceforge.net/ homepage] Uses Ruby on Rails which makes it a poor choice for Debian, Ubuntu and other .deb style distros. In the comments section of http://www.howtoforge.com/install-webvz-2.0-on-debian-etch-to-administrate-openvz there is a suggestion of how to get this one running under Ubuntu Hardy. The authors like it.

== Proprietary / non-free ==
* FluidVM: [http://www.binarykarma.com Home Page] • [http://www.binarykarma.com/demo.php Demo Videos] • [http://www.binarykarma.com/fluidvm_screenshots.php Screen shots]
* VZ-Manager: [http://vzmanager.de/ homepage (German)]
* HyperVM: [http://lxlabs.com/software/hypervm/ homepage]
* vzAdmin: [http://www.vzAdmin.info/ homepage (German)]
* Aventurin{e}: [http://www.aventurin.net/ homepage (English)]

== Frozen projects ==
* VZAdmin: [http://www.ronny-goerner.de/ homepage] ''seems not available now''
* WVZ: [http://homaly.dunanet.hu/wvz/ homepage] ''seems frozen''
* New OpenVZ Web Based Control Panel by rsailor: {{forum|230}} ''seems not available now''
* EasyVZ: [http://easyvz.sourceforge.net/ screenshots] | [http://sourceforge.net/projects/easyvz sf.net project page] (little bit outdated, but only working and free control panel?) (requires Unix/Linux)
* Mwamko: [http://mwamko.devjavu.com/ homepage]
* OpenVZ Control panel for Windows(r): {{forum|1491}} | [http://downloads.qmailrocks.ru/vz/ downloads] ''unknown license''

== In development ==
* WIVZ/GIVZ: [http://source.icenetx.net/ homepage] Release scheduled for October 2008. Unknow license.
* RoboVZ: [http://sharesource.org/project/robovz homepage] {{forum|2559}} Lots of promises since announced in May 2007, nothing usable yet. Possibly GPL license.

Control panels

2009-04-06T23:18:04Z

Fayette: /* Free software / Open source (in alphabetical order) */

This page contains links to different control panels for OpenVZ, written by third parties. If you know the project that's missing here, please add it.

== Free software / Open source (in alphabetical order) ==
* Proxmox Virtual Environment: [http://pve.proxmox.com Proxmox VE Wiki] - including bare-metal ISO installer
* Vtonf: [http://www.vtonf.com/ homepage] | According to the documentation only runs on Centos 4.5 or higher. Marked as beta, but works quite well. Last change April 2008
* Webmin: [http://www.webmin.com/ homepage] | [http://www.webmin.com/cgi-bin/search_third.cgi?search=OpenVZ OpenVZ plugin] | Version 1.0, last updated 2006-02-07
* WebVZ: [http://webvz.sourceforge.net/ homepage] Uses Ruby on Rails which makes it a poor choice for Debian, Ubuntu and other .deb style distros.

== Proprietary / non-free ==
* FluidVM: [http://www.binarykarma.com Home Page] • [http://www.binarykarma.com/demo.php Demo Videos] • [http://www.binarykarma.com/fluidvm_screenshots.php Screen shots]
* VZ-Manager: [http://vzmanager.de/ homepage (German)]
* HyperVM: [http://lxlabs.com/software/hypervm/ homepage]
* vzAdmin: [http://www.vzAdmin.info/ homepage (German)]
* Aventurin{e}: [http://www.aventurin.net/ homepage (English)]

== Frozen projects ==
* VZAdmin: [http://www.ronny-goerner.de/ homepage] ''seems not available now''
* WVZ: [http://homaly.dunanet.hu/wvz/ homepage] ''seems frozen''
* New OpenVZ Web Based Control Panel by rsailor: {{forum|230}} ''seems not available now''
* EasyVZ: [http://easyvz.sourceforge.net/ screenshots] | [http://sourceforge.net/projects/easyvz sf.net project page] (little bit outdated, but only working and free control panel?) (requires Unix/Linux)
* Mwamko: [http://mwamko.devjavu.com/ homepage]
* OpenVZ Control panel for Windows(r): {{forum|1491}} | [http://downloads.qmailrocks.ru/vz/ downloads] ''unknown license''

== In development ==
* WIVZ/GIVZ: [http://source.icenetx.net/ homepage] Release scheduled for October 2008. Unknow license.
* RoboVZ: [http://sharesource.org/project/robovz homepage] {{forum|2559}} Lots of promises since announced in May 2007, nothing usable yet. Possibly GPL license.

FUSE

2009-01-04T11:12:46Z

Fayette: /* Mounting filesystem I attempted to defeat the linkification, but it doesn't work*/

This page describes how to setup FUSE (filesystem in userspace) inside a container.

[http://git.openvz.org/?p=linux-2.6.18-openvz;a=blob;h=a584f05403a412e778cf359e84d3690d5a22d1e4;hb=045f4a5fcb8c2625fe7505a8d9d4ebffd7e0d905;f=Documentation/filesystems/fuse.txt FUSE] is a filesystem in which data and metadata are provided by an ordinary userspace process. The filesystem can be accessed normally through the kernel interface.

== Preparations ==
To use FUSE you need the following:
# OpenVZ kernel version [http://git.openvz.org/?p=linux-2.6.18-openvz;a=commit;h=045f4a5fcb8c2625fe7505a8d9d4ebffd7e0d905 028test005] or higher
# [http://mesh.dl.sourceforge.net/sourceforge/fuse/fuse-2.6.0.tar.gz Fuse lib]
# Any FUSE-based [http://fuse.sourceforge.net/wiki/index.php/FileSystems filesystem]

In the examples below [http://fuse.sourceforge.net/sshfs.html sshfs] is used.

== Setup ==
=== Kernel ===
Download appropriate kernel from [http://download.openvz.org/ openvz.org] or compile kernel with <code>CONFIG_FUSE_FS</code> option set

=== Userspace ===

You have to fuse libraries and some fuse filesystem modules (here we use sshfs as an example).

The best way to have it installed is to use the packages from your distro vendor. An alternative is compiling the stuff from source.

==== Gentoo ====

# emerge sys-fs/sshfs-fuse

==== Fedora ====

# yum install fuse-sshfs

==== Debian/Ubuntu ====

# apt-get install sshfs

==== Compiling from source ====
If there are no packages provided for you distribution, you have to compile from source.

First, compile libfuse in a container without kernel module
<pre>
# vzctl enter 100
# tar xzf fuse-2.6.0.tar.gz
# cd fuse-2.6.0
# ./configure --disable-kernel-module
...
# make
...
# make install
</pre>

{{note|Sometimes <code>libfuse.so.X</code> is unseen by your programs. Usually this file is installed in <code>/usr/local/lib</code> directory so don't forget to add this directory into your <code>/etc/ld.so.conf</code> and then run <code>ldconfig</code>.}}

Next, download and compile filesystem.
<pre>
# vzctl enter 100
# tar xzf sshfs-fuse-1.7.tar.gz
# cd sshfs-fuse-1.7
# ./configure
...
# make
...
# make install
</pre>

=== Container tuning ===
You need to make a character device named <code>/dev/fuse</code> and grant your container permissions to it
<pre>
# vzctl set 100 --devices c:10:229:rw --save
...
# vzctl exec 100 mknod /dev/fuse c 10 229
...
</pre>

=== Mounting filesystem ===
After this you may try to mount FUSE in a container.
<pre>
# vzctl enter 100
# sshfs <nowiki>root@foo.org</nowiki>:/root /mnt/foo.org.root
</pre>

==== Unmounting filesystem ====
In case of <code>sshfs</code> after umounting an appropriate daemon must be killed. This may be done by the following command:
<pre>
# fusermount -u moutpoint
</pre>

== Using fusectl filesystem ==
Fusectl is a helper filesystem for FUSE. You may mount it in a container as well.
<pre>
# vzctl enter 100
# mount -t fusectl none /fuse_ctl
</pre>

== External links ==

* [http://fuse.sourceforge.net/ FUSE site]

[[Category:HOWTO]]

Talk:Installing Trixbox 2.0 in CentOS VE

2008-09-07T20:46:59Z

Fayette:

In attempting to follow these instructions I've found the following:

I am using the http://download.openvz.org/beta/templates/precreated/centos-5-x86.tar.gz template.

Between the "Add character device" and the "Install rpmforge & apt" steps you'll probably want to do
<pre>
vzctl enter <VEID>
</pre>

I found that for some reason rpm could not access the files so I had to do the following to install rpmforge:
<pre>
SITE="http://dag.wieers.com/packages/rpmforge-release/"
wget ${SITE}/rpmforge-release-0.3.6-1.el5.rf.i386.rpm
rpm -Uvh rpmforge-release-0.3.6-1.el5.rf.i386.rpm
</pre>

Install apt:
<pre>
SITE="http://dag.wieers.com/packages/apt/"
wget ${SITE}/apt-0.5.15lorg3.2-1.el5.rf.i386.rpm
rpm -ivh apt-0.5.15lorg3.2-1.el5.rf.i386.rpm
</pre>
Also note that I am using the el5 versions of these rpms.

Yum is available in the el5 template that I used so I didn't have to install it.

In the step, "Install speex and libspeex-devel" I found it easier to use yum.
<pre>
yum install speex speex-devel
</pre>

It appears that the folks that brought us Trixbox would rather us download and install an ISO. You have to dig pretty deep to find an RPM file. I finally found one:
<pre>
wget http://yum.trixbox.org/centos/5/RPMS-2.6.0.7/trixbox-2.6.0.0-3.i386.rpm
</pre>

I found that there were a great number of dependencies that were not found by yum. It appears that you must use a large number of the files at ftp://ftp.pbone.net/mirror/yum.trixbox.org/centos/5/RPMS/. I wrote a simple perl script to download all the files and built a yum repository containing them.

I used the following yum command to install:
<pre>
yum --nogpgcheck --enablerepo=trixbox localinstall trixbox-2.6.0.0-3.i386.rpm
</pre>

None of the trixbox references at the end of the article are still valid URLs.

Talk:Installing Trixbox 2.0 in CentOS VE

2008-09-06T13:32:05Z

Fayette:

Talk:Installing Trixbox 2.0 in CentOS VE

2008-09-06T13:26:32Z

Fayette:

Talk:Installing Trixbox 2.0 in CentOS VE

2008-09-06T13:14:32Z

Fayette: New page: In attempting to follow these instructions I've found the following: I am using the http://download.openvz.org/beta/templates/precreated/centos-5-x86.tar.gz template. Between the "Add ...

Using veth and brctl for protecting HN and saving IP addresses

2008-09-05T14:24:40Z

Fayette:

Configuration described below has been suggested by Ugo123. Thank you.

Consider we are facing the following task:

1) We have limited range of IP addresses granted by ISP.
We want to assign as many granted IPs to containers as possible.
We do not want to protect containers from Internet.
2) We want to protect the [[HN]] OS ([[CT]]0) from Internet and make it possible to manage containers from [[CT0]] within local area network.

Assume we have a [[HN]] with 2 Ethernet cards (interfaces eth0 and eth1), OpenVZ kernel 2.6.18-028stab033, vzctl version 3.0.16,
bridge-utils version 1.1. OpenVZ installation process is covered in [[quick installation]].

This task can be effectively performed by setting up the configuration presented in Figure 1.

Figure 1: Effective configuration. 10.0.98.96-10.0.98.X - range of IP addresses granted by ISP, 192.168.1.136 - IP address from LAN

[[Image:fig.jpg]]

Initial ifconfig output of HN is the following:
<pre>
[HN]# ifconfig
eth0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:34
inet addr:192.168.1.136 Bcast:192.168.3.255 Mask:255.255.252.0
inet6 addr: fe80::230:48ff:fe5b:ab34/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3122 errors:0 dropped:0 overruns:0 frame:0
TX packets:246 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:325879 (318.2 KiB) TX bytes:57278 (55.9 KiB)
Interrupt:20

eth1 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:35
inet addr:192.168.0.32 Bcast:192.168.3.255 Mask:255.255.252.0
inet6 addr: fe80::213:d4ff:fe90:4d50/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:603734 errors:0 dropped:0 overruns:0 frame:0
TX packets:36627 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:21

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1376 errors:0 dropped:0 overruns:0 frame:0
TX packets:1376 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2078718 (1.9 MiB) TX bytes:2078718 (1.9 MiB)
</pre>
Let us step through the setup process.

1) Create 2 containers on the HN as described in http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf.
For testing purposes I've used opensuse-10 precreated template from openvz.org:
<pre>
[HN]# cd /vz/template/cache
[HN]# wget http://download.openvz.org/template/precreated/opensuse-10-i386-default.tar.gz
</pre>
Create container 101 and assign it one of the IP addresses obtained from ISP:
<pre>
[HN]# vzctl create 101 --ostemplate opensuse-10-i386-default --ipadd 10.0.98.96
[HN]# vzctl set 101 --userpasswd root:XXX --save
</pre>
And do the same for CT 102 ... CT N. When ready - start containers:
<pre>
[HN]# vzctl start 101
[HN]# vzlist -a
CTID NPROC STATUS IP_ADDR HOSTNAME
101 4 running 10.0.98.96 -
102 4 running 10.0.98.97 -
</pre>
2) By default containers use venet device for networking (see [[venet]]). But current
configuration requires using alternative networking - through veth devices (see [[Virtual Ethernet device]]).
Switch CT 101 to veth by doing the following:

MAC address needed by eth0 of CT 101 and veth101.0 should be generated by easymac:
<pre>
[HN]# wget http://www.easyvmx.com/software/easymac.sh
[HN]# chmod 0777 easymac.sh
[HN]# ./easymac.sh -R
00:0C:29:70:BB:34
[HN]# ./easymac.sh -R
00:0C:29:C0:2E:07
</pre>
Replace venet by veth device on HN:
<pre>
[HN]# ifconfig venet0:0 down
[HN]# vzctl set 101 --netif_add eth0,00:0C:29:70:BB:34,veth101.0,00:0C:29:C0:2E:07 --save
[HN]# ifconfig veth101.0 0
[HN]# echo 0 > /proc/sys/net/ipv4/conf/veth101.0/forwarding
[HN]# echo 0 > /proc/sys/net/ipv4/conf/veth101.0/proxy_arp
</pre>
Enter the container and tune ifconfig within the container:
<pre>
[CT 101]# vzctl enter 101
[CT 101]# ifconfig venet0:0 down
[CT 101]# ifconfig venet0 down
[CT 101]# ifconfig eth0 0
[CT 101]# ip addr add 10.0.98.96 dev eth0
[CT 101]# ip route add default dev eth0
</pre>
The same (whole item 2) should be done for CT 102 ... CT N.
3) Now we should eliminate the IP address on eth1:

[HN]# vim /etc/sysconfig/network-scripts/ifcfg-eth1

Edit like this:
DEVICE=eth1
#BOOTPROTO=dhcp <<== comment out
HWADDR=XX:XX:XX:XX:XX:XX
ONBOOT=yes

and save changes (:wq).

[HN]# /etc/init.d/network restart

And turn off forwarding and proxy_arp for eth1.

[HN]# ifconfig eth1 0
[HN]# echo 0 > /proc/sys/net/ipv4/conf/eth1/forwarding
[HN]# echo 0 > /proc/sys/net/ipv4/conf/eth1/proxy_arp
</pre>
4) Create br0 bridge uniting eth1, veth101.0, ..., vethN.0:
<pre>
[HN]# brctl addbr br0
[HN]# brctl addif br0 eth1
[HN]# brctl addif br0 veth101.0
..., veth102.0, vethN.0 etc.
[HN]# ifconfig br0 0
</pre>
And turn off frowarding and proxy_arp for br0:
<pre>
[HN]# echo 0 > /proc/sys/net/ipv4/conf/br0/forwarding
[HN]# echo 0 > /proc/sys/net/ipv4/conf/br0/proxy_arp
</pre>
This is very important action. If skipped, network
can be broken on further steps due to incoming arp-requests provoked storm.

As a result of above listed actions the ifconfig output like the following should be listed:
<pre>
[HN]# ifconfig
br0 Link encap:Ethernet HWaddr 00:0C:29:A7:A9:D9
inet6 addr: fe80::20c:29ff:fea7:a9d9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:79 errors:0 dropped:0 overruns:0 frame:0
TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2972 (2.9 KiB) TX bytes:4390 (4.2 KiB)

eth0 Link encap:Ethernet HWaddr 00:30:48:5B:AB:34
inet addr:192.168.1.136 Bcast:192.168.3.255 Mask:255.255.252.0
inet6 addr: fe80::230:48ff:fe5b:ab34/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:347855 errors:0 dropped:0 overruns:0 frame:0
TX packets:4778 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:35964081 (34.2 MiB) TX bytes:698801 (682.4 KiB)
Interrupt:20

eth1 Link encap:Ethernet HWaddr 00:30:48:5B:AB:35
inet6 addr: fe80::230:48ff:fe5b:ab35/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:322 errors:0 dropped:0 overruns:0 frame:0
TX packets:182 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:41943 (40.9 KiB) TX bytes:21338 (20.8 KiB)
Interrupt:21

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1376 errors:0 dropped:0 overruns:0 frame:0
TX packets:1376 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2078718 (1.9 MiB) TX bytes:2078718 (1.9 MiB)

veth101.0 Link encap:Ethernet HWaddr 00:0C:29:C0:2E:07
inet6 addr: fe80::20c:29ff:fec0:2e07/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:363 errors:0 dropped:0 overruns:0 frame:0
TX packets:397 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:31134 (30.4 KiB) TX bytes:31440 (30.7 KiB)

veth102.0 Link encap:Ethernet HWaddr 00:0C:29:A7:A9:D9
inet6 addr: fe80::20c:29ff:fea7:a9d9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:36 errors:0 dropped:0 overruns:0 frame:0
TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1840 (1.7 KiB) TX bytes:2350 (2.2 KiB)
</pre>
5) That is all. It's time to test the obtained configuration.
Now plug eth1 of HN into network wall outlet provided by ISP and carry out the following testing:

- It should be tested that containers are accessible from Internet:
<pre>
[INET]# ssh root@10.0.98.96
[CT 101]# ...
</pre>
- HN is not accessible from Internet:
<pre>
[INET]# ssh root@192.168.1.136
inaccessible
</pre>
- containers can be managed from HN:
<pre>
[HN]# vzctl enter 101
[CT 101]# ...
</pre>
- containers CT 101, CT 102 .. CT N "see" each other (ping).

If all the steps are done as written, it should work.
Enjoy.

Download/template

2008-09-05T14:17:52Z

Fayette:

A '''template''' is an image of an OS (i.e. a Linux distribution) aimed for installation into a container. Template utilities are provided to assist in the creation of such images, but they are completely optional.

;[[Download/template/precreated|Precreated]]
:Precreated templates of different distributions.
;[[Download/template/utils|Utilities]]
:Template utilities are programs designed to assist with template maintenance, such as the creation and update of templates and containers. Currently these consists of [[Download/vzpkg|'''vzpkg''']], [[Download/vzyum|'''vzyum''']] and several versions of the RPM utility repackaged for OpenVZ. '''All this is optional and currently only supported on systems with x86 architecture and with python <= 2.4.'''
;[[Download/template/metadata|Metadata]]
: Template metadata is data needed to (re)create or update template cache using template utilities. Metadata for a template contains the following information: list of packages that form this template; locations of package repositories; scripts needed to be executed on various stages of template installation; public GPG key(s) needed to check signatures of packages; additional OpenVZ-specific packages.

== See also ==

* [[:Category:Templates]]

Download/template

2008-09-05T14:15:02Z

Fayette:

A '''template''' is an image of an OS (i.e. a Linux distribution) aimed for installation into a container. Template utilities are provided to assist in the creation of such images, but they are completely optional.

;[[Download/template/precreated|Precreated]]
:Precreated templates of different distributions.
;[[Download/template/utils|Utilities]]
:Template utilities is a software aimed at template maintenance, such as creation and update of templates and containers. Currently these consists of [[Download/vzpkg|'''vzpkg''']], [[Download/vzyum|'''vzyum''']] and several versions of RPM utility repackaged for OpenVZ. '''All this stuff is highly optional and currently only supported on systems with x86 architecture and with python <= 2.4.'''
;[[Download/template/metadata|Metadata]]
: Template metadata is data needed to (re)create or update template cache using template utilities. Metadata for a template contains the following information: list of packages that form this template; locations of package repositories; scripts needed to be executed on various stages of template installation; public GPG key(s) needed to check signatures of packages; additional OpenVZ-specific packages.

== See also ==

* [[:Category:Templates]]

Machine check exception

2008-09-05T14:11:45Z

Fayette:

'''Machine check exception''' is when you see something like this in your logs:
<pre>
Jul 9 12:19:41 vz01 kernel: CPU 0: Machine Check Exception: 0000000000000004
Jul 9 12:19:41 vz01 kernel: Bank 4: b604a00100000813 at 000000007e4f2f68
Jul 9 12:19:41 vz01 kernel: Kernel panic: CPU context corrupt
</pre>

== What does that mean? ==
Such messages are printed when the CPU detects hardware problems, e.g. memory corruptions or some other problems. It is 100% hardware problem with your server.

== What to do? ==
The best thing to do is check your server — see [[Hardware testing]].

== External links ==
* [http://en.wikipedia.org/wiki/Machine_Check_Exception wikipedia:Machine Check Exception]

[[Category: Troubleshooting]]
[[Category: FAQ]]

OS template metadata

2008-09-05T14:10:37Z

Fayette: /* Contributions */

'''OS template metadata''' is a set of a few files containing the following information:

* List of packages that form this [[OS template]]
* Locations of package repositories
* Scripts needed to be executed on various stages of template installation
* Public GPG key(s) needed to check signatures of packages
* Additional OpenVZ-specific packages

==Internals==
(Incomplete) Based off the centos-4 vztmpl:

*addons/vzdev is a static list of most commonly used /dev entries. Provides dev package. Uses MAKEDEV.spec
*addons/MAKEDEV-3.3.13-1.3.swsoft is generated from a copy of fedora core 2's MAKEDEV-3.3.13. Uses MAKEDEV.spec which is a customized version to install only the essential devices and depend on vzdev
*dummy-centos-4 is a placeholder for kernel, module-init-tools, modutils, mingetty, kernel-utils, ethtool, and kernel-drm packages. Uses dummy.spec
*default.list, minimal.list, *.list are list of packages for a flavor of the template. Must contain dummy-centos-4, vzdev, and MAKEDEV packages
*config/yum.conf.in template for yum.conf with tokens replaced during build.
*config/install-pre or install-post is executed by cache-os which is executed by vzpkgcache when creating a template cache
*config/update-pre or update-post is executed when updating a template cache
*config/gpgkeys are the keys for the packages to be cached
*config/rpm contains the rpm version
*vztmpl.spec.in is template for the vztmpl package
*make.defs is the common variables for the make process

Download the vztmpl-centos-4*.src.rpm. Install it. Modify it.

To generate the OS template metadata rpm run "make rpms" inside the /usr/src/redhat/SOURCES/centos-4 dir. You will need gcc, rpmbuild, and createrepo packages.

==Contributions==
* http://www.neonhost.com/openvz/ - Centos 5 rpm and patch for centos 4 template contributed by Chris Turan. See http://forum.openvz.org/index.php?t=msg&&th=5037

* Kir's beta templates - http://download.openvz.org/beta/templates/precreated/
Using OS template metadata and vzpkg tools, an OS template cache can be created.
<noinclude>

== See also ==
* [[OS template]]
* [[OS template cache]]
* [[OS template cache preparation]]

[[Category: Definitions]]
[[Category: Templates]]
</noinclude>

Resource shortage

2008-09-05T14:06:44Z

Fayette:

Sometimes you see strange failures from some programs inside your [[container]]. In some cases it means one of the resources controlled by OpenVZ has hit the limit.

The first thing to do is to check the contents of the /proc/user_beancounters file in your [[container]]. The last column of output is the fail counter. Each time a resource hits the limit, the fail counter is incremented. So, if you see non-zero values in the failcnt column that means something is wrong.

There are two ways to fix the situation: reconfigure (in some cases recompile) the application, or change the resource management settings.

== [[UBC]] parameters ==

Here is an example of current [[UBC]] values obtained from <code>/proc/user_beancounters</code> file in container 123:
<pre>
# cat /proc/user_beancounters
Version: 2.5
uid resource held maxheld barrier limit failcnt
123: kmemsize 836919 1005343 2752512 2936012 0
lockedpages 0 0 32 32 0
privvmpages 4587 7289 49152 53575 0
shmpages 39 39 8192 8192 0
dummy 0 0 0 0 0
numproc 20 26 65 65 0
physpages 2267 2399 0 2147483647 0
vmguarpages 0 0 6144 2147483647 0
oomguarpages 2267 2399 6144 2147483647 0
numtcpsock 3 3 80 80 0
numflock 3 4 100 110 0
numpty 1 1 16 16 0
numsiginfo 0 1 256 256 0
tcpsndbuf 0 0 319488 524288 0
tcprcvbuf 0 0 319488 524288 0
othersockbuf 6684 7888 132096 336896 0
dgramrcvbuf 0 8372 132096 132096 0
numothersock 8 10 80 80 0
dcachesize 87672 92168 1048576 1097728 0
numfile 238 306 2048 2048 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 10 16 128 128 0
</pre>

You can see if you hit the limit for some [[UBC]] parameters by analyzing the last column (named <code>failcnt</code>). It shows a number of failures for this counter, i.e. a number of times a parameter hit the limit. Usually what you need to do is to increase the parameter in question. But you need to do it carefully, and here is how.

<ol>
<li>Get the current values for the parameter's barrier and limit. For example, we want to increase kmemsize values. From <code>/proc/user_beancounters</code> we see that <code>kmemsize</code> barrier is 2752512, and its limit is 2936012.
</li>

<li>Increase the values. Say, we want to double <code>kmemsize</code>. This is how it can be done using built-in bash arithmetics:
<pre>
# vzctl set 123 --kmemsize $((2752512*2)):$((2936012*2)) --save
</pre>
By using the <code>--save</code> flag, we indicate we want to apply the new setting to the running container and save it in the configuration file (from which the settings will be taken during next container start).
</li>

<li>Check the new configuration. Issue the following command:
<pre>
# vzcfgvalidate /etc/vz/conf/123.conf
</pre>
If something is wrong, you need to fix it as suggested by the utility.
</li>
</ol>

For more in-depth explanation of different parameters, their meaning and how to set them properly, see [[setting UBC parameters]].

== Disk quota ==
To check if your [[container]] exceeded its disk quota, use the following commands (inside a container):
<pre>
# df
Filesystem 1K-blocks Used Available Use% Mounted on
simfs 1048576 327664 720912 32% /
# df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
simfs 200000 18857 181143 10% /
</pre>

The first command shows disk space usage and the second command shows the inodes usage (you can roughly use the inodes count as a number of files/directories on your system).

If one of the commands shows a usage of 100% you have exceeded one of the disk quota limits.

You can increase the limit from the host system ([[CT0]] [[aka]] [[VE0]]) only. This is how:
<ol>
<li>Get the current values for disk quota:
<pre># vzquota stat 123
resource usage softlimit hardlimit grace
1k-blocks 327664 1048576 1153434
inodes 18857 200000 220000
</pre>
</li>

<li>To increase the disk space quota, use vzctl set --diskspace. For example, we want to increase it by a factor of 2:
<pre>
vzctl set 123 --diskspace $(( 1048576*2 )):$(( 1153434*2 )) --save
</pre>
</li>

<li>To increase the disk inodes quota, use <tt>vzctl set --diskinodes</tt>. For example, we want to increase it by a factor of 3:
<pre>
vzctl set 123 --diskinodes $(( 200000*3 )):$(( 220000*3 )) --save
</pre>
</li>
</ol>

{{Note|shell does not support floating-point arithmetic, i.e. you can not use expressions like <code>$(( 220000*1.5 ))</code>. To use floating point, try <code>bc</code> instead, something like this: <code><nowiki>$(echo 220000*1.5 | bc)</nowiki></code>.}}

== CPU ==

There are two parameters controlling fair CPU scheduler in OpenVZ: cpuunits and cpulimit.

Cpuunits are set via
<pre>
vzctl set 101 --cpuunits 1000 --save
</pre>
For example. If you set a cpuunit for one container to a value and set a cpuunit on another container to a different value, the time allotted to each of the containers will be the ratio of the two units. Let's use a real example.

We did the following:
<pre>
vzctl set 101 --cpuunits 1000 --save
vzctl set 102 --cpuunits 2000 --save
vzctl set 103 --cpuunits 3000 --save
</pre>

If we started a cpu intensive application on each VE, then 103 would be given 3 times as much cpu time as 101 and 102 would get twice as much as 101, but some fraction of what 103 got. Here's how to determine what the real ratios are.

Add the three units, 1000+2000+3000 = 6000

101 gets 1000/6000 or 1/6th of the time. (16%)
102 gets 2000/6000 or 1/3rd of the time. (34%)
103 gets 3000/6000 or 1/2 of the time. (50%)

CPULIMIT

The cpulimit parameter sets the absolute maximum limit for a container to a percent value. For instance:
<pre>
vzctl set 101 --cpulimit 25 --save
</pre>
says that container 101 cannot ever have more than 25 percent of the cpu even if the cpu is idle for the other 75% of the time.

{{Stub}}

[[Category: Troubleshooting]]
[[Category: HOWTO]]
[[Category: UBC]]
[[Category: Resource management]]
[[Category: Disk quota]]

Fair-share scheduling

2008-09-05T13:36:41Z

Fayette: New page: Fair-share scheduling is a method of allotting CPU time to muliple processors in a defined way. When mulitple processes need a CPU, operating systems frequently allot CPU time slices on a...

Fair-share scheduling is a method of allotting CPU time to muliple processors in a defined way. When mulitple processes need a CPU, operating systems frequently allot CPU time slices on a round robin, equal time basis for processes with the same priority. An exmaple is that if there are 4 processes wanting the CPU then each process will get 1/4 of a second every second. This is not to say that each process will get 1/4 of a second all at one time. Most operating systems define a time slice, something like 50 msec (arbitrary number that doesn't necessarily represent any OS) and will give each process a time slice. So in this completely made up case, Each process will get 5 time slices every second.

Long ago someone said that we need a way of giving people with legitimate requirements more of the time than less needy people. "Need" often reflects what level of service the user wants to pay for. The fair-share scheduler was born. There have been a number of implementations over the years, but on of the most common was to simply assign weights to users such that one user may get twice as many time slices in a given time period as others. This has been expanded often to groups so that processes belonging to a group of users would be given the same number of time slices as another group.

For example if group A had 8 processes running and group B had 4, then each group would get half the time, meaning that each process in the A group would only get 6.25% of the time (8*6.5 = 50) and each process in group B would get 12.5% of the time.

There are a number of different implementations of the fair-share scheduler other than the ones described here. I know of one that actually kept track of the accumulated time over a time period for a user/group and would use that information in it's calculations. The theory was that if you'd been a cpu hog in the past, you might not get as much time right now. This calculation also was also time weighted such that your share of time in the last second was much more important than a second a few minutes ago.

Aka

2008-09-05T13:13:00Z

Fayette: New page: aka - also know as, an alias, meaning the same

aka - also know as, an alias, meaning the same

Resource shortage

2008-09-05T13:12:31Z

Fayette: /* Disk quota */

Sometimes you see strange failures from some programs inside your [[container]]. In some cases it means one of the resources controlled by OpenVZ has hit the limit.

The first thing to do is to check the contents of the /proc/user_beancounters file in your [[container]]. The last column of output is the fail counter. Each time a resource hits the limit, the fail counter is incremented. So, if you see non-zero values in the failcnt column that means something is wrong.

There are two ways to fix the situation: reconfigure (in some cases recompile) the application, or change the resource management settings.

== [[UBC]] parameters ==

Here is an example of current [[UBC]] values obtained from <code>/proc/user_beancounters</code> file in container 123:
<pre>
# cat /proc/user_beancounters
Version: 2.5
uid resource held maxheld barrier limit failcnt
123: kmemsize 836919 1005343 2752512 2936012 0
lockedpages 0 0 32 32 0
privvmpages 4587 7289 49152 53575 0
shmpages 39 39 8192 8192 0
dummy 0 0 0 0 0
numproc 20 26 65 65 0
physpages 2267 2399 0 2147483647 0
vmguarpages 0 0 6144 2147483647 0
oomguarpages 2267 2399 6144 2147483647 0
numtcpsock 3 3 80 80 0
numflock 3 4 100 110 0
numpty 1 1 16 16 0
numsiginfo 0 1 256 256 0
tcpsndbuf 0 0 319488 524288 0
tcprcvbuf 0 0 319488 524288 0
othersockbuf 6684 7888 132096 336896 0
dgramrcvbuf 0 8372 132096 132096 0
numothersock 8 10 80 80 0
dcachesize 87672 92168 1048576 1097728 0
numfile 238 306 2048 2048 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 10 16 128 128 0
</pre>

You can see if you hit the limit for some [[UBC]] parameters by analyzing the last column (named <code>failcnt</code>). It shows a number of failures for this counter, i.e. a number of times a parameter hit the limit. Usually what you need to do is to increase the parameter in question. But you need to do it carefully, and here is how.

<ol>
<li>Get the current values for the parameter's barrier and limit. For example, we want to increase kmemsize values. From <code>/proc/user_beancounters</code> we see that <code>kmemsize</code> barrier is 2752512, and its limit is 2936012.
</li>

<li>Increase the values. Say, we want to double <code>kmemsize</code>. This is how it can be done using built-in bash arithmetics:
<pre>
# vzctl set 123 --kmemsize $((2752512*2)):$((2936012*2)) --save
</pre>
By using the <code>--save</code> flag, we indicate we want to apply the new setting to the running container and save it in the configuration file (from which the settings will be taken during next container start).
</li>

<li>Check the new configuration. Issue the following command:
<pre>
# vzcfgvalidate /etc/vz/conf/123.conf
</pre>
If something is wrong, you need to fix it as suggested by the utility.
</li>
</ol>

For more in-depth explanation of different parameters, their meaning and how to set them properly, see [[setting UBC parameters]].

== Disk quota ==
To check if your [[container]] exceeded its disk quota, use the following commands (inside a container):
<pre>
# df
Filesystem 1K-blocks Used Available Use% Mounted on
simfs 1048576 327664 720912 32% /
# df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
simfs 200000 18857 181143 10% /
</pre>

The first command shows disk space usage and the second command shows the inodes usage (you can roughly use the inodes count as a number of files/directories on your system).

If one of the commands shows a usage of 100% you have exceeded one of the disk quota limits.

You can increase the limit from the host system ([[CT0]] [[aka]] [[VE0]]) only. This is how:
<ol>
<li>Get the current values for disk quota:
<pre># vzquota stat 123
resource usage softlimit hardlimit grace
1k-blocks 327664 1048576 1153434
inodes 18857 200000 220000
</pre>
</li>

<li>To increase the disk space quota, use vzctl set --diskspace. For example, we want to increase it by a factor of 2:
<pre>
vzctl set 123 --diskspace $(( 1048576*2 )):$(( 1153434*2 )) --save
</pre>
</li>

<li>To increase the disk inodes quota, use <tt>vzctl set --diskinodes</tt>. For example, we want to increase it by a factor of 3:
<pre>
vzctl set 123 --diskinodes $(( 200000*3 )):$(( 220000*3 )) --save
</pre>
</li>
</ol>

{{Note|shell does not support floating-point arithmetic, i.e. you can not use expressions like <code>$(( 220000*1.5 ))</code>. To use floating point, try <code>bc</code> instead, something like this: <code><nowiki>$(echo 220000*1.5 | bc)</nowiki></code>.}}

== CPU ==

There are two parameters controlling fair CPU scheduler in OpenVZ: cpuunits and cpulimit.

{{Stub}}

[[Category: Troubleshooting]]
[[Category: HOWTO]]
[[Category: UBC]]
[[Category: Resource management]]
[[Category: Disk quota]]

Resource shortage

2008-09-05T13:11:42Z

Fayette: /* Disk quota */

Sometimes you see strange failures from some programs inside your [[container]]. In some cases it means one of the resources controlled by OpenVZ has hit the limit.

The first thing to do is to check the contents of the /proc/user_beancounters file in your [[container]]. The last column of output is the fail counter. Each time a resource hits the limit, the fail counter is incremented. So, if you see non-zero values in the failcnt column that means something is wrong.

There are two ways to fix the situation: reconfigure (in some cases recompile) the application, or change the resource management settings.

== [[UBC]] parameters ==

Here is an example of current [[UBC]] values obtained from <code>/proc/user_beancounters</code> file in container 123:
<pre>
# cat /proc/user_beancounters
Version: 2.5
uid resource held maxheld barrier limit failcnt
123: kmemsize 836919 1005343 2752512 2936012 0
lockedpages 0 0 32 32 0
privvmpages 4587 7289 49152 53575 0
shmpages 39 39 8192 8192 0
dummy 0 0 0 0 0
numproc 20 26 65 65 0
physpages 2267 2399 0 2147483647 0
vmguarpages 0 0 6144 2147483647 0
oomguarpages 2267 2399 6144 2147483647 0
numtcpsock 3 3 80 80 0
numflock 3 4 100 110 0
numpty 1 1 16 16 0
numsiginfo 0 1 256 256 0
tcpsndbuf 0 0 319488 524288 0
tcprcvbuf 0 0 319488 524288 0
othersockbuf 6684 7888 132096 336896 0
dgramrcvbuf 0 8372 132096 132096 0
numothersock 8 10 80 80 0
dcachesize 87672 92168 1048576 1097728 0
numfile 238 306 2048 2048 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 10 16 128 128 0
</pre>

You can see if you hit the limit for some [[UBC]] parameters by analyzing the last column (named <code>failcnt</code>). It shows a number of failures for this counter, i.e. a number of times a parameter hit the limit. Usually what you need to do is to increase the parameter in question. But you need to do it carefully, and here is how.

<ol>
<li>Get the current values for the parameter's barrier and limit. For example, we want to increase kmemsize values. From <code>/proc/user_beancounters</code> we see that <code>kmemsize</code> barrier is 2752512, and its limit is 2936012.
</li>

<li>Increase the values. Say, we want to double <code>kmemsize</code>. This is how it can be done using built-in bash arithmetics:
<pre>
# vzctl set 123 --kmemsize $((2752512*2)):$((2936012*2)) --save
</pre>
By using the <code>--save</code> flag, we indicate we want to apply the new setting to the running container and save it in the configuration file (from which the settings will be taken during next container start).
</li>

<li>Check the new configuration. Issue the following command:
<pre>
# vzcfgvalidate /etc/vz/conf/123.conf
</pre>
If something is wrong, you need to fix it as suggested by the utility.
</li>
</ol>

For more in-depth explanation of different parameters, their meaning and how to set them properly, see [[setting UBC parameters]].

== Disk quota ==
To check if your [[container]] exceeded its disk quota, use the following commands (inside a container):
<pre>
# df
Filesystem 1K-blocks Used Available Use% Mounted on
simfs 1048576 327664 720912 32% /
# df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
simfs 200000 18857 181143 10% /
</pre>

The first command shows disk space usage and the second command shows the inodes usage (you can roughly use the inodes count as a number of files/directories on your system).

If one of the commands shows a usage of 100% you have exceeded one of the disk quota limits.

You can increase the limit from the host system ([[CT0]] aka [[VE0]]) only. This is how:
<ol>
<li>Get the current values for disk quota:
<pre># vzquota stat 123
resource usage softlimit hardlimit grace
1k-blocks 327664 1048576 1153434
inodes 18857 200000 220000
</pre>
</li>

<li>To increase the disk space quota, use vzctl set --diskspace. For example, we want to increase it by a factor of 2:
<pre>
vzctl set 123 --diskspace $(( 1048576*2 )):$(( 1153434*2 )) --save
</pre>
</li>

<li>To increase the disk inodes quota, use <tt>vzctl set --diskinodes</tt>. For example, we want to increase it by a factor of 3:
<pre>
vzctl set 123 --diskinodes $(( 200000*3 )):$(( 220000*3 )) --save
</pre>
</li>
</ol>

{{Note|shell does not support floating-point arithmetic, i.e. you can not use expressions like <code>$(( 220000*1.5 ))</code>. To use floating point, try <code>bc</code> instead, something like this: <code><nowiki>$(echo 220000*1.5 | bc)</nowiki></code>.}}

== CPU ==

There are two parameters controlling fair CPU scheduler in OpenVZ: cpuunits and cpulimit.

{{Stub}}

[[Category: Troubleshooting]]
[[Category: HOWTO]]
[[Category: UBC]]
[[Category: Resource management]]
[[Category: Disk quota]]

Resource shortage

2008-09-05T13:11:06Z

Fayette: /* Disk quota */

Sometimes you see strange failures from some programs inside your [[container]]. In some cases it means one of the resources controlled by OpenVZ has hit the limit.

The first thing to do is to check the contents of the /proc/user_beancounters file in your [[container]]. The last column of output is the fail counter. Each time a resource hits the limit, the fail counter is incremented. So, if you see non-zero values in the failcnt column that means something is wrong.

There are two ways to fix the situation: reconfigure (in some cases recompile) the application, or change the resource management settings.

== [[UBC]] parameters ==

Here is an example of current [[UBC]] values obtained from <code>/proc/user_beancounters</code> file in container 123:
<pre>
# cat /proc/user_beancounters
Version: 2.5
uid resource held maxheld barrier limit failcnt
123: kmemsize 836919 1005343 2752512 2936012 0
lockedpages 0 0 32 32 0
privvmpages 4587 7289 49152 53575 0
shmpages 39 39 8192 8192 0
dummy 0 0 0 0 0
numproc 20 26 65 65 0
physpages 2267 2399 0 2147483647 0
vmguarpages 0 0 6144 2147483647 0
oomguarpages 2267 2399 6144 2147483647 0
numtcpsock 3 3 80 80 0
numflock 3 4 100 110 0
numpty 1 1 16 16 0
numsiginfo 0 1 256 256 0
tcpsndbuf 0 0 319488 524288 0
tcprcvbuf 0 0 319488 524288 0
othersockbuf 6684 7888 132096 336896 0
dgramrcvbuf 0 8372 132096 132096 0
numothersock 8 10 80 80 0
dcachesize 87672 92168 1048576 1097728 0
numfile 238 306 2048 2048 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 10 16 128 128 0
</pre>

You can see if you hit the limit for some [[UBC]] parameters by analyzing the last column (named <code>failcnt</code>). It shows a number of failures for this counter, i.e. a number of times a parameter hit the limit. Usually what you need to do is to increase the parameter in question. But you need to do it carefully, and here is how.

<ol>
<li>Get the current values for the parameter's barrier and limit. For example, we want to increase kmemsize values. From <code>/proc/user_beancounters</code> we see that <code>kmemsize</code> barrier is 2752512, and its limit is 2936012.
</li>

<li>Increase the values. Say, we want to double <code>kmemsize</code>. This is how it can be done using built-in bash arithmetics:
<pre>
# vzctl set 123 --kmemsize $((2752512*2)):$((2936012*2)) --save
</pre>
By using the <code>--save</code> flag, we indicate we want to apply the new setting to the running container and save it in the configuration file (from which the settings will be taken during next container start).
</li>

<li>Check the new configuration. Issue the following command:
<pre>
# vzcfgvalidate /etc/vz/conf/123.conf
</pre>
If something is wrong, you need to fix it as suggested by the utility.
</li>
</ol>

For more in-depth explanation of different parameters, their meaning and how to set them properly, see [[setting UBC parameters]].

== Disk quota ==
To check if your [[container]] exceeded its disk quota, use the following commands (inside a container):
<pre>
# df
Filesystem 1K-blocks Used Available Use% Mounted on
simfs 1048576 327664 720912 32% /
# df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
simfs 200000 18857 181143 10% /
</pre>

The first command shows disk space usage and the second command shows the inodes usage (you can roughly use the inodes count as a number of files/directories on your system).

If one of the commands shows a usage of 100% you have exceeded one of the disk quota limits.

You can increase the limit from the host system ([[CT0]] [[aka VE0]]) only. This is how:
<ol>
<li>Get the current values for disk quota:
<pre># vzquota stat 123
resource usage softlimit hardlimit grace
1k-blocks 327664 1048576 1153434
inodes 18857 200000 220000
</pre>
</li>

<li>To increase the disk space quota, use vzctl set --diskspace. For example, we want to increase it by a factor of 2:
<pre>
vzctl set 123 --diskspace $(( 1048576*2 )):$(( 1153434*2 )) --save
</pre>
</li>

<li>To increase the disk inodes quota, use <tt>vzctl set --diskinodes</tt>. For example, we want to increase it by a factor of 3:
<pre>
vzctl set 123 --diskinodes $(( 200000*3 )):$(( 220000*3 )) --save
</pre>
</li>
</ol>

{{Note|shell does not support floating-point arithmetic, i.e. you can not use expressions like <code>$(( 220000*1.5 ))</code>. To use floating point, try <code>bc</code> instead, something like this: <code><nowiki>$(echo 220000*1.5 | bc)</nowiki></code>.}}

== CPU ==

There are two parameters controlling fair CPU scheduler in OpenVZ: cpuunits and cpulimit.

{{Stub}}

[[Category: Troubleshooting]]
[[Category: HOWTO]]
[[Category: UBC]]
[[Category: Resource management]]
[[Category: Disk quota]]

One more entry point

2008-09-05T13:01:55Z

Fayette:

This entry point of OpenVZ wiki is created in order to arrange all the information on this site more logically. Here is a structure something like a table of contents. Each chapter contains a collection of pages that are relevant to subject of the chapter. There can be multiple articles on the same subject in one chapter: one writes an article one way, another does it in another way. It is important that pages in chapters are ordered by the complexity of the material e. g. simpler articles appear first.
This allows the OpenVZ novices to read only the first pages of each chapter to get a feature working. Advanced users can quickly go through this table of contents and find more specific information that they actually need.

We urge you to create entries in this table (even without writing the article) in order for the community to know what topics are popular and need to be described. Writing articles is also very useful.

== Table of Contents ==
{| width="100%"
| valign="top" width="50%" |
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Introduction to Virtualization Technology
|}
* [[Introduction to virtualization]]
* [[Virtualization implementation comparison]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Basic concepts of OpenVZ
|}
* [[VE]] = [[Virtual Environment]]
* [[HN]] = [[HW]] = [[Hardware Node]] = [[Host system]]
* [[CT0]]
* [[OS template]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Choosing and Installing OpenVZ
|}
* [[Quick installation]] -- [[Downloading and installing]]
* [[OpenVZ components]]
* [[Kernel versioning]]
* [[Different kernel flavors (UP, SMP, ENTERPRISE, ENTNOSPLIT)]]
* [[Features]]
* [[Security]]
* [[HA cluster with DRBD and Heartbeat]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Templates
|}
* [[OS template]]
* [[OS template cache]]
* [[OS template metadata]]
* [[Adding OS template to the installation]]
* [[OS template cache preparation]]
* [[Debian template creation]]
* [[Gentoo template creation]]
* [[Slackware template creation]]
* [[Ubuntu template]]
* [[Creating your own template]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | First steps inside OpenVZ environment
|}
* [[VE creation]]
* [[Starting VE]]
* [[Entering VE]]
* [[Running a process in VE]]
* [[Stoping VE]]
* [[Destroying VE]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Resource accounting
|}
* [[User beancounters]]
* [[OpenVZ quota]]
* [[CPU Fairscheduler]]
* [[Resource shortage]]
|}
| valign="top" | 
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Network
|}
* [[Setting up network in VE]]
* [[Virtual network device]]
* [[Virtual Ethernet device]]
* [[iptables in OpenVZ environment]]
* [[Differences between venet and veth]]
* [[Using NAT for VE with private IPs]]
* [[Source based routing]]
* [[VPN via the TUN/TAP device]]
* [[Traffic accounting with iptables]]
* [[Traffic shaping with tc]]
* [[Using bridges in OpenVZ]]
* [[NFS server inside VE]]
* [[X inside VE]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Checkpointing and Migration
|}
* [[What is checkpointing]]
* [[Live migration]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Working with OpenVZ code
|}
* [[Porting the kernel]]
* [[Kernel build]]
* [[Containers/Pidcache]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Troubleshooting
|}
* [[Magic SysRq Key]]
* [[Remote console setup]]
* [[SysRq debugger]]
* [[When you have an oops]]
* [[Modifying initrd image]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Using specific tools in VE
|}
* [[Asterisk in VE with debian stable]]
* [[Plesk in VE]]
* [[Yum]]
* [[Shared webhosting]]
* [[CPanel in VE]]
* [[Zimbra on OpenVZ on CentOS]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Other
|}
* [[Processes scope and visibility]]
* [[Setting up a mirror]]
* [[MAX ULONG]]
* [[Memory page]]
* [[Artwork]]
* [[FAQ]]
|}
|}

One more entry point

2008-09-05T13:00:02Z

Fayette:

This entry point of OpenVZ wiki is created in order to arrange all the information on this site more logically. Here is a structure something like a table of contents. Each chapter contains a collection of pages that are relevant to subject of the chapter. There can be multiple articles on the same subject in one chapter: one writes an article one way, another does it in another way. It is important that pages in chapters are ordered by the complexity of the material e. g. simpler articles appear first.
This allows the OpenVZ novices to read only the first pages of each chapter to get a feature working. Advanced users can quickly go through this table of contents and find more specific information that they actually need.

We urge you to create entries in this table (even without writing the article) in order for the community to know what topics are popular and need to be described. Writing articles is also very useful in fact.

== Table of Contents ==
{| width="100%"
| valign="top" width="50%" |
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Introduction to Virtualization Technology
|}
* [[Introduction to virtualization]]
* [[Virtualization implementation comparison]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Basic concepts of OpenVZ
|}
* [[VE]] = [[Virtual Environment]]
* [[HN]] = [[HW]] = [[Hardware Node]] = [[Host system]]
* [[CT0]]
* [[OS template]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Choosing and Installing OpenVZ
|}
* [[Quick installation]] -- [[Downloading and installing]]
* [[OpenVZ components]]
* [[Kernel versioning]]
* [[Different kernel flavors (UP, SMP, ENTERPRISE, ENTNOSPLIT)]]
* [[Features]]
* [[Security]]
* [[HA cluster with DRBD and Heartbeat]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Templates
|}
* [[OS template]]
* [[OS template cache]]
* [[OS template metadata]]
* [[Adding OS template to the installation]]
* [[OS template cache preparation]]
* [[Debian template creation]]
* [[Gentoo template creation]]
* [[Slackware template creation]]
* [[Ubuntu template]]
* [[Creating your own template]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | First steps inside OpenVZ environment
|}
* [[VE creation]]
* [[Starting VE]]
* [[Entering VE]]
* [[Running a process in VE]]
* [[Stoping VE]]
* [[Destroying VE]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Resource accounting
|}
* [[User beancounters]]
* [[OpenVZ quota]]
* [[CPU Fairscheduler]]
* [[Resource shortage]]
|}
| valign="top" | 
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Network
|}
* [[Setting up network in VE]]
* [[Virtual network device]]
* [[Virtual Ethernet device]]
* [[iptables in OpenVZ environment]]
* [[Differences between venet and veth]]
* [[Using NAT for VE with private IPs]]
* [[Source based routing]]
* [[VPN via the TUN/TAP device]]
* [[Traffic accounting with iptables]]
* [[Traffic shaping with tc]]
* [[Using bridges in OpenVZ]]
* [[NFS server inside VE]]
* [[X inside VE]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Checkpointing and Migration
|}
* [[What is checkpointing]]
* [[Live migration]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Working with OpenVZ code
|}
* [[Porting the kernel]]
* [[Kernel build]]
* [[Containers/Pidcache]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Troubleshooting
|}
* [[Magic SysRq Key]]
* [[Remote console setup]]
* [[SysRq debugger]]
* [[When you have an oops]]
* [[Modifying initrd image]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Using specific tools in VE
|}
* [[Asterisk in VE with debian stable]]
* [[Plesk in VE]]
* [[Yum]]
* [[Shared webhosting]]
* [[CPanel in VE]]
* [[Zimbra on OpenVZ on CentOS]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Other
|}
* [[Processes scope and visibility]]
* [[Setting up a mirror]]
* [[MAX ULONG]]
* [[Memory page]]
* [[Artwork]]
* [[FAQ]]
|}
|}

One more entry point

2008-09-05T12:54:20Z

Fayette:

This entry point of OpenVZ wiki is created in order to arrange all the information on this site more logically. General idea of arrangement is the following. Here you can find something like table of contents. Each chapter contains a collection of pages, that pass to the subject of the chapter. Of course there can be articles on the same subject in one chapter: one writes an article in his own way, another person does it in another way. It is important that pages in chapters are ordered by the complexity of the material.
This allows the OpenVZ novices to read only the first pages of each chapter to get a feature working. Advanced users can quickly go through this table of contents and find more specific information that they actually need.

It is appreciated that you will create points in this table (even without writing the article) in order for the community to know what topics are popular and need to be described. Writing articles is also very useful in fact.

== Table of Contents ==
{| width="100%"
| valign="top" width="50%" |
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Introduction to Virtualization Technology
|}
* [[Introduction to virtualization]]
* [[Virtualization implementation comparison]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Basic concepts of OpenVZ
|}
* [[VE]] = [[Virtual Environment]]
* [[HN]] = [[HW]] = [[Hardware Node]] = [[Host system]]
* [[CT0]]
* [[OS template]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Choosing and Installing OpenVZ
|}
* [[Quick installation]] -- [[Downloading and installing]]
* [[OpenVZ components]]
* [[Kernel versioning]]
* [[Different kernel flavors (UP, SMP, ENTERPRISE, ENTNOSPLIT)]]
* [[Features]]
* [[Security]]
* [[HA cluster with DRBD and Heartbeat]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Templates
|}
* [[OS template]]
* [[OS template cache]]
* [[OS template metadata]]
* [[Adding OS template to the installation]]
* [[OS template cache preparation]]
* [[Debian template creation]]
* [[Gentoo template creation]]
* [[Slackware template creation]]
* [[Ubuntu template]]
* [[Creating your own template]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | First steps inside OpenVZ environment
|}
* [[VE creation]]
* [[Starting VE]]
* [[Entering VE]]
* [[Running a process in VE]]
* [[Stoping VE]]
* [[Destroying VE]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Resource accounting
|}
* [[User beancounters]]
* [[OpenVZ quota]]
* [[CPU Fairscheduler]]
* [[Resource shortage]]
|}
| valign="top" | 
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Network
|}
* [[Setting up network in VE]]
* [[Virtual network device]]
* [[Virtual Ethernet device]]
* [[iptables in OpenVZ environment]]
* [[Differences between venet and veth]]
* [[Using NAT for VE with private IPs]]
* [[Source based routing]]
* [[VPN via the TUN/TAP device]]
* [[Traffic accounting with iptables]]
* [[Traffic shaping with tc]]
* [[Using bridges in OpenVZ]]
* [[NFS server inside VE]]
* [[X inside VE]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Checkpointing and Migration
|}
* [[What is checkpointing]]
* [[Live migration]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Working with OpenVZ code
|}
* [[Porting the kernel]]
* [[Kernel build]]
* [[Containers/Pidcache]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Troubleshooting
|}
* [[Magic SysRq Key]]
* [[Remote console setup]]
* [[SysRq debugger]]
* [[When you have an oops]]
* [[Modifying initrd image]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Using specific tools in VE
|}
* [[Asterisk in VE with debian stable]]
* [[Plesk in VE]]
* [[Yum]]
* [[Shared webhosting]]
* [[CPanel in VE]]
* [[Zimbra on OpenVZ on CentOS]]
|}
{| style="border:1px solid #ccc;background-color:#f7fff7;margin-top:+.7em" cellpadding="10" width=100%
|
{| style="background-color:#e5ffe5;border:1px solid #ccc;" width=100%
| align=center | Other
|}
* [[Processes scope and visibility]]
* [[Setting up a mirror]]
* [[MAX ULONG]]
* [[Memory page]]
* [[Artwork]]
* [[FAQ]]
|}
|}

Performance tuning

2008-09-04T14:49:01Z

Fayette:

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

= HW node environment tuning =

== Disable unnecessary services ==

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

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

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

== Shell scripts performance improvement ==

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

To see current settings, type

# locale

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

# export LANG=C

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

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

= Container tuning =

== CPU distribution inside container on SMP hosts ==

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

To set the number of CPUs available inside container use:

# vzctl set $CTID --cpus N

== Network checksumming ==

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

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

# ethtool -k eth0

Make sure that tx/rx features are switched on.

To see current offload settings for the venet0 device, type

# ethtool -k venet0

To set offload settings on for the venet0 device, type

# ethtool -K venet0 tx on sg on

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

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

== Shell scripts performance improvement ==

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

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

# build-locale-archive

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

Archlinux Template creation

2008-09-04T14:42:51Z

Fayette: /* Prerequisites */

Instructions manually create a minimal Archlinux (0.8) "Voodoo" OS Template.

== Prerequisites ==

I used a modified archbootstrap script which can be found at http://forzza.systs.org/openvz-misc/
{{Note | This link is currently broken}}
Edit settings of script "archbootstrap" :

ARCH="i686"
IGNORE="rp-pppoe ppp wireless_tools xfsdump xfsprogs reiserfsprogs lshwd usbutils pciutils pcmciautils module-init-tools mdadm mkinitcpio libusb jfsutils lvm2 lilo cryptsetup device-mapper dhcpcd hwdetect dmapi gen-init-cpio grub"
umark PACMAN_OPTS (remove '#')

{{Note|I suggest to place the build for OpenVZ templates to /vz/template/, schema: /vz/template/$DIST/$VERSION/$ARCH/}}

Built this OS-Template with:

{| class="wikitable"
|| [[CT0]]_dist || Debian
|-
|| [[CT0]]_ARCH || i386
|-
|| DIST || arch
|-
|| VERSION || 0.8
|-
|| ARCH || depends on CT0 settings above
|}

== bootstrapping Archlinux ==

Syntax:

CT0_# /usr/bin/archbootstrap /vz/template/$DIST/$VERSION/$ARCH/ [MIRROR]

{{Note|Please use mirrors! A full list of Archlinux mirrors: http://wiki.archlinux.org/index.php/Mirror}}

== enter the Build with chroot ==

All the commands below are executed from the root shell. I this howto "chroot" is used to enter as NEWROOT, a BUILD-VE must not be created!

CT0_# chroot /vz/template/$DIST/$VERSION/$ARCH/

=== setting DNS server ===

For the chroot BUILD we also need to specify a DNS for it:

BUILD_# mv /etc/resolv.conf.pacorig /etc/resolv.conf

=== update and install packages ===

Update (sync) pacman cache and update installed packages

BUILD_# pacman -Syu

Install openssh (client and server) , quota-tools and iproute

BUILD_# pacman -S openssh quota-tools iproute

=== fix /etc/mtab ===

Add symlink /proc/mount /etc/mtab

BUILD_# ln -s /proc/mounts /etc/mtab

=== fix /etc/inittab ===

Remove getty lines from inittab:

BUILD_# sed -i -e '/getty/d' /etc/inittab

=== create device nodes ===

Create device nodes at /dev, like console, full, null, zero, urandom, ptmx and fifo of initctl

BUILD_# mknod -m 600 /dev/console c 5 1
BUILD_# mknod -m 666 /dev/tty c 5 0
BUILD_# mknod -m 666 /dev/full c 1 7
BUILD_# mknod -m 600 /dev/initctl p
BUILD_# mknod -m 666 /dev/null c 1 3
BUILD_# mknod -m 666 /dev/ptmx c 5 2
BUILD_# mkdir pts
BUILD_# mknod -m 666 /dev/random c 1 8
BUILD_# mknod -m 444 /dev/urandom c 1 9
BUILD_# mknod -m 666 /dev/zero c 1 5

=== sysinit script modification ===

Remove deleting of /etc/mtab in /etc/rc.sysinit and add mounting of /dev/pts

BUILD_# nano /etc/rc.sysinit

[...]
/bin/rm -f /etc/mtab
[...]

to

[...]
#/bin/rm -f /etc/mtab
/bin/mount -t devpts none /dev/pts
[...]

=== modify the main configuration file ===

BUILD_# nano /etc/rc.conf

# Localization
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"

# example : German KEYMAP and Timezone to Berlin
TIMEZONE="Europe/Berlin"
KEYMAP="de-latin1-nodeadkeys"

CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# Network settings
HOSTNAME="localhost"

# DAEMONS
# Add openssh to DAEMONS, start at bootup ; ssh-keys are build on first VE start !!!
DAEMONS=(syslog-ng network netfs crond ssh)

=== enable ssh connections ===

{{Note|All connection are disabled to VE, see /etc/hosts.deny, only affected server built-in with libwrap}}

Allow ssh:

BUILD_# echo "ssh: ALL : ALLOW" >> /etc/hosts.allow}

=== lock (disable) the root account ===

BUILD_# passwd -l root

=== exit the chroot to CT0 ===

BUILD_# exit

== build a exclude list ==

Shrink the OS-Template, so not all files needed in a VE - OS - TEMPLATE

Remove unused pacman backup files:

CT0_# find ./ -name '*.pacorig' > ../exclude.list-$ARCH

<code>/etc/resolv.conf</code> is added by vzctl:

CT0_# echo "etc/resolv.conf" >> ../exclude.list-$ARCH

Don't add downloaded pkg to ostemplate:

CT0_# find ./var/cache/ -name '*.tar.gz' >> ../exclude.list-$ARCH

We dont need no logs and history:

CT0_# find ./var/cache/ -name '*.tar.gz' >> ../exlcude.list-$ARCH
CT0_# find ./root/.bash_history >> ../exclude.list-$ARCH

== create OS template ==

CT0_# tar -X ../exclude.list-$ARCH -czf /vz/template/cache/arch-0.8-$ARCH-minimal.tar.gz ./

== use the OS template ==

CT0_# vzctl create <VEID> --ostemplate arch-0.8-$ARCH-minimal ...

== update the OS template ==

To update a template is really easy, enter the build with chroot, performing upgrade task

CT0_# chroot /vz/template/$DIST/$VERSION/$ARCH/ 'pacman -Syu'

Update the exclude list, and pack upgraded OS - Template

== Links ==

* [http://wiki.archlinux.org/index.php/Main_Page Archlinux wiki]

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

Control panels

2008-08-04T23:41:10Z

Fayette: /* Free software / Open source */

This page contains links to different control panels for OpenVZ, written by third parties. If you know the project that's missing here, please add it.

== Free software / Open source ==
* Proxmox Virtual Environment: [http://pve.proxmox.com Proxmox VE Wiki] - including bare-metal ISO installer
* WebVZ: [http://webvz.sourceforge.net/ homepage] Uses Ruby on Rails which makes it a poor choice for Debian, Ubuntu and other .deb style distros.
* Webmin: [http://www.webmin.com/ homepage] | [http://www.webmin.com/cgi-bin/search_third.cgi?search=OpenVZ OpenVZ plugin] | Version 1.0, last updated 2006-02-07
* Vtonf: [http://www.vtonf.com/ homepage] | According to the documentation only runs on Centos 4.5 or higher. Last change January 2008

== Proprietary / non-free ==
* FluidVM: [http://www.binarykarma.com Home Page] • [http://www.binarykarma.com/demo.php Demo Videos] • [http://www.binarykarma.com/fluidvm_screenshots.php Screen shots]
* VZ-Manager: [http://vzmanager.de/ homepage (German)]
* HyperVM: [http://lxlabs.com/software/hypervm/ homepage]
* vzAdmin: [http://www.vzAdmin.info/ homepage (German)]
* Aventurin{e}: [http://www.aventurin.net/ homepage (English)]

== Frozen projects ==
* VZAdmin: [http://www.ronny-goerner.de/ homepage] ''seems not available now''
* WVZ: [http://homaly.dunanet.hu/wvz/ homepage] ''seems frozen''
* New OpenVZ Web Based Control Panel by rsailor: {{forum|230}} ''seems not available now''
* EasyVZ: [http://easyvz.sourceforge.net/ screenshots] | [http://sourceforge.net/projects/easyvz sf.net project page] (little bit outdated, but only working and free control panel?) (requires Unix/Linux)
* Mwamko: [http://mwamko.devjavu.com/ homepage]
* OpenVZ Control panel for Windows(r): {{forum|1491}} | [http://downloads.qmailrocks.ru/vz/ downloads] ''unknown license''

== In development ==
* WIVZ/GIVZ: [http://source.icenetx.net/ homepage] Release scheduled for October 2008. Unknow license.
* RoboVZ: [http://sharesource.org/project/robovz homepage] {{forum|2559}} Lots of promises since announced in May 2007, nothing usable yet. Possibly GPL license.

Control panels

2008-08-04T23:34:20Z

Fayette: /* Free software / Open source */

This page contains links to different control panels for OpenVZ, written by third parties. If you know the project that's missing here, please add it.

== Free software / Open source ==
* Proxmox Virtual Environment: [http://pve.proxmox.com Proxmox VE Wiki] - including bare-metal ISO installer
* WebVZ: [http://webvz.sourceforge.net/ homepage] Uses Ruby on Rails which makes it a poor choice for Debian, Ubuntu and other .deb style distros.
* Webmin: [http://www.webmin.com/ homepage] | [http://www.webmin.com/cgi-bin/search_third.cgi?search=OpenVZ OpenVZ plugin] | Version 1.0, last updated 2006-02-07
* Vtonf: [http://www.vtonf.com/ homepage]

== Proprietary / non-free ==
* FluidVM: [http://www.binarykarma.com Home Page] • [http://www.binarykarma.com/demo.php Demo Videos] • [http://www.binarykarma.com/fluidvm_screenshots.php Screen shots]
* VZ-Manager: [http://vzmanager.de/ homepage (German)]
* HyperVM: [http://lxlabs.com/software/hypervm/ homepage]
* vzAdmin: [http://www.vzAdmin.info/ homepage (German)]
* Aventurin{e}: [http://www.aventurin.net/ homepage (English)]

== Frozen projects ==
* VZAdmin: [http://www.ronny-goerner.de/ homepage] ''seems not available now''
* WVZ: [http://homaly.dunanet.hu/wvz/ homepage] ''seems frozen''
* New OpenVZ Web Based Control Panel by rsailor: {{forum|230}} ''seems not available now''
* EasyVZ: [http://easyvz.sourceforge.net/ screenshots] | [http://sourceforge.net/projects/easyvz sf.net project page] (little bit outdated, but only working and free control panel?) (requires Unix/Linux)
* Mwamko: [http://mwamko.devjavu.com/ homepage]
* OpenVZ Control panel for Windows(r): {{forum|1491}} | [http://downloads.qmailrocks.ru/vz/ downloads] ''unknown license''

== In development ==
* WIVZ/GIVZ: [http://source.icenetx.net/ homepage] Release scheduled for October 2008. Unknow license.
* RoboVZ: [http://sharesource.org/project/robovz homepage] {{forum|2559}} Lots of promises since announced in May 2007, nothing usable yet. Possibly GPL license.

Control panels

2008-08-04T23:27:48Z

Fayette: /* Free software / Open source */

This page contains links to different control panels for OpenVZ, written by third parties. If you know the project that's missing here, please add it.

== Free software / Open source ==
* Proxmox Virtual Environment: [http://pve.proxmox.com Proxmox VE Wiki] - including bare-metal ISO installer
* WebVZ: [http://webvz.sourceforge.net/ homepage] Uses Ruby on Rails which makes it a poor choice for Debian, Ubuntu and other .deb style distros.
* Webmin: [http://www.webmin.com/ homepage] | [http://www.webmin.com/cgi-bin/search_third.cgi?search=OpenVZ OpenVZ plugin]
* Vtonf: [http://www.vtonf.com/ homepage]

== Proprietary / non-free ==
* FluidVM: [http://www.binarykarma.com Home Page] • [http://www.binarykarma.com/demo.php Demo Videos] • [http://www.binarykarma.com/fluidvm_screenshots.php Screen shots]
* VZ-Manager: [http://vzmanager.de/ homepage (German)]
* HyperVM: [http://lxlabs.com/software/hypervm/ homepage]
* vzAdmin: [http://www.vzAdmin.info/ homepage (German)]
* Aventurin{e}: [http://www.aventurin.net/ homepage (English)]

== Frozen projects ==
* VZAdmin: [http://www.ronny-goerner.de/ homepage] ''seems not available now''
* WVZ: [http://homaly.dunanet.hu/wvz/ homepage] ''seems frozen''
* New OpenVZ Web Based Control Panel by rsailor: {{forum|230}} ''seems not available now''
* EasyVZ: [http://easyvz.sourceforge.net/ screenshots] | [http://sourceforge.net/projects/easyvz sf.net project page] (little bit outdated, but only working and free control panel?) (requires Unix/Linux)
* Mwamko: [http://mwamko.devjavu.com/ homepage]
* OpenVZ Control panel for Windows(r): {{forum|1491}} | [http://downloads.qmailrocks.ru/vz/ downloads] ''unknown license''

== In development ==
* WIVZ/GIVZ: [http://source.icenetx.net/ homepage] Release scheduled for October 2008. Unknow license.
* RoboVZ: [http://sharesource.org/project/robovz homepage] {{forum|2559}} Lots of promises since announced in May 2007, nothing usable yet. Possibly GPL license.

Control panels

2008-08-04T23:25:18Z

Fayette:

This page contains links to different control panels for OpenVZ, written by third parties. If you know the project that's missing here, please add it.

== Free software / Open source ==
* Proxmox Virtual Environment: [http://pve.proxmox.com Proxmox VE Wiki] - including bare-metal ISO installer
* WebVZ: [http://webvz.sourceforge.net/ homepage]
* Webmin: [http://www.webmin.com/ homepage] | [http://www.webmin.com/cgi-bin/search_third.cgi?search=OpenVZ OpenVZ plugin]
* Vtonf: [http://www.vtonf.com/ homepage]

== Proprietary / non-free ==
* FluidVM: [http://www.binarykarma.com Home Page] • [http://www.binarykarma.com/demo.php Demo Videos] • [http://www.binarykarma.com/fluidvm_screenshots.php Screen shots]
* VZ-Manager: [http://vzmanager.de/ homepage (German)]
* HyperVM: [http://lxlabs.com/software/hypervm/ homepage]
* vzAdmin: [http://www.vzAdmin.info/ homepage (German)]
* Aventurin{e}: [http://www.aventurin.net/ homepage (English)]

== Frozen projects ==
* VZAdmin: [http://www.ronny-goerner.de/ homepage] ''seems not available now''
* WVZ: [http://homaly.dunanet.hu/wvz/ homepage] ''seems frozen''
* New OpenVZ Web Based Control Panel by rsailor: {{forum|230}} ''seems not available now''
* EasyVZ: [http://easyvz.sourceforge.net/ screenshots] | [http://sourceforge.net/projects/easyvz sf.net project page] (little bit outdated, but only working and free control panel?) (requires Unix/Linux)
* Mwamko: [http://mwamko.devjavu.com/ homepage]
* OpenVZ Control panel for Windows(r): {{forum|1491}} | [http://downloads.qmailrocks.ru/vz/ downloads] ''unknown license''

== In development ==
* WIVZ/GIVZ: [http://source.icenetx.net/ homepage] Release scheduled for October 2008. Unknow license.
* RoboVZ: [http://sharesource.org/project/robovz homepage] {{forum|2559}} Lots of promises since announced in May 2007, nothing usable yet. Possibly GPL license.

Using NAT for container with private IPs

2008-07-28T12:58:09Z

Fayette: Added example of IP range specification.

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 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. For example to specify IP addresses from 192.168.2.12 through 192.168.2.25 use:
<pre>
# iptables -t nat -A POSTROUTING -s 192.168.2.12/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|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}}

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

Resource management

2008-05-26T10:16:47Z

Fayette:

'''OpenVZ resource management''' is a set of controls providing per-[[container]] resource accounting and limiting. This is required for multiple containers to coexist gracefully on a single [[host system]].

OpenVZ resource management includes these four primary controllers:

* [[User beancounters]] (a set of limits and guarantees controlled on a per container basis: memory etc.)
* [[Disk quota]]
* [[CPU Fair scheduler]]
* [[I/O priorities for VE]] and [[IO accounting]]

OpenVZ administrators can also use the following mainstream Linux mechanisms:
* [[Traffic accounting with iptables]]
* [[Traffic shaping with tc]]

[[Category:Resource management]]
[[Category:Definitions]]
[[Category:Kernel]]

UBC consistency check

2008-05-25T11:52:58Z

Fayette:

{{UBC toc}}

System resource control parameters have certain interdependencies. Constraints on the parameter settings are listed below. Indexes <code>bar</code> and <code>lim</code> in the formulae below mean the barrier and the limit of the parameters, respectively.

Configuration of resource control parameters for a container
is invalid if these constraints are not satisfied. The best way to ensure the
validity of the configuration is to use the {{man|vzcfgvalidate|8}} utility.

All the interdependencies discussed below and their importance are summarized in [[UBC interdependencies table]].

The configured limits can be checked through
* <code>/proc/user_beancounters</code> interface;
* container configuration files in <code>/etc/vz/conf/</code> directory.

== kmemsize should be enough for the expected number of processes ==
<math>kmemsize_{bar} \ge 40KB \cdot avnumproc + dcachesize_{lim}</math>

(<code>avnumproc</code> here stands for the expected average number of processes).

This constraint is important for applications to work reliably in the
container.
If it is not satisfied, applications will start to fail in the middle of
operations instead of failing while spawning more processes
and the application's ability to handle resource shortage will be very
limited.

== Memory allocation limits should not be less than the guarantee ==
<math> privvmpages_{bar} \ge vmguarpages_{bar}</math>

If this constraint is not satisfied, <code>vmguarpages</code> will not work.

== Send buffers should have enough space for all sockets ==
<math>tcpsndbuf_{lim} - tcpsndbuf_{bar} \ge 2.5KB \cdot numtcpsock</math>

<math>othersockbuf_{lim} - othersockbuf_{bar} \ge 2.5KB \cdot numothersock</math>

These constraints are also important.
If they are not satisfied, transmission of data over the sockets
may hang in some circumstances.

== Other TCP socket buffers should be big enough ==
<math>tcprcvbuf_{lim} - tcprcvbuf_{bar} \ge 2.5KB \cdot numtcpsock</math>

<math>tcprcvbuf_{bar} \ge 64KB</math>

<math>tcpsndbuf_{bar} \ge 64KB</math>

Selecting the left side equal to the right side in the inequalities
above ensures minimal performance of network communications.
Increasing the left side will increase performance to a certain extent.

== UDP socket buffers should be large enough if the system is not tight on memory ==
<math>dgramrcvbuf_{bar} \ge 129KB</math>

<math>othersockbuf_{bar} \ge 129KB</math>

These constraints are desired, but not essential.
Large enough buffers for UDP sockets improve reliability of datagram delivery.
However, note that if the UDP traffic is so bursty that it needs larger
buffers, the datagrams will likely be lost not because of resource control
limits, but because of other memory and performance limitations.

== Number of files limit should be adequate for the expected number of processes ==
<math>numfile \ge avnumproc \cdot 32</math>

Note that each process after a <code>execve(2)</code> system call
requires a file for each loaded shared library.
A too low <code>numfile</code> limit will increase the chances of failures
during <code>execve(2)</code> calls with error messages that are not clear
to the users.

== The limit on the total size of <code>dentry</code> and <code>inode</code> structures locked in memory should be adequate for allowed number of files ==

<math>dcachesize_{bar} \ge numfile \cdot 384\ \rm(bytes)</math>

A too low <code>dcachesize</code> limit will increase the chances of
file operation refusals resulting in unexpected application failures.

== Barrier should be less or equal than limit ==
In addition to the conditions listed above,

<math>barrier \le limit</math>

should be maintained for each parameter.

[[Category:Troubleshooting]]

IO accounting

2008-05-25T11:43:59Z

Fayette: /* Debugging information */

This page describes how accounting is done for I/O activity of VE processes. This feature is available beginning with OpenVZ kernels version <code>028test008</code>.

== New resources ==
The following resources are accounted:
; read bytes
: is the number of bytes read by tasks. Reads are always synchronous in the kernel so this type of resource is the easiest one.

; dirty bytes
: is the number of bytes that were dirty since VE start, i. e. data that isn't yet flushed to disk. This type of resource is accumulated using [[RSS_fractions_accounting|page beancounters]] and the context the page was dirtied by is determined like this:
:* if a page is mapped it's "mapper" is used as this may happen in any context (unmapping of a page under memory pressure);
:* if a page is not mapped — current BC is used as this can happen during usual write (writev) only.

; written bytes
: is the number of bytes flushed to disk. The beancounter charged with this is the one by which the page was dirtied.

; canceled bytes
: is the number of bytes that were dirty but weren't flushed to disk.

; missed bytes
: is the number of bytes that were dirtied but the context (beancounter) wasn't saved due to lack of memory.

== Proc interface ==
=== General information ===
As was described in [[BC proc entries|another article]] each beancounter has its own <code>/proc/bc/$BCID</code> directory where subsystems add their entries. I/O accounting adds an <code>ioacct</code> entry to show I/O information. This entry contains the following information:
<pre>
# cat /proc/bc/101/ioacct
read 24330240
write 598016
dirty 622592
cancel 24576
missed 0
...
</pre>

Note that <code>dirty</code> is not the size of dirty data at the moment, but the size of dirty data seen so far.

=== Debugging information ===
When <code>CONFIG_UBC_DEBUG_IO</code>, is on <code>/proc/bc/ioacct_debug</code> is added. This entry contains a snapshot of current dirty pages with its beancounter. For example:
<pre>
# cat /proc/bc/ioacct_debug
Races: io 0 anon 0 clean 0 missed 0
pb page flg cnt mcnt pb_list page_pb mapping ub
f7a4a520 e c17cfc68 Dawl 2 0 00000000 f7a4a521 c3870168 0
f7a15ce0 e c17d034c Dawl 2 0 00000000 f7a15ce1 c3870168 0
f72e4680 e c1083364 Dawl 2 0 00000000 f72e4681 c3870168 0
f72e4800 e c1083388 Dawl 2 0 00000000 f72e4801 c3870168 0
f7a15dc0 e c17d0010 Dawl 2 0 00000000 f7a15dc1 c3870168 0
</pre>

== Auxiliary information ==
Along with VFS I/O activity the following information is gathered
; sync counts
: The number of <code>sync(2)</code>, <code>fsync(2)</code>, <code>fdatasync(2)</code> and <code>sync_file_range</code>.
<pre>
# cat /proc/bc/101/ioacct
...
syncs_total 0
fsyncs_total 0
fdatasyncs_total 10
range_syncs_total 0
syncs_active 0
fsyncs_active 0
fdatasyncs_active 0
range_syncs_active 0
</pre>
<code>_active</code> suffix refers to the number of operations in progress.

; write/read calls counts
: The number of <code>read(2)</code>, <code>readv(2)</code>, <code>write(2)</code>, <code>writev(2)</code>, etc. and the number of bytes passed.
<pre>
# cat /proc/bc/101/ioacct
...
vfs_reads 24491
vfs_read_chars 2616512
vfs_writes 380
vfs_write_chars 30064899102
</pre>

; number of page beancounters pinned by I/O
: This is the number of page beancounters that save information about page dirtier. This is actually the number of dirty pages within beancounter at the moment.
<pre>
# cat /proc/bc/0/ioacct
...
write 598016
dirty 622592
...
io_pbs 0
# dd if=/dev/zero of=tmp bs=512 count=40
# cat /proc/bc/0/ioacct
...
write 598016
dirty 643072
...
io_pbs 5
# sync
# cat /proc/bc/0/ioacct
...
write 618496
dirty 643072
...
io_pbs 0
</pre>

[[Category:Resource management]]

IO accounting

2008-05-25T11:42:50Z

Fayette: /* General information */

This page describes how accounting is done for I/O activity of VE processes. This feature is available beginning with OpenVZ kernels version <code>028test008</code>.

== New resources ==
The following resources are accounted:
; read bytes
: is the number of bytes read by tasks. Reads are always synchronous in the kernel so this type of resource is the easiest one.

; dirty bytes
: is the number of bytes that were dirty since VE start, i. e. data that isn't yet flushed to disk. This type of resource is accumulated using [[RSS_fractions_accounting|page beancounters]] and the context the page was dirtied by is determined like this:
:* if a page is mapped it's "mapper" is used as this may happen in any context (unmapping of a page under memory pressure);
:* if a page is not mapped — current BC is used as this can happen during usual write (writev) only.

; written bytes
: is the number of bytes flushed to disk. The beancounter charged with this is the one by which the page was dirtied.

; canceled bytes
: is the number of bytes that were dirty but weren't flushed to disk.

; missed bytes
: is the number of bytes that were dirtied but the context (beancounter) wasn't saved due to lack of memory.

== Proc interface ==
=== General information ===
As was described in [[BC proc entries|another article]] each beancounter has its own <code>/proc/bc/$BCID</code> directory where subsystems add their entries. I/O accounting adds an <code>ioacct</code> entry to show I/O information. This entry contains the following information:
<pre>
# cat /proc/bc/101/ioacct
read 24330240
write 598016
dirty 622592
cancel 24576
missed 0
...
</pre>

Note that <code>dirty</code> is not the size of dirty data at the moment, but the size of dirty data seen so far.

=== Debugging information ===
When <code>CONFIG_UBC_DEBUG_IO</code>, is on <code>/proc/bc/ioacct_debug</code> is added. This entry contains a snapshot of current dirty pages with its beancounter in system. For example:
<pre>
# cat /proc/bc/ioacct_debug
Races: io 0 anon 0 clean 0 missed 0
pb page flg cnt mcnt pb_list page_pb mapping ub
f7a4a520 e c17cfc68 Dawl 2 0 00000000 f7a4a521 c3870168 0
f7a15ce0 e c17d034c Dawl 2 0 00000000 f7a15ce1 c3870168 0
f72e4680 e c1083364 Dawl 2 0 00000000 f72e4681 c3870168 0
f72e4800 e c1083388 Dawl 2 0 00000000 f72e4801 c3870168 0
f7a15dc0 e c17d0010 Dawl 2 0 00000000 f7a15dc1 c3870168 0
</pre>

== Auxiliary information ==
Along with VFS I/O activity the following information is gathered
; sync counts
: The number of <code>sync(2)</code>, <code>fsync(2)</code>, <code>fdatasync(2)</code> and <code>sync_file_range</code>.
<pre>
# cat /proc/bc/101/ioacct
...
syncs_total 0
fsyncs_total 0
fdatasyncs_total 10
range_syncs_total 0
syncs_active 0
fsyncs_active 0
fdatasyncs_active 0
range_syncs_active 0
</pre>
<code>_active</code> suffix refers to the number of operations in progress.

; write/read calls counts
: The number of <code>read(2)</code>, <code>readv(2)</code>, <code>write(2)</code>, <code>writev(2)</code>, etc. and the number of bytes passed.
<pre>
# cat /proc/bc/101/ioacct
...
vfs_reads 24491
vfs_read_chars 2616512
vfs_writes 380
vfs_write_chars 30064899102
</pre>

; number of page beancounters pinned by I/O
: This is the number of page beancounters that save information about page dirtier. This is actually the number of dirty pages within beancounter at the moment.
<pre>
# cat /proc/bc/0/ioacct
...
write 598016
dirty 622592
...
io_pbs 0
# dd if=/dev/zero of=tmp bs=512 count=40
# cat /proc/bc/0/ioacct
...
write 598016
dirty 643072
...
io_pbs 5
# sync
# cat /proc/bc/0/ioacct
...
write 618496
dirty 643072
...
io_pbs 0
</pre>

[[Category:Resource management]]

IO accounting

2008-05-25T11:40:48Z

Fayette: /* New resources */

This page describes how accounting is done for I/O activity of VE processes. This feature is available beginning with OpenVZ kernels version <code>028test008</code>.

== New resources ==
The following resources are accounted:
; read bytes
: is the number of bytes read by tasks. Reads are always synchronous in the kernel so this type of resource is the easiest one.

; dirty bytes
: is the number of bytes that were dirty since VE start, i. e. data that isn't yet flushed to disk. This type of resource is accumulated using [[RSS_fractions_accounting|page beancounters]] and the context the page was dirtied by is determined like this:
:* if a page is mapped it's "mapper" is used as this may happen in any context (unmapping of a page under memory pressure);
:* if a page is not mapped — current BC is used as this can happen during usual write (writev) only.

; written bytes
: is the number of bytes flushed to disk. The beancounter charged with this is the one by which the page was dirtied.

; canceled bytes
: is the number of bytes that were dirty but weren't flushed to disk.

; missed bytes
: is the number of bytes that were dirtied but the context (beancounter) wasn't saved due to lack of memory.

== Proc interface ==
=== General information ===
As it was described in [[BC proc entries|another article]] each beancounter has it's own <code>/proc/bc/$BCID</code> directory where subsystems add their entries. I/O accounting adds <code>ioacct</code> entry to show I/O information. This entry contains the following information:
<pre>
# cat /proc/bc/101/ioacct
read 24330240
write 598016
dirty 622592
cancel 24576
missed 0
...
</pre>

Note that <code>dirty</code> is not the size of a dirty data at the moment, but the size of a dirty data seen so far.

=== Debugging information ===
When <code>CONFIG_UBC_DEBUG_IO</code>, is on <code>/proc/bc/ioacct_debug</code> is added. This entry contains a snapshot of current dirty pages with its beancounter in system. For example:
<pre>
# cat /proc/bc/ioacct_debug
Races: io 0 anon 0 clean 0 missed 0
pb page flg cnt mcnt pb_list page_pb mapping ub
f7a4a520 e c17cfc68 Dawl 2 0 00000000 f7a4a521 c3870168 0
f7a15ce0 e c17d034c Dawl 2 0 00000000 f7a15ce1 c3870168 0
f72e4680 e c1083364 Dawl 2 0 00000000 f72e4681 c3870168 0
f72e4800 e c1083388 Dawl 2 0 00000000 f72e4801 c3870168 0
f7a15dc0 e c17d0010 Dawl 2 0 00000000 f7a15dc1 c3870168 0
</pre>

== Auxiliary information ==
Along with VFS I/O activity the following information is gathered
; sync counts
: The number of <code>sync(2)</code>, <code>fsync(2)</code>, <code>fdatasync(2)</code> and <code>sync_file_range</code>.
<pre>
# cat /proc/bc/101/ioacct
...
syncs_total 0
fsyncs_total 0
fdatasyncs_total 10
range_syncs_total 0
syncs_active 0
fsyncs_active 0
fdatasyncs_active 0
range_syncs_active 0
</pre>
<code>_active</code> suffix refers to the number of operations in progress.

; write/read calls counts
: The number of <code>read(2)</code>, <code>readv(2)</code>, <code>write(2)</code>, <code>writev(2)</code>, etc. and the number of bytes passed.
<pre>
# cat /proc/bc/101/ioacct
...
vfs_reads 24491
vfs_read_chars 2616512
vfs_writes 380
vfs_write_chars 30064899102
</pre>

; number of page beancounters pinned by I/O
: This is the number of page beancounters that save information about page dirtier. This is actually the number of dirty pages within beancounter at the moment.
<pre>
# cat /proc/bc/0/ioacct
...
write 598016
dirty 622592
...
io_pbs 0
# dd if=/dev/zero of=tmp bs=512 count=40
# cat /proc/bc/0/ioacct
...
write 598016
dirty 643072
...
io_pbs 5
# sync
# cat /proc/bc/0/ioacct
...
write 618496
dirty 643072
...
io_pbs 0
</pre>

[[Category:Resource management]]

IO accounting

2008-05-25T11:34:14Z

Fayette:

This page describes how accounting is done for I/O activity of VE processes. This feature is available beginning with OpenVZ kernels version <code>028test008</code>.

== New resources ==
The following resources are accounted:
; read bytes
: is the amount of bytes read by tasks. Reads are always synchronous in kernel so this type of resources is the easiest one.

; dirty bytes
: is the amount of bytes that were dirty since VE start, i. e. data that isn't yet flushed to disk. This type of resources is accounted using [[RSS_fractions_accounting|page beancounters]] and the context the page was dirtied by is determined like this:
:* if a page is mapped it's "mapper" is used as this may happen in any context (unmapping of a page under memory pressure);
:* if a page is not mapped — current BC is used as this can happen during usual write (writev) only.

; written bytes
: is the amount of bytes flushed to disk. The beancounter to charge this to is the one the page was dirtied by.

; canceled bytes
: is the amount of bytes that were dirty but weren't flushed to disk.

; missed bytes
: is the amount of bytes that were dirtied but the context (beancounter) wasn't saved due to lack of memory.

== Proc interface ==
=== General information ===
As it was described in [[BC proc entries|another article]] each beancounter has it's own <code>/proc/bc/$BCID</code> directory where subsystems add their entries. I/O accounting adds <code>ioacct</code> entry to show I/O information. This entry contains the following information:
<pre>
# cat /proc/bc/101/ioacct
read 24330240
write 598016
dirty 622592
cancel 24576
missed 0
...
</pre>

Note that <code>dirty</code> is not the size of a dirty data at the moment, but the size of a dirty data seen so far.

=== Debugging information ===
When <code>CONFIG_UBC_DEBUG_IO</code>, is on <code>/proc/bc/ioacct_debug</code> is added. This entry contains a snapshot of current dirty pages with its beancounter in system. For example:
<pre>
# cat /proc/bc/ioacct_debug
Races: io 0 anon 0 clean 0 missed 0
pb page flg cnt mcnt pb_list page_pb mapping ub
f7a4a520 e c17cfc68 Dawl 2 0 00000000 f7a4a521 c3870168 0
f7a15ce0 e c17d034c Dawl 2 0 00000000 f7a15ce1 c3870168 0
f72e4680 e c1083364 Dawl 2 0 00000000 f72e4681 c3870168 0
f72e4800 e c1083388 Dawl 2 0 00000000 f72e4801 c3870168 0
f7a15dc0 e c17d0010 Dawl 2 0 00000000 f7a15dc1 c3870168 0
</pre>

== Auxiliary information ==
Along with VFS I/O activity the following information is gathered
; sync counts
: The number of <code>sync(2)</code>, <code>fsync(2)</code>, <code>fdatasync(2)</code> and <code>sync_file_range</code>.
<pre>
# cat /proc/bc/101/ioacct
...
syncs_total 0
fsyncs_total 0
fdatasyncs_total 10
range_syncs_total 0
syncs_active 0
fsyncs_active 0
fdatasyncs_active 0
range_syncs_active 0
</pre>
<code>_active</code> suffix refers to the number of operations in progress.

; write/read calls counts
: The number of <code>read(2)</code>, <code>readv(2)</code>, <code>write(2)</code>, <code>writev(2)</code>, etc. and the number of bytes passed.
<pre>
# cat /proc/bc/101/ioacct
...
vfs_reads 24491
vfs_read_chars 2616512
vfs_writes 380
vfs_write_chars 30064899102
</pre>

; number of page beancounters pinned by I/O
: This is the number of page beancounters that save information about page dirtier. This is actually the number of dirty pages within beancounter at the moment.
<pre>
# cat /proc/bc/0/ioacct
...
write 598016
dirty 622592
...
io_pbs 0
# dd if=/dev/zero of=tmp bs=512 count=40
# cat /proc/bc/0/ioacct
...
write 598016
dirty 643072
...
io_pbs 5
# sync
# cat /proc/bc/0/ioacct
...
write 618496
dirty 643072
...
io_pbs 0
</pre>

[[Category:Resource management]]

Live CD

2008-05-25T11:31:51Z

Fayette:

OpenVZ live CD is a great way to test drive the technology without needing to install OpenVZ.

* If you want to burn a live CD, see [[Download live CD]].

* If you have OpenVZ live CD already, see [[Getting started with OpenVZ live CD]].

* If you want to create your own OpenVZ live CD, see [[Creating OpenVZ LiveCD]] and/or [[Creating OpenVZ LiveCD based on Centos 4.4]].

[[Category: Live CD]]

Bridge doesn't forward packets

2008-05-25T11:30:27Z

Fayette:

Sometimes a bridge can mysteriously drop packets and not forward them.
e.g. eyck user experienced a problem when some of the broadcasts were not
delivered to container via the bridge.

Original report and the thread: [http://forum.openvz.org/index.php?t=tree&th=4052& forum thread]

== Simplest configuration ==

Container #101 with veth interface (veth101.0) connected to eth0 physical interface via bridge.

== Problem statement ==

We faced a situation when some of the broadcast packets were not delivered to
the container. Actually it could happen with any packets, not with the
broadcasts only. But broadcasts are simpler and obviously should have been
delivered to all the networking interfaces with no doubt.

Using tcpdump we see that BOOTP/DHCP request is visible on br0 interface in
the host system ([[CT0]]):
15:21:52.258220 00:1b:d5:2c:bf:38 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 350: 0.0.0.0.68 > 255.255.255.255.67:
BOOTP/DHCP, Request from 00:1b:d5:2c:bf:38, length 308
15:21:52.287269 00:08:02:ac:36:20 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 172.17.8.254.67 > 255.255.255.255.68:
BOOTP/DHCP, Reply, length 300

However, eth0 inside the container received only 2nd packet with a BOOTP/DHCP reply and doesn't see the 1st one with the request itself:
15:21:52.291145 00:08:02:ac:36:20 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 172.17.8.254.67 > 255.255.255.255.68:
BOOTP/DHCP, Reply, length 300

== Resolution ==

It is not obvious at all, but bridges (though they have their own ebtables filters) do also call iptables FORWARD chain when forwarding packets between interfaces.
Thus your FORWARD iptables rules should allow all the packets which are supposed to go through.

in our case eyck had a default DROP policy on FORWARD and had to add:
iptables -A FORWARD -d 255.255.255.255 -j ACCEPT
to fix the issue.

== Credits ==
Many credits to Dariush Pietrzak, who patiently helped to debug this.

[[Category:Troubleshooting]]
[[Category:Networking]]