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 1270715 - Wrong display of numatune result if guest use numad advise
Summary: Wrong display of numatune result if guest use numad advise
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: John Ferlan
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-12 09:01 UTC by Luyao Huang
Modified: 2016-11-03 18:25 UTC (History)
5 users (show)

Fixed In Version: libvirt-1.3.1-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-03 18:25:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2577 0 normal SHIPPED_LIVE Moderate: libvirt security, bug fix, and enhancement update 2016-11-03 12:07:06 UTC

Description Luyao Huang 2015-10-12 09:01:41 UTC 
Description of problem:
Wrong display of numatune result if guest use numad advise

Version-Release number of selected component (if applicable):
libvirt-1.2.17-13.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. prepare a running guest which memtune placement is auto:

# virsh dumpxml rhel7.0-rhel |grep -1 numatune
  <vcpu placement='auto' current='2'>4</vcpu>
  <numatune>
    <memory mode='strict' placement='auto'/>
  </numatune>
  <resource>


2. use numatune to check nodeset:

# virsh numatune rhel7.0-rhel --live
numa_mode      : strict
numa_nodeset   : 



3.

Actual results:

libvirt do not print the current nodeset which guest running

Expected results:

# virsh numatune rhel7.0-rhel --live
numa_mode      : strict
numa_nodeset   : 0

Additional info:

test with 1.2.15-2 and find cannot reproduce this issue, so i think this maybe a regression issue:

# virsh dumpxml rhel7.0-rhel |grep -1 numatune
  <vcpu placement='auto' current='2'>4</vcpu>
  <numatune>
    <memory mode='strict' placement='auto'/>
  </numatune>
  <resource>

# virsh numatune rhel7.0-rhel --live
numa_mode      : strict
numa_nodeset   : 0
Comment 2 Luyao Huang 2015-10-12 09:31:19 UTC 
Send a patch to upstream:

https://www.redhat.com/archives/libvir-list/2015-October/msg00328.html
Comment 3 John Ferlan 2015-10-28 20:57:20 UTC 
Pushed upstream, commit id '4eac55238'

$ git describe 4eac55238
v1.2.20-148-g4eac552
$
Comment 5 Luyao Huang 2016-08-10 08:03:54 UTC 
Verify this bug with libvirt-2.0.0-4.el7.x86_64:

1. check numa struct:

# numactl --har
available: 4 nodes (0-3)
node 0 cpus: 0 2 4 6 8 10
node 0 size: 10205 MB
node 0 free: 6198 MB
node 1 cpus: 12 14 16 18 20 22
node 1 size: 8192 MB
node 1 free: 5519 MB
node 2 cpus: 1 3 5 7 9 11
node 2 size: 6144 MB
node 2 free: 3818 MB
node 3 cpus: 13 15 17 19 21 23
node 3 size: 8175 MB
node 3 free: 5799 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. prepare a guest which memtune placement is auto:

# virsh dumpxml r7
<domain type='kvm'>
  <name>r7</name>
  <uuid>67c7a123-5415-4136-af62-a2ee098ba6cd</uuid>
  <maxMemory slots='16' unit='KiB'>15243264</maxMemory>
  <memory unit='KiB'>2097152</memory>
  <currentMemory unit='KiB'>2097152</currentMemory>
  <vcpu placement='auto' current='6'>10</vcpu>
  <numatune>
    <memory mode='strict' placement='auto'/>
  </numatune>

3. start guest:

# virsh start r7
Domain r7 started

4. check numatune info:

# virsh numatune r7
numa_mode      : strict
numa_nodeset   : 0-1

5. restart libvirtd and recheck:

# virsh numatune r7
numa_mode      : strict
numa_nodeset   : 0-1
Comment 7 errata-xmlrpc 2016-11-03 18:25:59 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://rhn.redhat.com/errata/RHSA-2016-2577.html
Note You need to log in before you can comment on or make changes to this bug.