We will make the template from a stage3 file. An OpenVZ OS template should be an archive (.tar.gz) of the root of a working system, but without the kernel and some files. You can download stage3 from the nearest mirror here: from http://www.gentoo.org/main/en/mirrors.xml.or here [directly from http://distfiles.gentoo.org/releases/x86/current-stage3/]

---- == Or try to Download 64 bit stage3 == If you experience with 32bit containers you can also try to create Gentoo template with 64bits binary support. Try to download '''64bit''' stage3. For 64bit Gentoo template creation, search for nearest mirrors http://www.gentoo.org/main/en/mirrors.xml or directly from: http://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3/ with 32bit binary '''multilib''' support, or  http://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3/hardened/ (stage3-amd64-hardened+nomultilib-20xxxxxx.tar.bz2) try the hardend profile without multilib support (only 64bit binary support for gentoo template containers!!)  Don't forget that hostnode must support 64bit binary too, with or without 32bit multilib support!! Hostnodes that supports multilib can start 64bits containers with 32bits containers but with a '''''slight''''' performance degradation. Don't forget to look for:<pre>ACCEPT_KEYWORDS="amd64" in /etc/make.conf</pre> there you can accept 64bit binary packages support for your containers.<pre>cat /proc/cpuinfo</pre> for 64 bits Intel\AMD CPU instructions set support.  '''WARNING''': There is no warrantied that template should work, you can bugtack the errors. But I haven't confronted with problem. == Create directory directories for the new container and unarchive stage3 ==

tar -xjf xvjpf /root/stage3-i686-20111213.tar.bz2 -C /vz/private/1001

Gentoo users wil see warning, but nothing to wary worry just ignore it

Add the following First, you need to <code>/etc/vz/conf/1001.conf</code>let vzctl know that this CT is using Gentoo:<pre> echo 'OSTEMPLATE="gentoo"' >>/etc/vz/conf/1001.conf</pre>

values are providing 2 GiByte GB soft limit with 2.5 GiByte GB hard limit:<pre> DISKSPACE="20971522.4G:2.5G" If you use independed Gentoo portage tree for each container, is considered correct in the use of gentoo containers, don't forget to raise inodes number  DISKINODES="400000:2621440420000"</pre>You should also increase the ram to a minimum of 512 MB. Otherwise, you will get errors during compilation. Since vzctl 3.0.30 you can do:  vzctl set 1001 --ram 512M --swap 1G --save Prior to vzctl 3.0.30 you have to do, which gives you 512 MB guaranteed and 1024 MB burstable:  vzctl set 1001 --vmguarpages 512M --save vzctl set 1001 --oomguarpages 512M --save vzctl set 1001 --privvmpages 512M:1024M --save vzctl set 1001 --swappages 0:1024M --save

But if you using Independed Gentoo 11portage tree for each container would be good idea, because newer portage can delete older ebuilds already installed in container with other dependences.2 release and future Otherwise you can skip 't reinstall already installed packages if you bind the increasing the disk space limits, by deafult you have 2 GiByte soft limit and 2.3 GiByte hard limitnewer version of portage in gentoo containers.

<pre> # cp /etc/vz/conf/1001.conf /etc/vz/conf/ve-gentoo.conf-sample</pre>

Gentoo 11.2 release have an option in /vz/private/1001/etc/'''rc.conf'''

Get latest snapshot of portage tree from your favourite mirror (http://www.gentoo.org/main/en/mirrors.xml) and extract it into <code>/vz/private/7771001/usr</code>:

# wget <your-mirro>http://distfiles.gentoo.org/releases/snapshots/current/portage-latest.tar.bz2# tar xjf portage-latest.tar.bz2 -C /vz/private/7771001/usr

Add the following strings to the <code>/vz/private/7771001/etc/make.conf</code>:

You should update host-node portage tree on regular basis to keep it up to date because <code>emerge --sync</code> won't work inside guest container.

cd /vz/private/7771001/