Bug 2137332

Summary:	RFE: guest agent 'guest-get-cpustats' api support
Product:	Red Hat Enterprise Linux 9	Reporter:	dehanmeng <demeng>
Component:	qemu-kvm	Assignee:	Kostiantyn Kostiuk <kkostiuk>
qemu-kvm sub component:	Guest Agent	QA Contact:	dehanmeng <demeng>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	coli, jinzhao, juzhang, kkostiuk, mrezanin, qizhu, virt-maint, yfu, ymankad, yvugenfi
Version:	9.2	Keywords:	FutureFeature, Triaged
Target Milestone:	rc	Flags:	kkostiuk: needinfo+
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	qemu-kvm-7.1.0-1.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-09 07:20:51 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2135806
Bug Blocks:

Description dehanmeng 2022-10-24 13:47:23 UTC

Description of problem:
Add a new 'guest-get-cpustats' command for getting statistics of each CPU in millisecond.
for Linux guests.

[1]: https://qemu-project.gitlab.io/qemu/interop/qemu-ga-ref.html#id89
[2]: https://github.com/qemu/qemu/blob/master/qga/qapi-schema.json#L1650

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

Comment 2 John Ferlan 2022-11-04 10:55:18 UTC

Similar to bug 2137330, I see this is a Linux bug, so I'll revert the component/subcomponent/pool change that I made in error.

Since I was looking through qemu.git, I searched through and found commit 1db8a0b0ea2fb72ecab36bd3143a9715c083d5d3, so I'll assume that's what is necessary and adjust the bug here.

I also note that commit went into qemu-7.1 so theoretically it could be tested already since qemu-7.1 has already been rebased. That means it probably could be verified, but then we'd have to get it added to the errata.  We can leave it like this since we're close to the next rebase anyway.

I left a needinfo on you just to be my assumptions are good...

We'll also need the qa_ack+ and ITR being set in order to get release+

Comment 5 Yanan Fu 2022-12-19 02:21:27 UTC

QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass.

Comment 10 errata-xmlrpc 2023-05-09 07:20:51 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 (Moderate: qemu-kvm security, bug fix, and enhancement update), 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://access.redhat.com/errata/RHSA-2023:2162