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.
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.
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:3113
I can reproduce this issue on libvirt-3.2.0-14.el7_4.9.x86_64: 1. # numactl --har available: 4 nodes (0-3) node 0 cpus: 0 2 4 6 node 0 size: 2047 MB node 0 free: 1666 MB node 1 cpus: 8 10 12 14 node 1 size: 2014 MB node 1 free: 1640 MB node 2 cpus: 9 11 13 15 node 2 size: 4096 MB node 2 free: 3881 MB node 3 cpus: 1 3 5 7 node 3 size: 8191 MB node 3 free: 7945 MB node distances: node 0 1 2 3 0: 10 20 20 20 1: 20 10 20 20 2: 20 20 10 20 3: 20 20 20 10 2. # virsh capabilities ... <cell id='3'> <memory unit='KiB'>8388604</memory> <pages unit='KiB' size='4'>2097151</pages> <pages unit='KiB' size='2048'>0</pages> <pages unit='KiB' size='1048576'>0</pages> ... 3. add 4 1g hugepage (only reproduce this issue when use page >= 4) echo 4 > /sys/devices/system/node/node3/hugepages/hugepages-1048576kB/nr_hugepages 4. <cell id='3'> <memory unit='KiB'>8388604</memory> <pages unit='KiB' size='4'>2097151</pages> <pages unit='KiB' size='2048'>0</pages> <pages unit='KiB' size='1048576'>4</pages> And i used gdb to check why this will happened and found some interesting things: After add 4294967296 to huge_page_sum, the huge_page_sum still is 0, that looks like overflow happened, but huge_page_sum is a ull type and 4294967296 is 2^32 (32bit ull length). 781 huge_page_sum += 1024 * page_size * page_avail; (gdb) p page_avail $26 = 4 (gdb) p page_size $27 = 1048576 (gdb) p huge_page_sum $28 = 0 (gdb) n 745 while (dir && (direrr = virDirRead(dir, &entry, path)) > 0) { (gdb) p huge_page_sum $29 = 0