Comment 1 for bug 1829349

Just to make sure I'm following, since we don't claim resources in the resource tracker (yet) for NUMA during live migration on the dest host, both VMs landed there and are running there but with conflicting pinned CPUs and that's what causes the update_available_resource periodic task on the destination compute host to fail, until one of those VMs is deleted or migrated elsewhere, is that correct?