On 16/08/21 16:23, Daniel P. Berrangé wrote:
snip
With this implementation, the number of mirror vCPUs does not even have to
be indicated on the command line. The VM and its vCPUs can simply be
created when migration starts. In the SEV-ES case, the guest can even
provide the VMSA that starts the migration helper.
I don't think management apps will accept that approach when pinning
guests. They will want control over how many extra vCPU threads are
created, what host pCPUs they are pinned to, and what schedular
policies might be applied to them.
That doesn't require creating the migration threads at startup, or
making them vCPU threads, does it?
The migration helper is guest code that is run within the context of the
migration helper in order to decrypt/re-encrypt the code (using a
different tweak that is based on e.g. the ram_addr_t rather than the
HPA). How does libvirt pin migration thread(s) currently?
Paolo
