Description of problem: On xen/ia64, 'node_to_cpu' field shown by 'xm info' command is always 'no cpus'. Version-Release number of selected component (if applicable): RHEL5.2GA How reproducible: 100% Steps to Reproduce: 1. Execute 'xm info' command on xen/ia64 2. 3. Actual results: 'node_to_cpu' always shows 'no cpus' as follows: node_to_cpu : node0:no cpus node1:no cpus Expected results: The relation between nodes and cpus is shown correctly. For example, in the case of 2 nodes with 8 pcpus, the result should be as follows: node_to_cpu : node0:0-7 node1:8-15 Additional info: The following upstream patches fix this problem. *HV - [IA64] Fixup physinfo http://xenbits.xensource.com/xen-unstable.hg?rev/a36c51f43fdb - Fix XEN_SYSCTL_physinfo to handle NUMA info properly. http://xenbits.xensource.com/xen-unstable.hg?rev/547d10d2d384 *Kernel - [IA64] NUMA support http://xenbits.xensource.com/xen-unstable.hg?rev/fd1d742487f8 - [IA64] Kludge for XEN_GUEST_HANDLE_64 http://xenbits.xensource.com/xen-unstable.hg?rev/8b37c7bba7e1 - Extended the physinfo sysctl to export NUMA cpu_to_node topology info. http://xenbits.xensource.com/xen-unstable.hg?rev/89d2192942be # HV and tools have this in RHEL5.2, but kernel doesn't. - [IA64] Map cpu_to_node table with xencomm for physinfo sysctl http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/86ac3059ab67 Beside these patches, the fix for bz444589 is needed.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Created attachment 312579 [details] Fix patches
in kernel-2.6.18-110.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5
in kernel-2.6.18-113.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5
This bug has been marked for inclusion in the Red Hat Enterprise Linux 5.3 Release Notes. To aid in the development of relevant and accurate release notes, please fill out the "Release Notes" field above with the following 4 pieces of information: Cause: What actions or circumstances cause this bug to present. Consequence: What happens when the bug presents. Fix: What was done to fix the bug. Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
tetsu, rel note info requested.
release note added.
Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: The function to show NUMA info on ia64/xen was not supported. Consequence: What happens when the bug presents. 'xm info' command always shows 'no cpus' in 'node_to_cpu' field. Fix: Added the funciton to show NUMA info correctly for ia64/xen. Result: 'xm info' command shows the correct relation between cpus and nodes.
Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,11 +1 @@ -Cause: +Non-Uniform Memory Access (NUMA) information was not being displayed by the xm info command. Consequently, node_to_cpu value for each node was being incorrectly returned as no cpus. In this update, this issue has been resolved.- The function to show NUMA info on ia64/xen was not supported. - -Consequence: What happens when the bug presents. - 'xm info' command always shows 'no cpus' in 'node_to_cpu' field. - -Fix: - Added the funciton to show NUMA info correctly for ia64/xen. - -Result: - 'xm info' command shows the correct relation between cpus and nodes.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2009-0225.html