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 614288 - RFE: Option to perform CPU pinning on a running VM, (aka #virsh vcpupin)
Summary: RFE: Option to perform CPU pinning on a running VM, (aka #virsh vcpupin)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Cole Robinson
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 655920
TreeView+ depends on / blocked
 
Reported: 2010-07-14 03:10 UTC by dyuan
Modified: 2011-05-19 13:46 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-19 13:46:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0637 0 normal SHIPPED_LIVE virt-manager bug fix and enhancement update 2011-05-18 17:55:47 UTC

Description dyuan 2010-07-14 03:10:35 UTC 
Description of problem:

Assign the NUMA generated pinning to a running VM, which should not require a guest reboot to take effect as #virsh vcpupin behavior in libvirt.

And it should show the error just like 'error: vcpupin: Invalid vCPU number.' but not 'Some changes may require a guest reboot to take effect.' when I give a larger value than the num of physical cpus.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 2 RHEL Program Management 2010-07-14 03:37:20 UTC 
This feature request did not get resolved in time for Feature Freeze
for the current Red Hat Enterprise Linux release and has now been
denied. It has been proposed for the next Red Hat Enterprise Linux
release.

**  If you would still like this feature request considered for
the current release, please ask your support representative to
file an exception on your behalf.  **
Comment 3 Daniel Berrangé 2010-07-14 09:49:55 UTC 
NB it doesn't make sense to refer to this as NUMA pinning, since NUMA pinning can only be done at startup. Once a VM is running, its memory has already been allocated from whatever NUMA node it started running on. You can change pinning of the virtual CPUs at runtime, but this will not affect NUMA placement of the guest's memory.
Comment 5 dyuan 2010-07-15 06:04:40 UTC 
Version-Release number of selected component :
virt-manager-0.8.4-6.el6.
libvirt-0.8.1-15.el6.

This feature has been supported by libvirt for a long time, but never be supported by virt-manager. So, it's really a bug need to be fixed.
Comment 7 Cole Robinson 2011-01-13 19:27:06 UTC 
Upstream now:

http://hg.fedorahosted.org/hg/virt-manager/rev/076a25e83401
Comment 8 Cole Robinson 2011-01-14 22:19:39 UTC 
Fixed in virt-manager-0.8.6-1.el6
Comment 10 zhanghaiyan 2011-03-02 10:06:07 UTC 
Verified this bug PASS with virt-manager-0.8.6-2.el6.noarch

Could perfrom cpu pin for each vcpu at runtime via virt-manager
Comment 11 mliu 2011-04-18 05:33:27 UTC 
Verified this bug PASS with virt-manager-0.8.6-3.el6.noarch
Comment 12 errata-xmlrpc 2011-05-19 13:46:16 UTC 
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/RHBA-2011-0637.html
Note You need to log in before you can comment on or make changes to this bug.