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 868972 - CPU topology is missing in capabilities XML when libvirt fails to detect host CPU model
Summary: CPU topology is missing in capabilities XML when libvirt fails to detect host...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Jiri Denemark
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 866999 876475
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-22 15:27 UTC by Chris Pelland
Modified: 2012-11-22 09:40 UTC (History)
15 users (show)

Fixed In Version: libvirt-0.9.10-21.el6_3.6
Doc Type: Bug Fix
Doc Text:
Cause: When libvirt could not find a suitable CPU model for host CPU, it would not provide CPU topology in host capabilities even though the topology was detected correctly. Consequence: Applications that want to examine host CPU topology but otherwise do not care about CPU model could not see the topology in host capabilities. Fix: Host capabilities XML now contains host CPU topology even if host CPU model is unknown. Result: Applications can rely on host CPU topology to always be present in capabilities XML unless detecting the topology itself failed.
Clone Of:
Environment:
Last Closed: 2012-11-22 09:40:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:1484 0 normal SHIPPED_LIVE libvirt bug fix update 2012-11-22 14:39:12 UTC

Description Chris Pelland 2012-10-22 15:27:07 UTC
This bug has been copied from bug #866999 and has been proposed
to be backported to 6.3 z-stream (EUS).

Comment 7 Rami Vaknin 2012-11-14 16:23:44 UTC
Verified on libvirt-0.9.10-21.el6_3.6.x86_64 (rhel6.3).

The VM's xml given by "virsh capabilities" now contains the cpu topology:

<capabilities>

  <host>
    <uuid>067f8a8b-5ab3-413c-aa37-945854bf102e</uuid>
    <cpu>
      <arch>x86_64</arch>
      <topology sockets='1' cores='1' threads='1'/>
    </cpu>
    <power_management>
      <suspend_disk/>
    </power_management>
    <migration_features>
      <live/>
      <uri_transports>
        <uri_transport>tcp</uri_transport>
      </uri_transports>
    </migration_features>
    <topology>
      <cells num='1'>
        <cell id='0'>
          <cpus num='1'>
            <cpu id='0'/>
          </cpus>
        </cell>
      </cells>
    </topology>
    <secmodel>
      <model>selinux</model>
      <doi>0</doi>
    </secmodel>
  </host>

</capabilities>

Comment 9 errata-xmlrpc 2012-11-22 09:40:03 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-2012-1484.html


Note You need to log in before you can comment on or make changes to this bug.