Bug 1854922
Summary: | spec_ctrl host feature not detected | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [oVirt] vdsm | Reporter: | Rik Theys <rik.theys> | ||||||||||||
Component: | General | Assignee: | Milan Zamazal <mzamazal> | ||||||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Yaning Wang <yaniwang> | ||||||||||||
Severity: | high | Docs Contact: | |||||||||||||
Priority: | high | ||||||||||||||
Version: | 4.40.22 | CC: | ahadas, bugs, gorbyo, michal.skrivanek, mzamazal, sigbjorn.lie, usurse | ||||||||||||
Target Milestone: | ovirt-4.4.2 | Keywords: | ZStream | ||||||||||||
Target Release: | 4.40.24 | Flags: | sbonazzo:
ovirt-4.4?
sbonazzo: planning_ack? sbonazzo: devel_ack? sbonazzo: testing_ack? |
||||||||||||
Hardware: | Unspecified | ||||||||||||||
OS: | Unspecified | ||||||||||||||
Whiteboard: | |||||||||||||||
Fixed In Version: | vdsm-4.40.24 | Doc Type: | Bug Fix | ||||||||||||
Doc Text: |
spec_ctrl CPU flag might not be set for newer Intel CPU models, resulting in problems with adding hosts with those CPUs. It has been fixed and spec_ctrl is set for those CPUs now.
|
Story Points: | --- | ||||||||||||
Clone Of: | |||||||||||||||
: | 1870040 1875609 (view as bug list) | Environment: | |||||||||||||
Last Closed: | 2020-09-18 07:12: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: | |||||||||||||||
Bug Depends On: | |||||||||||||||
Bug Blocks: | 1875609 | ||||||||||||||
Attachments: |
|
Description
Rik Theys
2020-07-08 12:46:49 UTC
Can you please attach full vdsm.log and engine.log? And virsh domcapabilities and virsh capabilities output if you can. Thanks! Created attachment 1700387 [details]
vdsm log
Created attachment 1700388 [details]
engine log
Created attachment 1700389 [details]
capabilities
Created attachment 1700390 [details]
domcapabilities
Hi,
I've attached the requested logs and command output.
The logs will show a lot of attempts to get this host up as I'm having multiple issues.
Regards,
Rik
It could be because your host is Cascadelake-Server and bug 1837266 is adding it only for names ending with -IBRS...but in this case it doesn't. Milan, it may need another exception or maybe blacklist rather than a whitelist for this... Hi Michal, (In reply to Michal Skrivanek from comment #6) > It could be because your host is Cascadelake-Server and bug 1837266 is > adding it only for names ending with -IBRS...but in this case it doesn't. > Milan, it may need another exception or maybe blacklist rather than a > whitelist for this... Are you sure my cpu is a Cascadelake? According to the 'virsh capabilities' my cpu model is Skylake-Server-IBRS. Since it ends with -IBRS, it makes me believe the feature should have been automatically added to my feature list already. According to https://ark.intel.com/content/www/us/en/ark/products/123550/intel-xeon-silver-4114-processor-13-75m-cache-2-20-ghz.html my cpu is a Skylake cpu. Regards, Rik Hi Rik, indeed your physical CPU model is reported as Skylake-Server-IBRS. For some reason, libvirt apparently decides to use Cascadelake model for your guests, as reported in `virsh domcapabilities'. Both the models should report spec_ctrl, but Vdsm currently reports it only for *-IBRS. So I think Michal's analysis above still applies and we need one of the suggested fixes. Verified on: rhv-4.4.2-2 vdsm-4.40.24-1 Steps: 1. Add an Intel(R) Xeon(R) Silver 4110 CPU host to a 4.4 cluster Actual results: hosts successfully added to cluster without any complaints I created cluster for v4.4.0 and after upgrade I had the same problem on ovirt v4.4.1.4. I found this bugreport and updated to version 4.4.2-pre, the problem remained with error The host CPU does not match the Cluster CPU Type and is running in a degraded mode. It is missing the following CPU flags: vmx, model_Skylake-Server, nx. Please update the host CPU microcode or change the Cluster CPU Type. In additional I tried reinstall CPU: Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz ovirt-engine-4.4.2.2-1.el8.noarch vdsm-4.40.25-1.el8.x86_64 Created attachment 1711580 [details]
engine log
Sorry missed text I tried reinstall exist host and catch same error it's not the same issue, please use a separate bugs with separate logs (from hosts please) *** Bug 1869209 has been marked as a duplicate of this bug. *** This bugzilla is included in oVirt 4.4.2 release, published on September 17th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.2 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. |