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. Most of the dependencies are trivial and should be fulfilled by default, but there may be exceptions:
 ip 
command is required for bridged networkingAs the last three should be trivial, the iptools package is may be a challenging dependency (especially at *BSD). However, for advanced functionality it is required to have available:
Through the documentation we use some terms:
We use special terms for directory names, because the real locations differs depending on the used layout at build time. The term vardir (or VARDIR) refers to the var directory (for “variable” data). On Linux systems this is usually “/var”, perhaps with a suffix for a sub directory like “/var/qemud”. Similar terms are etcdir, libdir, rundir and others (see directories).
qemu-init requires one dedicated user and group (each). As this is configurable at build time we refer to it with the terms SYSUSR and SYSGRP.
The terms root user or root privileges refers to the user with uid 0 always.
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  -name 
(default)!
These abbreviations are used for some files further (see here):
 <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!