Bug 1397697

Summary:	Backport remaining kvm_stat patches from the kernel to QEMU
Product:	Red Hat Enterprise Linux 7	Reporter:	David Hildenbrand <dhildenb>
Component:	qemu-kvm-rhev	Assignee:	David Hildenbrand <dhildenb>
Status:	CLOSED ERRATA	QA Contact:	Chao Yang <chayang>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	chayang, hhuang, juzhang, qzhang, virt-maint
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	qemu-kvm-rhev-2.8.0-3.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 23:39:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Hildenbrand 2016-11-23 08:23:03 UTC

The kvm_stat script has been moved from QEMU to the kernel in QEMU 2.7.0. As kvm_stat is shipped in RHEL 7.X via qemu-kvm-tools, Bug 1389238 moved the script back to QEMU, so we can continue shipping it via qemu-kvm-tools.

Let's backport the remaining upstream patches (from the kernel to QEMU).

These should include the following kernel commits:

f0cf040 tools: kvm_stat: Introduce pid monitoring
fabc712 tools: kvm_stat: Add comments

Comment 2 Miroslav Rezanina 2017-02-03 09:08:48 UTC

Fix included in qemu-kvm-rhev-2.8.0-3.el7

Comment 6 errata-xmlrpc 2017-08-01 23:39:45 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.

https://access.redhat.com/errata/RHSA-2017:2392

Comment 7 errata-xmlrpc 2017-08-02 01:17:23 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.

https://access.redhat.com/errata/RHSA-2017:2392

Comment 8 errata-xmlrpc 2017-08-02 02:09:23 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.

https://access.redhat.com/errata/RHSA-2017:2392

Comment 9 errata-xmlrpc 2017-08-02 02:50:09 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.

https://access.redhat.com/errata/RHSA-2017:2392

Comment 10 errata-xmlrpc 2017-08-02 03:14:52 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.

https://access.redhat.com/errata/RHSA-2017:2392

Comment 11 errata-xmlrpc 2017-08-02 03:35:00 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.

https://access.redhat.com/errata/RHSA-2017:2392