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.
Bug 799708 - [RFE] Display CPU type + extended information on status screen
Summary: [RFE] Display CPU type + extended information on status screen
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.4
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Joey Boggs
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 831319
Blocks: 816255 840699 852682
TreeView+ depends on / blocked
 
Reported: 2012-03-04 14:13 UTC by Andrew Cathrow
Modified: 2016-04-26 16:36 UTC (History)
15 users (show)

Fixed In Version: ovirt-node-2.5.0-5.el6
Doc Type: Enhancement
Doc Text:
The CPU Details Info section of the status page has been improved to include more information. It now lists CPU Name, CPU Type, Virtualization Extensions Enabled, Flag, CPU Sockets, and CPU Cores.
Clone Of:
: 831319 852682 (view as bug list)
Environment:
Last Closed: 2013-02-28 16:30:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0556 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2013-02-28 21:29:06 UTC

Description Andrew Cathrow 2012-03-04 14:13:54 UTC 
The CPU type is used by RHEV-M for compatibility - eg. Nehalem family, westmere, etc.

A common issue from users is to understand what CPU they have and it's capabilities - eg. VT/SVM and NX being disabled are problem for us.

We should provide 
CPU name (eg. "Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz")
CPU Type (eg. Intel Westmere)
Virtualization Extensions enabled (true|false)
If XD(NX) is set for Intel machines 
or "Enhanced Virus Protection" for AMD machines

Socket Count : eg 2 Socket
Cores per Socket: eg 4
Hyperthreading enabled : Yes / no (only for AMD)
Comment 4 Daniel Berrangé 2012-04-03 15:44:52 UTC 
> A common issue from users is to understand what CPU they have and it's
> capabilities - eg. VT/SVM and NX being disabled are problem for us.

Libvirt 0.9.10+ now provides a standalone command expressly for validating the scenario fo VT/SVM being off in the BIOS. eg you can run

 # virt-host-validate qemu
  QEMU: Checking for hardware virtualization                                 : PASS
  QEMU: Checking for device /dev/kvm                                         : PASS
  QEMU: Checking for device /dev/vhost-net                                   : PASS
  QEMU: Checking for device /dev/net/tun                                     : PASS


we don't check NX currently, but that could be added. The virt-host-validate command is intended to be used by users / admins to sanity check their hardware prior to running libvirt/KVM
Comment 5 Andrew Cathrow 2012-04-03 15:54:03 UTC 
(In reply to comment #4)
> > A common issue from users is to understand what CPU they have and it's
> > capabilities - eg. VT/SVM and NX being disabled are problem for us.
> 
> Libvirt 0.9.10+ now provides a standalone command expressly for validating the
> scenario fo VT/SVM being off in the BIOS. eg you can run
> 
>  # virt-host-validate qemu
>   QEMU: Checking for hardware virtualization                                 :
> PASS
>   QEMU: Checking for device /dev/kvm                                         :
> PASS
>   QEMU: Checking for device /dev/vhost-net                                   :
> PASS
>   QEMU: Checking for device /dev/net/tun                                     :
> PASS
> 
> 
> we don't check NX currently, but that could be added. The virt-host-validate
> command is intended to be used by users / admins to sanity check their hardware
> prior to running libvirt/KVM

Dan what's your thoughts on adding the virsh capabilities cpu vendor|model output there as well ?
Alternatively we just parse that ourselves.
Comment 6 Daniel Berrangé 2012-04-03 16:05:40 UTC 
We could add a check that the host CPU model, is resolvable to one of the CPU models in cpu_map.xml - that would catch the NX problem nicely.
Comment 7 RHEL Program Management 2012-07-10 08:23:01 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 8 RHEL Program Management 2012-07-11 01:48:02 UTC 
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 13 haiyang,dong 2012-12-18 05:38:27 UTC 
Test version:
rhev-hypervisor6-6.4-20121212.1.el6 
ovirt-node-2.5.0-11.el6

Tested as follows:
1. clean install rhev-h
2. Enter into status page
3. click the "<view cpu details>" button to view CPU Details Info

CPU Details page provide the follow item info:
CPU Name/CPU Type/Virtualization Extensions Enabled/Flag/CPU Sockets/CPU Cores

so this bug has been fixed, change the the status into "VERIFIED"
Comment 15 errata-xmlrpc 2013-02-28 16:30:16 UTC 
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-2013-0556.html
Note You need to log in before you can comment on or make changes to this bug.