Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1600595

Summary: [downstream clone - 4.2.5] add AMD EPYC SSBD CPU
Product: Red Hat Enterprise Virtualization Manager Reporter: RHV bug bot <rhv-bugzilla-bot>
Component: ovirt-engineAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED ERRATA QA Contact: meital avital <mavital>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.2.5CC: bugs, eedri, ipinto, lsurette, michal.skrivanek, Rhev-m-bugs, srevivo
Target Milestone: ovirt-4.2.5Keywords: Rebase, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of: 1600573 Environment:
Last Closed: 2018-07-31 17:49:18 UTC Type: ---
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: 1600573    
Bug Blocks:    

Description RHV bug bot 2018-07-12 14:49:19 UTC
+++ This bug is a downstream clone. The original bug is: +++
+++   bug 1600573 +++
======================================================================

similar to earlier Intel CPU update this one is for AMD EPYC family. Microcode update not required

+++ This bug was initially created as a clone of Bug #1581144 +++

add SSBD CPUs to the supported list. Requires host support and microcode updates to be effective

(Originally by michal.skrivanek)

Comment 1 RHV bug bot 2018-07-12 14:49:24 UTC
new type + a fix similar to https://gerrit.ovirt.org/#/c/91615

(Originally by michal.skrivanek)

Comment 3 RHV bug bot 2018-07-12 14:49:28 UTC
(In reply to Michal Skrivanek from comment #1)
> new type + a fix similar to https://gerrit.ovirt.org/#/c/91615

actually, AMD EPYC was new in 4.2 GA and changed there already to use +ibpb instead of -IBPB so just a new type is enough

(Originally by michal.skrivanek)

Comment 4 Michal Skrivanek 2018-07-12 14:52:08 UTC
+ requiring the right rhvm-setup-plugins

Comment 5 Eyal Edri 2018-07-15 13:24:28 UTC
testing jira sync, please ignore.

Comment 7 Israel Pinto 2018-07-17 06:43:28 UTC
Verify with: 4.2.5.1-0.1.el7ev
Build: rhv-release-4.2.5-3-001.noarch

Steps: 
1. Add host with capabilities:
# virsh -r domcapabilities | grep EPYC
      <model fallback='forbid'>EPYC-IBPB</model>
      <model usable='yes'>EPYC</model>
      <model usable='yes'>EPYC-IBPB</model>
  To cluster AMD EPYC IBPB
2. Start VM on host
VM started and host added 

PASS

Comment 8 Israel Pinto 2018-07-24 09:11:12 UTC
(In reply to Israel Pinto from comment #7)
> Verify with: 4.2.5.1-0.1.el7ev
> Build: rhv-release-4.2.5-3-001.noarch
> 
> Steps: 
> 1. Add host with capabilities:
> # virsh -r domcapabilities | grep EPYC
>       <model fallback='forbid'>EPYC-IBPB</model>
>       <model usable='yes'>EPYC</model>
>       <model usable='yes'>EPYC-IBPB</model>
>   To cluster AMD EPYC IBPB
> 2. Start VM on host
> VM started and host added 
> 
> PASS

Verify with:
Engine: 4.2.5.2_SNAPSHOT-83.g4210c43.0.scratch.master.el7ev
Host: 
OS Version:RHEL - 7.5 - 8.el7
Kernel Version:3.10.0 - 862.6.3.el7.x86_64
KVM Version:2.10.0 - 21.el7_5.4
LIBVIRT Version:libvirt-3.9.0-14.el7_5.6
VDSM Version:vdsm-4.20.34-1.el7ev
SPICE Version:0.14.0 - 2.el7_5.4 
CPU model: AMD EPYC 7251 8-Core Processor
microcode version: microcode_ctl-2.1-29.3.el7_5.x86_64

Steps:
1. Add host to cluster: AMD EPYC IBPB SSBD
2. Check host domcapabilities for ssbd:
   # virsh -r domcapabilities |  grep -i ssbd
      <feature policy='require' name='virt-ssbd'/>
3. Start VM and check guest cpu type: 
   EPYC,+ibpb,+virt-ssbd

PASS

Comment 9 RHV bug bot 2018-07-24 12:26:42 UTC
INFO: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[Project 'vdsm'/Component 'ovirt-engine' mismatch]

For more info please contact: rhv-devops

Comment 11 errata-xmlrpc 2018-07-31 17:49:18 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2018:2318