diff options
| author | Vitaly Kuznetsov <vkuznets@redhat.com> | 2021-06-08 14:08:11 +0200 |
|---|---|---|
| committer | Eduardo Habkost <ehabkost@redhat.com> | 2021-07-13 09:13:29 -0400 |
| commit | 07454e2ea84ee9be298c96d9730dc82abfb1488a (patch) | |
| tree | cf814d65b00d97bea5c477c5eee28569b75e381e /scripts | |
| parent | 00c1b316edb33f2efb0775c2983bc5348c86529d (diff) | |
| download | qemu-07454e2ea84ee9be298c96d9730dc82abfb1488a.zip qemu-07454e2ea84ee9be298c96d9730dc82abfb1488a.tar.gz qemu-07454e2ea84ee9be298c96d9730dc82abfb1488a.tar.bz2 | |
i386: hardcode supported eVMCS version to '1'
Currently, the only eVMCS version, supported by KVM (and described in TLFS)
is '1'. When Enlightened VMCS feature is enabled, QEMU takes the supported
eVMCS version range (from KVM_CAP_HYPERV_ENLIGHTENED_VMCS enablement) and
puts it to guest visible CPUIDs. When (and if) eVMCS ver.2 appears a
problem on migration is expected: it doesn't seem to be possible to migrate
from a host supporting eVMCS ver.2 to a host, which only support eVMCS
ver.1.
Hardcode eVMCS ver.1 as the result of 'hv-evmcs' enablement for now. Newer
eVMCS versions will have to have their own enablement options (e.g.
'hv-evmcs=2').
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
Message-Id: <20210608120817.1325125-4-vkuznets@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions