Bug 1559730

Summary:	Allow backward-compatible CPUs on ppc64le
Product:	[oVirt] ovirt-engine	Reporter:	Michal Skrivanek <michal.skrivanek>
Component:	BLL.Virt	Assignee:	Martin Polednik <mpoledni>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Israel Pinto <ipinto>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2.2	CC:	bugs, mavital, mpoledni
Target Milestone:	ovirt-4.2.3	Flags:	rule-engine: ovirt-4.2+ mavital: testing_ack+
Target Release:	4.2.3.2
Hardware:	ppc64le
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.2.3.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-11 06:51:02 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:

Description Michal Skrivanek 2018-03-23 07:18:49 UTC

qemu option "-cpu host,compat=power8" can be used to specify a power8 guest to run on a power9 hardware.

We should apply the Cluster's CPU Type setting

Comment 1 Yaniv Kaul 2018-04-11 10:21:11 UTC

Any idea why it's still on POST? Does it need a backport to 4.2?

Comment 2 Michal Skrivanek 2018-04-11 10:54:24 UTC

yes it does.

Comment 4 Michal Skrivanek 2018-05-09 13:49:21 UTC

this bug is applicable to any supported POWER CPU, so you can verify also on POWER8

Comment 6 Israel Pinto 2018-05-10 09:31:35 UTC

Engine version: 4.2.3.4-0.1.el7
Host:
OS Version:RHEL - 7.5 - 8.el7
Kernel Version: 3.10.0 - 862.el7.ppc64le
KVM Version: 2.10.0 - 21.el7_5.2
LIBVIRT Version: libvirt-3.9.0-14.el7_5.3
VDSM Version: vdsm-4.20.27.1-1.el7ev

Verified on power8.
XML structure is in lower case:
 <cpu mode='host-model' check='partial'>
    <model fallback='forbid'>power8</model>
    <topology sockets='16' cores='1' threads='1'/>
    <numa>
      <cell id='0' cpus='0' memory='1048576' unit='KiB'/>
    </numa>
  </cpu>

Comment 7 Sandro Bonazzola 2018-05-11 06:51:02 UTC

This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.3 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.