Xen Template Manager requires very few things to run.
- A Unix shell interpreter
- Have dialog, Xdialog or gdialog installed
- At least one LVM Volume Group with available space
To run Xen Template Manager, go to the directory where extracted the package
were options can be
-X for use with Xdialog
-G for use with Gdialog
Template list file
All the templates that you have created must be declared in the xtm.conf file. Here is
one example of xtm.conf
1,rhas4-32-pvm,"Red Hat AS 4 32bits (pvm)","pvm"
2,rhas4-32-hvm,"Red Hat AS 4 32bits (hvm)","hvm"
9,win2k-hvm,"Windows 2000 Professional","hvm"
10,win2k-sever-hvm,"Windows 2000 Server","hvm"
xtm is a comma separated list, that is composed in the following way:
- first, a sequence number, this number must not be repeated.
- second, a name for the template, this is part of the name of the file that haves
- third, a description contanined between double quotes ` " `.
- fourth, the VM type, it must be either "hvm" o "pvm".
For the time being, the directories are hardcoded (only because I didn't changed it so
far) but this will change very soon and you can change them editing the xenman file.
The locations where XTM expect to find the files are:
this is the directory where the configurations file for the VM will be placed (the ones that
you give as argument to xm create
this is the location and name of the template list, by default is xtm.conf
depredicated, in early versions the templates where stored on LVM2 LV's, I changed that
on behalf of a NFS share
self explanatory, the directory where you store the themplate files
XTM constructs the filename of the template adding "lv-T-" before the name of the template
in the template list file and ".img" after them. For example, a template named "rhas4-32-hmv"
will have a file named "lv-T-rhas4-32-hvm.img"