Discrepancies of the definitions and conventions below will may be work, but are not supported!
qemu-init is designed with the following basics (requirements):
For the virtual machines itself qemu-init is designed
qemu-init is designed to have less dependencies as possible. The package comes with all required tools, except
ip command is required for bridged networking
bash , other shells may work too)
As the last two should be trivial, the iptools package is the only real dependency (especially at *BSD).
Through the documentation we use some terms:
Each virtual machine MUST have a unique identifier. The term <name> (with angle brackets) will be used as synonym of the unique identifier. The <name> is used to define which files belongs to one dedicated virtual machine. The <name> MUST
Recommended “best practice”: Use “<name>” as hostname (short, w/o domain) of the guest and as well as parameter of the qemu option
Each guest uses (could use) several config files (see Config files). All file which belongs to one guest starts with the <name> (in lower case letters) of the guest.
<name>-qemud.rc , default configuration file (required).
<name>-qemu.cfg , the file for extended qemu user configuration (optional).
Attention! qemu-init is the project name, qemud-init is a library!