Bug 1100326

Summary: caps._getCompatibleCpuModels() returns an empty set for Intel(R) Xeon(R) CPU X5450 @ 3.00GHz
Product: Red Hat Enterprise Linux 6 Reporter: Evgheni Dereveanchin <ederevea>
Component: libvirtAssignee: Jiri Denemark <jdenemar>
Status: CLOSED NOTABUG QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: medium    
Version: 6.5CC: acathrow, akotov, bazulay, didi, dougsland, ederevea, fromani, iheim, jdenemar, lpeer, lveyde, michal.skrivanek, Rhev-m-bugs, sbonazzo, stirabos, yeylon
Target Milestone: pre-dev-freeze   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-28 09:35:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Evgheni Dereveanchin 2014-05-22 14:25:52 UTC 
Description of problem:
when running "hosted-engine --deploy" on a host with Intel(R) Xeon(R) X5450 CPU,
no CPU family is listed as supported, although the vmx feature is present and virtualization is enabled.

Version-Release number of selected component (if applicable):
otopi-1.1.3 (otopi-1.1.3-1.el6ev)

Steps to Reproduce:
1. # hosted-engine --deploy
2. go through steps until "VM CONFIGURATION" section

Actual results:

the list of CPUs is empty:
The following CPU types are supported by this host:
Please specify the CPU type to be used by the VM []:


Expected results:

supported families are displayed:
The following CPU types are supported by this host: 
- model_Conroe: Intel Conroe Family
...
Please specify the CPU type to be used by the VM [model_Conroe]:

Additional info:
Comment 6 Sandro Bonazzola 2014-05-22 15:33:40 UTC 
excluded issues in ovirt-host-deploy, back to hosted-engine.
Comment 7 Sandro Bonazzola 2014-05-22 15:42:06 UTC 
Looks like VDSM caps call: caps._getCompatibleCpuModels() returns an empty set.

can you provide the output of:
# vdsClient -s 0 getVdsCaps
Comment 8 Sandro Bonazzola 2014-05-22 15:44:13 UTC 
moving to vdsm.
Comment 13 Michal Skrivanek 2014-05-23 12:09:30 UTC 
seems like the libvirt's detection doesn't work for this CPU.
Comment 15 Jiri Denemark 2014-05-23 12:16:48 UTC 
Can we get debugs logs from libvirtd generated when libvirtd starts?
Comment 18 Jiri Denemark 2014-05-28 09:35:59 UTC 
Everything works as expected from libvirt's point of view. According to the CPU features libvirt would detect host CPU as Penryn, which is a superset of Conroe, if there was an "nx" feature provided by the host CPU. In other words, nx is most likely disabled in host's BIOS and thus the host CPU model does not satisfy all features required by Conroe or better CPU models. Enabling nx should make libvirt detect the CPU as Penryn and then Conroe should be on the list of compatible CPUs.
Comment 19 Evgheni Dereveanchin 2014-06-02 10:35:39 UTC 
Thanks Jiri. I opened BZ#1103672 to implement a check for the NX flag in the installer script.