I am concerned because Intel doesn't and eVMCS is based on VMCS, somaybe they are going to use the live migration notifier to disable eVMCSon incompatible versions. TLFS points that they plan to handle eVMCSversions the same as Intel, but the spec might just be misleading.

> So currently we check that L0 supports at least ver1 (or some newer> version which implies all previously released versions are supported> too) and we declare that KVM supports ver1 exactly (this is the format> of the structure we put to memory and share with L0). We can't declare> support for any other version.

Yes, I'm saying that we don't proceed with any other version than 1.

> Currently, it is only Ver1 on WS2016.

Right. It should be an easy bug to spot, so I'm ok with the currentversion.