On Fri, Apr 27, 2018 at 10:34 AM, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote: > Or am I silly b/c you wouldn't be able to migrate in the first place > as the savevm/restorevm does not do any VMX states so it would crash > anyhow? > > If so, perhaps the commit should be amended to say this? That you can't > do migration until the new IOCTLs are added for the VMX states? AFAIK, Google is the only user of kvm that is curently doing save/restore of nested vCPU state, and we ran into this issue as we started our latest rebase. I'd therefore like to get this structure stabilized before the save/restore nested state IOCTLs are committed upstream, so that we're all playing on the same field. I'll amend the commit message.
