On Tue, Sep 08, 2015 at 03:39:53PM +0100, Ian Jackson wrote:
> Wei Liu writes ("[PATCH for 4.6 2/2] xl/libxl: disallow restoring guest with
> vNUMA configured"):
> > This is due to restoring a guest uses another path different from the
> > creation path and migration v2 frame record doesn't contai
Wei Liu writes ("[PATCH for 4.6 2/2] xl/libxl: disallow restoring guest with
vNUMA configured"):
> This is due to restoring a guest uses another path different from the
> creation path and migration v2 frame record doesn't contain node
> information.
The effect of this would be that you could do
This is due to restoring a guest uses another path different from the
creation path and migration v2 frame record doesn't contain node
information.
Signed-off-by: Wei Liu
---
Cc: andrew.coop...@citrix.com
I don't think this is specific to migration v2. Legacy migration suffers
from the same issu
