By this point, the subject isn't exactly accurate, but since v 1-6 had it, I'm not changing it now. As the commit message says, this feature is no longer an "auto topology" feature, but instead just a feature to allow users to configure topology for a vm template should they so desire. If we ever want to add an auto-configure option, then version 5 of this patchset can be resurrected. I would recommend re-adding the auto-element of the cpu_info for a template, instead of passing in threads=0, however. New to version 7: A near complete re-write that only does some checking in the backend, adds appropriate error messages, a mockmodel test, and a little tweaking so that the mockmodel tests pass. Christy Perez (2): Parts to allow Kimchi to configure the cpu topology. Mockmodel test for cpuinfo docs/API.md | 24 ++++++++ src/kimchi/control/cpuinfo.py | 37 ++++++++++++ src/kimchi/control/host.py | 2 + src/kimchi/i18n.py | 5 ++ src/kimchi/mockmodel.py | 10 ++++ src/kimchi/model/cpuinfo.py | 128 ++++++++++++++++++++++++++++++++++++++++++ src/kimchi/model/templates.py | 10 ++-- 7 files changed, 212 insertions(+), 4 deletions(-) create mode 100644 src/kimchi/control/cpuinfo.py create mode 100644 src/kimchi/model/cpuinfo.py -- 1.9.3