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

Bug 1431211

Summary: HE vm fails to migrate due to host CPU incompatibility even after changing cluster CPU type
Product: [oVirt] ovirt-engine Reporter: Stefano Stagnaro <stefano.stagnaro>
Component: BLL.HostedEngineAssignee: Doron Fediuck <dfediuck>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: high Docs Contact:
Priority: high    
Version: ---CC: bugs, mgoldboi, michal.skrivanek, stirabos
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: hosted-engine Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-13 14:58:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Stefano Stagnaro 2017-03-10 15:35:44 UTC 
Description of problem:
I've started an oVirt 4.1 HE deployment on a Broadwell based server. Then I added to HE a second, older host based on Nehalem. I've downgraded the cluster CPU type to Nehalem to accommodate host2 and it finally reached score 3400. However, when I try to migrate HE vm it fails with the following error:

2017-03-03 20:19:51,814 ERROR (migsrc/b0d38435) [virt.vm (vmId='b0d38435-5774-4ca9-ad24-70b57b5bc25d') unsupported configuration: 
guest and host CPU are not compatible: Host CPU does not provide 
required features: pclmuldq, fma, pcid, x2apic, movbe, tsc-deadline, 
aes, xsave, avx, fsgsbase, bmi1, hle, avx2, smep, bmi2, erms, invpcid, 
rtm, rdseed, adx, smap, 3dnowprefetch; try using 'Broadwell-noTSX' CPU 
model (migration:265)

The workaround is to manually change the number of cores for the HE vm from the Admin portal to force a configuration update.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. start HE deployment on the firts node
2. add second HE node with lower cpu family (adjusting cluster cpu type)
3. try to migrate the HE vm

Actual results:
HE vm migration fails with aforementioned error.

Expected results:
I believe this setting should be automatically configured, otherwise do not reach score 3400.

Additional info:
Comment 1 Doron Fediuck 2017-03-13 14:58:39 UTC 

*** This bug has been marked as a duplicate of bug 1393835 ***