diff options
| author | Vitaly Kuznetsov <vkuznets@redhat.com> | 2021-04-12 09:39:52 +0200 |
|---|---|---|
| committer | Eduardo Habkost <ehabkost@redhat.com> | 2021-05-31 15:53:02 -0400 |
| commit | 7bde6b18575dd79c26ce1616e0c33151e83d9d7e (patch) | |
| tree | ba1fbf7da6999835983f41cb76cc089edc6a6940 /hw/virtio/virtio-input-host-pci.c | |
| parent | 52848929b70dcf92a68aedcfd90207be81ba3274 (diff) | |
| download | qemu-7bde6b18575dd79c26ce1616e0c33151e83d9d7e.zip qemu-7bde6b18575dd79c26ce1616e0c33151e83d9d7e.tar.gz qemu-7bde6b18575dd79c26ce1616e0c33151e83d9d7e.tar.bz2 | |
target/i386: Add CPU model versions supporting 'xsaves'
Hyper-V 2016 refuses to boot on Skylake+ CPU models because they lack
'xsaves'/'vmx-xsaves' features and this diverges from real hardware. The
same issue emerges with AMD "EPYC" CPU model prior to version 3 which got
'xsaves' added. EPYC-Rome/EPYC-Milan CPU models have 'xsaves' enabled from
the very beginning so the comment blaming KVM to explain why other CPUs
lack 'xsaves' is likely outdated.
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Message-Id: <20210412073952.860944-1-vkuznets@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Diffstat (limited to 'hw/virtio/virtio-input-host-pci.c')
0 files changed, 0 insertions, 0 deletions