Bug 2157095
| Summary: | Backport the qemuDomainGetStatsCpu fallback Implementation [rhel-9.0.0.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | RHEL Program Management Team <pgm-rhel-tools> |
| Component: | libvirt | Assignee: | Michal Privoznik <mprivozn> |
| libvirt sub component: | General | QA Contact: | Luyao Huang <lhuang> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | alitman, jdenemar, jsuchane, jvilaca, kbidarka, kmajcher, lhuang, lmen, lpivarc, pkrempa, sgott, sradco, virt-maint, yalzhang, ymankad |
| Version: | 9.1 | Keywords: | AutomationBackLog, Triaged, ZStream |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | libvirt-8.0.0-8.5.el9_0 | Doc Type: | Enhancement |
| Doc Text: |
Feature:
When fetching statistics for a running QEMU guest, libvirt looks into CGroups and fetches some statistics from there (e.g. on CPU usage). However, this is not possible for session mode because there libvirt does not have permissions to even place QEMU into CGroups. Therefore, a workaround needs to be implemented where stats are fetched from a different source (procfs).
Reason:
Result:
|
Story Points: | --- |
| Clone Of: | 2148266 | Environment: | |
| Last Closed: | 2023-01-30 15:46:01 UTC | Type: | --- |
| 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: | 2148266 | ||
| Bug Blocks: | |||
|
Comment 5
Luyao Huang
2023-01-09 07:04:59 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 (libvirt bug fix 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/RHBA-2023:0521 |