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.

+++ This bug was initially created as a clone of Bug #848728 +++

Description of problem:
As a result of bz#781975 and http://gerrit.ovirt.org/1737 VDSM's getVdsCaps call only returns the number of physical cores on a system. We should provide a way for customers to force VDSM to return the total number of physical and logical cores/threads on the host.

Version-Release number of selected component (if applicable):
vdsm-4.9.6-28.0.el6_3

How reproducible:
Always

Steps to Reproduce:
1. vdsClient -s 0 getVdsCaps

  
Actual results:
getVdsCaps returns the number of physical cores on the host.

Expected results:
Given the correct config value getVdsCaps should be able to return both the total number of physical and logical cores/threads on a system.

Additional info:
http://gerrit.ovirt.org/#/c/7097/

http://gerrit.usersys.redhat.com/1398

when report_host_threads_as_cores is left in its default "false" value, the number of real host cores is to be reported in cpuCores. When the value is changed to "true", hyperthreads are counted instead.

Patch accepted downstream (http://gerrit.usersys.redhat.com/#change,1398)
Hence moving to MODIFIED.

OK - vdsm-4.9-113.4.el6_3

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-1390.html