RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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:

excluded issues in ovirt-host-deploy, back to hosted-engine.

Looks like VDSM caps call: caps._getCompatibleCpuModels() returns an empty set.

can you provide the output of:
# vdsClient -s 0 getVdsCaps

moving to vdsm.

seems like the libvirt's detection doesn't work for this CPU.

Can we get debugs logs from libvirtd generated when libvirtd starts?

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.

Thanks Jiri. I opened BZ#1103672 to implement a check for the NX flag in the installer script.