This is intended to work in a host with Centos-4 (tested) or a , Centos-5, Fedora Core 5, Fedora Core distribution (not tested)6, RHEL 4 or any other RPM based system with python 2.2, 2.3 or 2.4 version. 

Vzyum, vzpkgcache and vzrpm are broken in 64 bit systems, so we are unable to create new cache templates in a x86_64 computer or update each VE [[container]] using vzyum or vzrpm.

* - A host with x86_64 Centos-4 distribution (or , Fedora Core or RHEL, or other Redhat based systems with python 2.2, 2.3, or 2.4 or version (vzrpm is unable to run with python 2.5 - not testedversion).

* The yum cache is not common to all VE'[[container]]s. Instead, each VE [[container]] has it's its own yum cache in the directory <code>/var/cache/yum-cache</code>.

* You can only use the automatic install IF YOU HAVE <b>YUM </b> AND <b>RPM </b> PACKAGES INSTALLED IN YOUR SYSTEM, and if you want to install a Centos-4 cache template.* This process uses a bash script that automatizes which automates all the hard work made by hand in the manual install. It was successfully tested in several systems.* If something goes wrong, or if you want to understand the way it works to install a diferent cache templatedistribution, it's better to do the manual install, and try to adapt it to your needs.

* Download the file [http://linux.carreira.com.pt/ovzutils/setx86_64-0.26.tar.gz setx86_64-0.6] and then untar and run the script:

tar xzvf setx86_64-0.6.tar.gz./sh setx86_64

When it finishes Press Enter and some tests are made to know if you can go on with the message "END INSTALL", installation.If you can choose to go on reading this document jumping to with it, the script will download and patch everything for you.All the undermentioned <b>[[#STEP_10|STEP 10]]</b>vztemplates metadata available in openvz.org site are also installed and fixed for x86_64 system.

When it finishes with the message "END INSTALL", you can go on reading this document jumping to the undermentioned <b>Note:[[#STEP_11|STEP 11]]</b> This script will almost work for CentOS-5, however it's not quite right (you will get some errors). You will also need to:<pre>rm /usr/share/vzpkgtools/vzrpm43/lib/python2.4/site-packages/rpmmodule.so</pre>which will cause it to resolve a dependency using your system wide python implementation

We can't "yum install vzyum" because it breaks with an error:<br><b>Error: Missing Dependency: cElementTree.so is needed by package vzyum</b>

yum install vztmpl-centos-4 vzpkg*

The example is using <b>Centos-4</b> distribution (tested), but <b>Fedore CoreFedora</b> or other distribution with yum , rpm and rpm python (version 2.2, 2.3 or 2.4) installed, may be tried, if you . You only have to change the reference name and version in STEPS 1 to 4 (this was not tested).

If you didn't instal yet Install "vztmpl-centos-4", do it now:

mkdir x86_64 cp -a /vz/template/centos/4/i386/* /vz/template/centos/4/x86_64

Now we have a x86_64 centos template installed.<br>You can do the same procedure to other distro templates.

:<code>cachedir=/vz/template/centos/4/x86_64/yum-cache</code>

:to :<code>cachedir=/var/cache/yum-cache</code>

{{Note| <codeb>cachedir=1)</b> With these changes, vzyum won´t be able to use a common cache directory to all [[container]]s as it used to do. Each [[container]] will have its own cache directory.To avoid to have a directory named /vz/template/centos/4/x86_64/yum-cache in each [[container]], it is preferable to use the correct cache directory /var/cache/yum-cache</code>.

{{Note| With this changes, vzyum is not going to be able to use <b>2)</b> To set up a common cache directory to all VE's as it was used to do. Each VE will have it's own cache directory.To avoid to have a directory named /vz/template/centos/4/x86_64/yum-cache in each VE, it is preferable to you can use the correct cache directory autofs/varautomounter daemon together with [[Bind_mounts]] as described in <b>step 12</b>. Using a shared cache/yum-cachemay save a lot of network traffic when installing new VPSs.}}

 ===== STEP 5 6 =====

Substitute 32 bit module "In Centos-4 version python is 2.3. So, we must replace rpmmodule.so" from vzrpm43-python to the 64 bit module that rpm-python-x86_64 provides, using this method:.

For CentOS-5In other Operating Systems or other versions, you will need must verify which python version is installed in the host system. Depending on that, the 32 bit files to do something a bit be replaced are different. rpmmodule.so is provided in your sitewide python distribution(read the setx86_64 script, so instead of copying it acrossline 334 to line 358, you need to:understand how it is done).

  <blockquote style="background: white; border: 1px solid rgb(153, 153, 153); padding: 1em;"><b>Note:</b><br>Someone reported the note below, but the tests I made, <u>didn't confirm<pre/u> it was really needed. Everything worked flawless without it.<br>Nevertheless, if you find some problems, try the workaround described below:<br><br> <i>For CentOS-5, you will need to do something a bit different. "rpmmodule.so" is provided in your sitewide python distribution, so instead of copying it across, you need to::rm /usr/share/vzpkgtools/vzrpm43/lib/python2.4/site-packages/rpmmodule.so</prei></blockquote>

===== STEP 6 7 =====

Edit the file /usr/share/vzpkg/<b>cache-os</b><br>

===== STEP 7 8 =====

Edit the file /usr/share/vzpkg/<b>functions</b><br>

===== STEP 8 9 =====

Edit the file /usr/bin/<b>vzyum</b><br>

The next piece of code fixed the vzyum bug described in [http://bugzilla.openvz.org/show_bug.cgi?id=488#c0 bugzilla #488].<br>It was impossible to install a package group with spaces in his name.<br>Now we can use e.g. <b>vzyum groupinstall \"GNOME Desktop Environment\"</b>, or other group name listed in vzyum grouplist.<br>(Don't forget the backslash before each doublequote) <b> -Line 56:</b><pre>comment the line 56:#exec $YUM $YUM_ARGS $USER_ARGS</pre> <b> -Last Line (57):</b><br> <pre>add this code: TMPVZY=/tmp/tmpvzy.$$echo $YUM $YUM_ARGS $USER_ARGS > $TMPVZYsh $TMPVZYexec rm -f $TMPVZY</pre>  ===== STEP 9 10 =====

Change the next line:

===== STEP 10 11 =====

If you want your VE'[[container]]s to have other country locales

Now you can create your own cache template caches from your own cache templates.

Make my first two cache List all x86_64 templatesavailable:

They finish It finishes with complaints about <i>cron.daily</i>, but don't worry about it.Now <b>minimal</b> and <b>default</b> cache are is created. Confirm if they are were created: 

If you see it in the cache list, then you can create your first VE[[container]]: 

Now start VE 20 [[container]] 200 previously created:

Try to use vzrpm, to list all rpm's installed in VE200[[container]] 200: