Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1582418

Summary:	virsh capabilities reports invalid values for 4K pages [rhel-7.5.z]
Product:	Red Hat Enterprise Linux 7	Reporter:	Oneata Mircea Teodor <toneata>
Component:	libvirt	Assignee:	Michal Privoznik <mprivozn>
Status:	CLOSED ERRATA	QA Contact:	Jing Qi <jinqi>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.4	CC:	chhu, dyuan, jdenemar, jherrman, lmen, marjones, mkalinin, mprivozn, mtessun, rbalakri, tbonds, xuzhang
Target Milestone:	rc	Keywords:	Upstream, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libvirt-3.9.0-14.el7_5.6	Doc Type:	Bug Fix
Doc Text:	The "virsh capabilities" command previously displayed an inaccurate number of 4 KiB memory pages on systems with very large amounts of memory. This update optimizes the memory diagnostic mechanism to ensure memory page numbers are displayed correctly on such systems.	Story Points:	---
Clone Of:	1569678	Environment:
Last Closed:	2018-06-26 16:55:29 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1569678
Bug Blocks:

Description Oneata Mircea Teodor 2018-05-25 07:21:11 UTC

This bug has been copied from bug #1569678 and has been proposed to be backported to 7.5 z-stream (EUS).

Comment 3 Michal Privoznik 2018-05-25 12:50:40 UTC

To POST:

http://post-office.corp.redhat.com/archives/rhvirt-patches/2018-May/msg00790.html

Scratch build:

https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=16461622

Comment 5 Jing Qi 2018-06-08 02:36:47 UTC

With libvirt-3.9.0-14.virtcov.el7_5.6.x86_64 version, enable 1G hugepages in  RHEL7.5 system and config 1G hugepages counts for numa cells and run below commands. The values are correct.
#virsh capabilities 
<topology>
      <cells num='8'>
        <cell id='0'>
          <memory unit='KiB'>16742068</memory>
          <pages unit='KiB' size='4'>1039789</pages>
          <pages unit='KiB' size='2048'>0</pages>
          <pages unit='KiB' size='1048576'>12</pages>
          <distances>
            <sibling id='0' value='10'/>
            ...
          </distances>
          <cpus num='8'>
            <cpu id='0' socket_id='0' core_id='0' siblings='0,4'/>
            ...
          </cpus>
        </cell>
        <cell id='1'>
          <memory unit='KiB'>16777216</memory>
          <pages unit='KiB' size='4'>524288</pages>
          <pages unit='KiB' size='2048'>0</pages>
          <pages unit='KiB' size='1048576'>14</pages>
          ....
         
         <cell id='2'>
          <memory unit='KiB'>16777216</memory>
          <pages unit='KiB' size='4'>4194304</pages>
          <pages unit='KiB' size='2048'>0</pages>
          <pages unit='KiB' size='1048576'>0</pages>
          ....
         <cell id='3'>
          <memory unit='KiB'>16777216</memory>
          <pages unit='KiB' size='4'>524288</pages>
          <pages unit='KiB' size='2048'>0</pages>
          <pages unit='KiB' size='1048576'>14</pages>
          ...
          <cell id='4'>
          <memory unit='KiB'>16777216</memory>
          <pages unit='KiB' size='4'>4194304</pages>
          <pages unit='KiB' size='2048'>0</pages>
          <pages unit='KiB' size='1048576'>0</pages>
         ....
         <cell id='5'>
          <memory unit='KiB'>16777216</memory>
          <pages unit='KiB' size='4'>524288</pages>
          <pages unit='KiB' size='2048'>0</pages>
          <pages unit='KiB' size='1048576'>14</pages>
          ....
         <cell id='6'>
          <memory unit='KiB'>16777216</memory>
          <pages unit='KiB' size='4'>524288</pages>
          <pages unit='KiB' size='2048'>0</pages>
          <pages unit='KiB' size='1048576'>14</pages>
           ....
         <cell id='7'>
          <memory unit='KiB'>16760828</memory>
          <pages unit='KiB' size='4'>782335</pages>
          <pages unit='KiB' size='2048'>0</pages>
          <pages unit='KiB' size='1048576'>13</pages>

 # virsh freepages --all
Node 0:
4KiB: 869199
2048KiB: 0
1048576KiB: 12

Node 1:
4KiB: 430137
2048KiB: 0
1048576KiB: 14

Node 2:
4KiB: 4072669
2048KiB: 0
1048576KiB: 0

Node 3:
4KiB: 430401
2048KiB: 0
1048576KiB: 14

Node 4:
4KiB: 4073071
2048KiB: 0
1048576KiB: 0

Node 5:
4KiB: 430404
2048KiB: 0
1048576KiB: 14

Node 6:
4KiB: 428752
2048KiB: 0
1048576KiB: 14

Node 7:
4KiB: 633198
2048KiB: 0
1048576KiB: 13

Comment 7 errata-xmlrpc 2018-06-26 16:55:29 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.

https://access.redhat.com/errata/RHSA-2018:1997