Cross-Numa Hammerdb always runs to only one NUMA node

When I do the SQL Server performance test on a virtual machine with a large size (16U + 16U) across a NUMA node, I find that Hammerdb always uses only one NUMA node's CPU resources:

Here is the test scenario:

16U64G Windows Server R2 64bit

SQL Server 2008R2 WEB

Use HAMMERDB to open 101 concurrent connections:

Create a trace that records only audit login and audit logout

SPID:53 has been audit Login,audit logout

101 spid created from spid:54 to spid:154

Subsequent additions to the spid:54-spid154 associated with the NUMA Node ID show that the 101 spid with no audit logout is dispatched by the CPU resources of the NUMA nodes

Cross-Numa Hammerdb always runs to only one NUMA node