Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
When large numbers of CPUs are present, virsh vcpuinfo's linear representation of affinity is not very useful. (See example output below) I'd like to see an option for a representation based on ranges. I'm not a UI guy, but I'd prefer something along the lines of:
virsh vcpuinfo --affinityranges someguest
VCPU: 0
CPU: 0
State: running
CPU time: 5.6s
CPU Affinity: y: 0-3
-: 4-127
Current output:
virsh vcpuinfo someguest
VCPU: 0
CPU: 0
State: running
CPU time: 5.6s
CPU Affinity: yyyy----------------------------------------------------------------------------------------------------------------------------
Now pushed upstream:
commit a3173fef9dde49d7577e283109281e43d399b3a2
Author: Ján Tomko <jtomko>
CommitDate: 2014-06-06 14:35:19 +0200
Implement pretty flag for vcpuinfo and nodecpumap
Report CPU affinities / online CPUs in human-readable form when
this flag is present:
Before:
CPU Affinity: y-yy
After:
CPU Affinity: 0,2-3 (out of 4)
https://bugzilla.redhat.com/show_bug.cgi?id=985980
git describe: v1.2.5-68-ga3173fe
verify it as follows. The result is expected. Move its status to VERIFIED.
[root@localhost ~]# virsh vcpupin r7 1 0,2-3
[root@localhost ~]# virsh vcpuinfo r7
VCPU: 0
CPU: 0
State: running
CPU time: 8.1s
CPU Affinity: yyyy
VCPU: 1
CPU: 0
State: running
CPU time: 1.6s
CPU Affinity: y-yy
VCPU: 2
CPU: 1
State: running
CPU time: 1.7s
CPU Affinity: yyyy
VCPU: 3
CPU: 2
State: running
CPU time: 2.1s
CPU Affinity: yyyy
[root@localhost ~]# virsh vcpuinfo r7 --pretty
VCPU: 0
CPU: 3
State: running
CPU time: 8.1s
CPU Affinity: 0-3 (out of 4)
VCPU: 1
CPU: 0
State: running
CPU time: 1.7s
CPU Affinity: 0,2-3 (out of 4)
VCPU: 2
CPU: 0
State: running
CPU time: 1.7s
CPU Affinity: 0-3 (out of 4)
VCPU: 3
CPU: 1
State: running
CPU time: 2.1s
CPU Affinity: 0-3 (out of 4)
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.
https://rhn.redhat.com/errata/RHSA-2015-0323.html
Description of problem: When large numbers of CPUs are present, virsh vcpuinfo's linear representation of affinity is not very useful. (See example output below) I'd like to see an option for a representation based on ranges. I'm not a UI guy, but I'd prefer something along the lines of: virsh vcpuinfo --affinityranges someguest VCPU: 0 CPU: 0 State: running CPU time: 5.6s CPU Affinity: y: 0-3 -: 4-127 Current output: virsh vcpuinfo someguest VCPU: 0 CPU: 0 State: running CPU time: 5.6s CPU Affinity: yyyy----------------------------------------------------------------------------------------------------------------------------