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)
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager (Show other bugs)
(Show other bugs)
Version: 6.0
Hardware: All Linux
Target Milestone: rc
: ---
Assignee: Cole Robinson
QA Contact: Virtualization Bugs
Keywords: FutureFeature
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:
Story Points: ---
Clone Of:
Last Closed: 2011-05-19 13:46:16 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0637 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:
Actual results:

Expected results:

Additional info:

Comment 2 RHEL Product and 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

**  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 Berrange 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 :

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:


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.


Note You need to log in before you can comment on or make changes to this bug.