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 870099 - virsh emulatorpin still can work when vcpu placement is "auto".
Summary: virsh emulatorpin still can work when vcpu placement is "auto".
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Osier Yang
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-25 14:39 UTC by hongming
Modified: 2014-03-27 01:03 UTC (History)
8 users (show)

Fixed In Version: libvirt-0.10.2-6.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-21 07:11:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0276 0 normal SHIPPED_LIVE Moderate: libvirt security, bug fix, and enhancement update 2013-02-20 21:18:26 UTC

Description hongming 2012-10-25 14:39:49 UTC
Description of problem:
virsh emulatorpin still can work when vcpu placement is "auto".The following doc describes that "emulatorpin is not allowed if attribute placement of element vcpu is "auto". "
http://libvirt.org/formatdomain.html#elementsCPUTuning

Version-Release number of selected component (if applicable):
libvirt-0.10.2-5.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
# virsh list --all
 Id    Name                           State
----------------------------------------------------
 53    yuping-rhel6                   running


# virsh dumpxml yuping-rhel6 |grep vcpu
  <vcpu placement='auto' current='2'>4</vcpu>
# virsh emulatorpin yuping-rhel6 1

# pidof qemu-kvm
79058
# cat /proc/79058/task/79058/status |grep Cpu
Cpus_allowed:	00000000,00000000,00000000,00000000,00000002
Cpus_allowed_list:	1

  
Actual results:
virsh emulatorpin still can work when vcpu placement is "auto".

Expected results:
emulatorpin is not allowed if attribute placement of element vcpu is "auto"

Additional info:

Comment 3 hongming 2012-10-30 05:19:02 UTC
Verify it as follows. The result is expected. Move its status to VERIFIED.

# rpm -q libvirt
libvirt-0.10.2-6.el6.x86_64


# virsh dumpxml rhel6.3 |grep vcpu
  <vcpu placement='auto' current='1'>4</vcpu>


# virsh start rhel6.3
Domain rhel6.3 started


# virsh emulatorpin rhel6.3 1
error: Requested operation is not valid: Changing affinity for emulator thread dynamically is not allowed when CPU placement is 'auto'

Comment 4 errata-xmlrpc 2013-02-21 07:11:04 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.

http://rhn.redhat.com/errata/RHSA-2013-0276.html


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