Bug 1517286

Summary: [RFE] Skylake-server and AMD EPYC support
Product: [oVirt] ovirt-engine Reporter: Michal Skrivanek <michal.skrivanek>
Component: BLL.VirtAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED CURRENTRELEASE QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: unspecified    
Version: futureCC: alexander, bugs, cshao, huzhao, ipinto, marcoc, mavital, mtessun, qiyuan, weiwang, yaniwang, ycui
Target Milestone: ovirt-4.3.0Keywords: FutureFeature
Target Release: 4.3.0Flags: rule-engine: ovirt-4.3+
mavital: testing_plan_complete-
mtessun: planning_ack+
michal.skrivanek: devel_ack+
rule-engine: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.3.0_alpha Doc Type: If docs needed, set a value
Doc Text:
Skylake-server and AMD EPYC processor families are now supported for virtualization
Story Points: ---
Clone Of:
: 1537032 (view as bug list) Environment:
Last Closed: 2019-02-13 07:45:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1501508    
Bug Blocks: 1537032    

Description Michal Skrivanek 2017-11-24 13:51:03 UTC
7.5 adds "Skylake (server)" CPU family (machine type Skylake-server"
We should add it to oVirt, and differentiate from the existing "Skylake" family we have by renaming it to "Skylake (client)"

Comment 1 Michal Skrivanek 2017-11-24 13:59:37 UTC
depends on CentOS 7.5

Comment 3 Michal Skrivanek 2018-01-22 10:17:11 UTC
also AMD EPYC

Comment 5 Israel Pinto 2018-03-19 19:06:36 UTC
- Skylake-Server

Verify with:
Engine Version:4.2.2.4-0.1.el7
Host:
OS Version:RHEL - 7.5 - 8.el7
Kernel Version:3.10.0 - 861.el7.x86_64
KVM Version:2.10.0 - 21.el7_5.1
LIBVIRT Version:libvirt-3.9.0-14.el7
VDSM Version:vdsm-4.20.20-1.el7ev

Host info:
# virsh -r capabilities | head
<capabilities>
  <host>
    <uuid>965ad785-91c5-4d4c-8f4a-fd299017ba2c</uuid>
    <cpu>
      <arch>x86_64</arch>
      <model>Skylake-Server</model>
      <vendor>Intel</vendor>
      <microcode version='33554485'/>
      <topology sockets='1' cores='26' threads='2'/>

Steps:
1. Add Host
2. Run VM on Host

PASS

Comment 7 Michal Skrivanek 2018-03-26 11:48:10 UTC
this is an upstream bug and should not be tested on RHV

Comment 8 meital avital 2018-12-10 08:32:20 UTC
Verified on:
ovirt-engine-4.3.0-0.2.master.20181203100035.git0ee44c1.el7.noarch

kernel-3.10.0-957.el7.x86_64
libvirt-4.5.0-10.el7_6.3.x86_64
qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64
vdsm-4.30.4-2.git9e80801.el7.x86_64
Red Hat Enterprise Linux Server release 7.6 (Maipo)


# virsh -r capabilities | head
<capabilities>

  <host>
    <uuid>86ab5058-8720-4e5d-9e4e-d653168b5070</uuid>
    <cpu>
      <arch>x86_64</arch>
      <model>EPYC-IBPB</model>
      <vendor>AMD</vendor>
      <microcode version='134222375'/>
      <topology sockets='1' cores='6' threads='2'/>


# virsh -r capabilities | head
<capabilities>

  <host>
    <uuid>02b44f1e-edf6-416d-890d-ffe67f14b657</uuid>
    <cpu>
      <arch>x86_64</arch>
      <model>Skylake-Server-IBRS</model>
      <vendor>Intel</vendor>
      <microcode version='33554509'/>
      <topology sockets='1' cores='16' threads='2'/>

Comment 10 Sandro Bonazzola 2019-02-13 07:45:09 UTC
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.