Job Placements for ZeBu Emulators

By default, running vovemulmgr config creates resource maps that allow an emulation job to run on any valid Zebu placement.

On large Zebu emulators (for example, one with 16 units), there are many valid placements, and configuration may take a long time to complete, or can possibly cause the vovserver to run out of memory.

This is only an issue for jobs that require more than one unit.

These issues can be mitigated by reducing the number of legal placements generated by specifying the CONNECTIVTY entry in the relevant emulator specific section of the emul.cfg configuration file. The CONNECTIVTY option can take the following values which represent a trade off between configuration time and allowable placements:
  • combinations (default): Generate all valid Zebu placements.
  • extended: Generate a subset of the placements generated using the "combinations" value using a grouping heuristic to reduce the number of placements generated. This has the most impact for jobs that require approximately half of the number of emulator units.
  • explicit <comma separated list of targets>: Generate placements for the specified targets. For example, CONNECTIVITY = "explicit:SPAN1,SPAN25" will only generate placements for the SPAN1 and SPAN25 targets.
  • sequential: Generate placements only where the placement units are sequential.