Perhaps I am misunderstanding, but I don't see how nested SVM instances
can be properly migrated. How does one extract and rebuild the nested
hsave control block?
If it isn't done already, one possible way to add it as an extension
might be to represent the data as additional MSRs which are saved and
restored with migration.
Actually, looking deeper, there doesn't even appear to be any way to
export the nested CPU data at all, meaning basic features like
suspending and restoring the VM are not possible. Is there any plan to
make it work in the near future? I'm not complaining; if my
understanding is correct, this actually makes my current task easier.
Thanks,
Zach
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
