6,534
edits
Changes
→Creating your own templates: use --numeric-owner option for tar
== Use development branch ==
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.:
echo '
[openvz-kernel-devel]
gpgkey=http://download.openvz.org/RPM-GPG-Key-OpenVZ
' > /etc/yum.repos.d/openvz-devel.repo
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 == After installing the metadata, run the following <pre> INFILE=/vz/template/fedora-core/5/i386/config/default.list if [ ! -e $INFILE.orig ] then cp $INFILE $INFILE.orig fi </pre> If you have bind-9.3.2-20.FC5 you should run additional command <pre> sed 's/caching-nameserver/bind-config/' $INFILE.orig > $INFILE </pre>
== Creating your own templates ==
<pre>
tar --numeric-owner -zcf /vz/template/cache/fedora-core-5-i386-minimal-mine.tar.gz -C /vz/private/101/ .
</pre>
If you create a ve from one of your own templates, you should edit veid.conf in /etc/vz/conf to set the OSTEMPLATE variable back to fedora-core-5. This will insure that vzyum etc continue to work. Otherwise openvz may not find the metadata for your machine.
== Yum differences ==