Comment 2 for bug 1784462

NOTE: The hw_cpu_thread_policy property is only valid if hw_cpu_policy is set to dedicated. And "hw_cpu_policy" is also not documented in image properties, but is in flavor extra specs:

Valid CPU-POLICY values are:

    shared: (default) The guest vCPUs will be allowed to freely float across host pCPUs, albeit potentially constrained by NUMA policy.
    dedicated: The guest vCPUs will be strictly pinned to a set of host pCPUs. In the absence of an explicit vCPU topology request, the drivers typically expose all vCPUs as sockets with one core and one thread. When strict CPU pinning is in effect the guest CPU topology will be setup to match the topology of the CPUs to which it is pinned. This option implies an overcommit ratio of 1.0. For example, if a two vCPU guest is pinned to a single host core with two threads, then the guest will get a topology of one socket, one core, two threads.