Bug 1389238
| Summary: | Re-enable kvm_stat script | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Miroslav Rezanina <mrezanin> |
| Component: | qemu-kvm-rhev | Assignee: | Danilo de Paula <ddepaula> |
| Status: | CLOSED ERRATA | QA Contact: | Chao Yang <chayang> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.4 | CC: | chayang, juzhang, knoel, virt-maint, xfu |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | qemu-kvm-rhev-2.8.0-2.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 23:37:14 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1387600 | ||
|
Description
Miroslav Rezanina
2016-10-27 08:58:42 UTC
Fix included in qemu-kvm-rhev-2.8.0-2.el7 Verified pass with qemu-kvm-tools-rhev-2.9.0-2.el7.x86_64 # rpm -ql qemu-kvm-tools-rhev-2.9.0-2.el7.x86_64 /usr/bin/kvm_stat /usr/share/man/man1/kvm_stat.1.gz /usr/share/qemu-kvm/tscdeadline_latency.flat # kvm_stat -1 kvm_ack_irq 18 18 kvm_age_page 0 0 kvm_apic 0 0 kvm_apic_accept_irq 0 0 kvm_apic_ipi 0 0 kvm_async_pf_completed 0 0 kvm_async_pf_doublefault 0 0 kvm_async_pf_not_present 0 0 kvm_async_pf_ready 0 0 kvm_avic_incomplete_ipi 0 0 kvm_avic_unaccelerated_access 0 0 kvm_cpuid 0 0 kvm_cr 590 590 kvm_emulate_insn 140202 140202 kvm_enter_smm 0 0 kvm_entry 141414 141414 kvm_eoi 0 0 kvm_exit 141414 141414 Setting VERIFIED accordingly 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 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 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 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 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 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 |