On 09/09/15 18:03, Wei Liu wrote:
This is due to migration v2 frame record doesn't contain node information.
This isn't a migration v2 bug, and it was similarly non-functional with legacy migration. It was yet another oversight with the vNUMA work.
Isn't this information available in the domain configuration for the domain sent in the xl header? (That layer violation also need removing).
Finally, your phrasing is somewhat unclear. I would recommend "The migration stream does not preserve node information" as a clearer alternative.
~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
