OpenVZ is a neat piece of software, but sometimes there are confusing things that make it frustrating to use.  This is a collection of guidelines/tips for installing openvz on Fedora Core 5, with a lot of the common some gotchas covered.

You should be using the OpenVZ development branch of kernels with FC5. The kernels have <code>test </code> in their name. Go to your [[yum ]] repo configuration and make sure that the development repo is enabled , or do the following.:

Note: Do not install the FC5 openvz kernel on the website, it is outdated if you have an up to date FC5 install.

== Fix metadata Creating your own templates ==

After installing If you are trying to tar up a vps to use as a template, make sure you tar up the metadataINSIDE of the vps, run and do not include the vpsid at the followingbeginning (ie /101/). <pre> tar --numeric-owner -zcf /vz/template/cache/fedora-core-5-i386-minimal-mine.tar.gz -C /vz/private/101/ .</pre>

<pre> INFILE=If you create a ve from one of your own templates, you should edit veid.conf in /etc/vz/template/conf to set the OSTEMPLATE variable back to fedora-core/-5/i386/config/default.list if [ ! -e $INFILE.orig ] then cp $INFILE $INFILEThis will insure that vzyum etc continue to work.orig fi sed 's/caching-nameserver/bind-config/' $INFILEOtherwise openvz may not find the metadata for your machine.orig > $INFILE </pre>

== Creating your own templates Yum differences == OpenVZ creates an entirely new yum.conf as part of the meta-data for a distribution. For FC5 this is in '/vz/template/fedora-core/5/i386/config/yum.conf'. If you have a local repository mirror of FC5 this means openvz will seem very slow unless you update this new openvz yum.conf to match your normal system yum.conf.  Additionally vzyum doesn't seem to pick up $releasever in yum files. I haven't figured that one out yet, and havn't rechecked.