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 845864 - [RFE] Add optional --placement parameter to numatune command.
Summary: [RFE] Add optional --placement parameter to numatune command.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Osier Yang
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-06 01:13 UTC by hongming
Modified: 2012-09-17 14:29 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-17 14:29:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description hongming 2012-08-06 01:13:35 UTC 
Description of problem:
The numatune command can get or set the "mode" and "nodeset" parameters for a guest domain. But it is unable to set or get the "placement" parameter.The customers may have the request for virsh to tune the memory placement for domain process.  

Quote as follows from libvirt.org http://libvirt.org/formatdomain.html#elementsNUMATuning

Attribute placement (since 0.9.12) can be used to indicate the memory placement mode for domain process, its value can be either "static" or "auto", 
defaults to placement of vcpu, or "static" if nodeset is specified. "auto" indicates the domain process will only allocate memory from the advisory 
nodeset returned from querying numad, and the value of attribute nodeset will be ignored if it's specified.
If placement of vcpu is 'auto', and numatune is not specified, a default numatune with placement 'auto' and mode 'strict' will be added implicitly.




Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1.# virsh dumpxml rhel6q 

  <vcpu placement='auto'>10</vcpu>
  <numatune>
    <memory mode='strict' placement='auto'/>
  </numatune>


2.# virsh numatune rhel6q
numa_mode      : strict
numa_nodeset   : 1

3.
  
Actual results:
The numatune command is unable to set and get the placement parameter.


Expected results:
The numatune command is able to set and get the placement parameter.

Additional info:
Comment 2 Osier Yang 2012-08-17 07:51:46 UTC 
(In reply to comment #0)
> Description of problem:
> The numatune command can get or set the "mode" and "nodeset" parameters for
> a guest domain. But it is unable to set or get the "placement" parameter.The
> customers may have the request for virsh to tune the memory placement for
> domain process.  

IMO we should NACK this request, because the numatune command is based on cgroup
setting, however, the "placement" is for numad. It shouldn't be mixed together
further any more. We already suffering from the mess (share same XML syntax for
two underlying entries of one same driver). On the other hand, "placement"
tuning doesn't make any sense for a running domain.
Note You need to log in before you can comment on or make changes to this bug.