Goal

Currently there is no way to express that the qemu emulator thread should be pinned without also specifying that it should be dedicated. This requires extra dedicated CPU resources that don't always make sense.

User Stories

• As a workload owner, I would like the ability to specify that the qemu emulator thread should be pinned, without requiring the thread to be on distinct CPUs from other pinned threads.

Non-Requirements

• List of things not included in this epic, to alleviate any doubt raised during the grooming process.

Notes

• Any additional details or decisions made/needed