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 626742 - virsh vcpuinfo gives inaccurate output after vcpu pinning on NUMA host
Summary: virsh vcpuinfo gives inaccurate output after vcpu pinning on NUMA host
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Daniel Berrangé
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-24 09:25 UTC by Keqin Hong
Modified: 2011-06-21 01:45 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-21 01:45:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Keqin Hong 2010-08-24 09:25:45 UTC 
Description of problem:
After executing some vcpupin operation under virsh, CPU and CPU Affinity info mismatch by checking vcpuinfo.

Version-Release number of selected component (if applicable):
libvirt-0.8.1-27.el6.x86_64
libvirt-client-0.8.1-27.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. # virsh dump guest1
...
<vcpu cpuset='0-3'>4</vcpu>
...
2. # virsh start guest1
3. # virsh vcpuinfo guest1
VCPU:           0
CPU:            1
State:          running
CPU time:       9.2s
CPU Affinity:   yyyy------------

VCPU:           1
CPU:            0
State:          running
CPU time:       2.3s
CPU Affinity:   yyyy------------

VCPU:           2
CPU:            0
State:          running
CPU time:       2.7s
CPU Affinity:   yyyy------------

VCPU:           3
CPU:            0
State:          running
CPU time:       2.5s
CPU Affinity:   yyyy------------

4. pin vcpu0-3 to physical cpu0-3 respectively
# virsh vcpupin guest1 0 0
# virsh vcpupin guest1 1 1
# virsh vcpupin guest1 2 2
# virsh vcpupin guest1 3 3

5.# virsh vcpuinfo guest1
VCPU:           0
CPU:            1
                ^ wrong
State:          running
CPU time:       9.2s
CPU Affinity:   y---------------
                ^ right

VCPU:           1
CPU:            1
                ^ right
State:          running
CPU time:       2.4s
CPU Affinity:   -y--------------
                 ^ right
VCPU:           2
CPU:            0
                ^ wrong
State:          running
CPU time:       2.7s
CPU Affinity:   --y-------------
                  ^ right

VCPU:           3
CPU:            1
                ^ wrong
State:          running
CPU time:       2.6s
CPU Affinity:   ---y------------
                   ^ right
  
Actual results:
CPU and CPU affinity info mismatch

Expected results:
CPU and CPU affinity info should match

Additional info:
1. The problem seems to happen on NUMA machine only.
2. After a long time (several mins later), CPU and CPU affinity info match eventually.
So the problem is the CPU info being not synchronized in time.
Comment 1 Daniel Berrangé 2010-08-24 10:15:49 UTC 
The 'CPU: 1' field tells you what host CPU the guest vCPU is currently executing on. It sounds like the kernel isn't immediately honouring the CPU affinity libvirt requested & I'm not aware of any way to force it todo this more promptly
Comment 2 Suzanne Logcher 2011-03-28 21:12:04 UTC 
Since RHEL 6.1 External Beta has begun, and this bug remains 
unresolved, it has been rejected as it is not proposed as an 
exception or blocker.

Red Hat invites you to ask your support representative to 
propose this request, if appropriate and relevant, in the 
next release of Red Hat Enterprise Linux.
Comment 3 Dave Allan 2011-06-21 01:45:18 UTC 
Closing as CANTFIX per comment 1.
Note You need to log in before you can comment on or make changes to this bug.