Bug 985980 – virsh vcpuinfo output is difficult to read with large cpu counts

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 985980 - virsh vcpuinfo output is difficult to read with large cpu counts

Summary:	virsh vcpuinfo output is difficult to read with large cpu counts

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	libvirt (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity low
Target Milestone:	rc
Target Release:	---
Assigned To:	Ján Tomko
QA Contact:	Virtualization Bugs
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2013-07-18 12:30 EDT by Dave Allan
Modified:	2016-04-26 10:51 EDT (History)
CC List:	7 users (show)

See Also:
Fixed In Version:	libvirt-1.2.7-1.el7
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-03-05 02:20:56 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2015:0323	normal	SHIPPED_LIVE	Low: libvirt security, bug fix, and enhancement update	2015-03-05 07:10:54 EST

Groups: None (edit)

Description Dave Allan 2013-07-18 12:30:17 EDT

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----------------------------------------------------------------------------------------------------------------------------

Comment 1 Eric Blake 2013-07-18 15:06:57 EDT

For back-compat reason, we'd have to provide the new compressed output only when the user adds a flag, but the idea has merit.

Comment 2 Ján Tomko 2014-06-05 07:26:35 EDT

Upstream patch:
https://www.redhat.com/archives/libvir-list/2014-June/msg00259.html

Comment 3 Ján Tomko 2014-06-06 08:42:38 EDT

Now pushed upstream:
commit a3173fef9dde49d7577e283109281e43d399b3a2
Author:     Ján Tomko <jtomko@redhat.com>
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

Comment 6 hongming 2014-11-28 02:03:45 EST

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)

Comment 8 errata-xmlrpc 2015-03-05 02:20:56 EST

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

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