Bug 1259318 - [PPC64LE] Vdsm not set correct cpu model for vm
Summary: [PPC64LE] Vdsm not set correct cpu model for vm
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.6.0
Hardware: ppc64le
OS: Linux
medium
high
Target Milestone: ovirt-3.6.0-rc
: 3.6.0
Assignee: Martin Polednik
QA Contact: Artyom
URL:
Whiteboard:
Depends On:
Blocks: RHEV3.6PPC 1277183 1277184
TreeView+ depends on / blocked
 
Reported: 2015-09-02 12:03 UTC by Artyom
Modified: 2016-04-20 01:34 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-20 01:34:47 UTC
oVirt Team: Virt
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
vdsm log (4.78 MB, text/plain)
2015-09-02 12:03 UTC, Artyom 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 42736 0 master NEW virt: add logic for POWER cpu xml element Never
oVirt gerrit 46451 0 ovirt-3.6 MERGED virt: add logic for POWER cpu xml element Never

Description Artyom 2015-09-02 12:03:10 UTC 
Created attachment 1069399 [details]
vdsm log

Description of problem:
Vdsm not set correct cpu model for vm under ppc architecture

Version-Release number of selected component (if applicable):
vdsm-4.17.3-1.el7ev.noarch

How reproducible:
Always

Steps to Reproduce:
1. Run vm on ppc host
2.
3.

Actual results:
Vdsm send u'cpuType': u'power8', but no suck model under libvirt cpu's definition and we have
<cpu>
    <topology cores="1" sockets="1" threads="1"/>
</cpu>


Expected results:
vdsm must send u'POWER8'

Additional info:
Comment 1 Artyom 2015-10-07 15:48:10 UTC 
Verified on vdsm-4.17.8-1.el7ev.noarch

dumpxml of vm
<cpu mode='custom' match='exact'>
    <model fallback='allow'>POWER8</model>
    <topology sockets='1' cores='1' threads='1'/>
    <numa>
      <cell id='0' cpus='0' memory='1048576' unit='KiB'/>
    </numa>
</cpu>
Note You need to log in before you can comment on or make changes to this bug.