RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2073867 - Missing the doc of dirtyrate.calc_mode and dirtyrate.vcpu.<num>.megabytes_per_second
Summary: Missing the doc of dirtyrate.calc_mode and dirtyrate.vcpu.<num>.megabytes_per...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Peter Krempa
QA Contact: zhentang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-11 01:38 UTC by Lili Zhu
Modified: 2022-11-15 10:39 UTC (History)
7 users (show)

Fixed In Version: libvirt-8.3.0-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 10:04:06 UTC
Type: Bug
Target Upstream Version: 8.3.0
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-118493 0 None Closed ubi8/httpd-24 mod_mellon suffers from unpatched security issues 2022-06-08 07:27:50 UTC
Red Hat Product Errata RHSA-2022:8003 0 None None None 2022-11-15 10:04:26 UTC

Description Lili Zhu 2022-04-11 01:38:16 UTC 
Description of problem:
Missing the doc of dirtyrate.calc_mode and dirtyrate.vcpu.<num>.megabytes_per_second

Version-Release number of selected component (if applicable):
libvirt-8.2.0-1.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Check the doc of virsh
# man virsh
...
domstats
       Syntax:
...
  --dirtyrate returns:

       • dirtyrate.calc_status - the status of last memory dirty rate calculation, returned as number from virDomainDirtyRateStatus enum.

       • dirtyrate.calc_start_time - the start time of last memory dirty rate calculation.

       • dirtyrate.calc_period - the period of last memory dirty rate calculation.

       • dirtyrate.megabytes_per_second - the calculated memory dirty rate in MiB/s.

       Selecting a specific statistics groups doesn't guarantee that the daemon supports the selected group of stats. Flag --enforce forces the command to fail if the daemon
       doesn't support the selected group.



Actual results:
Missing the doc of dirtyrate.calc_mode and dirtyrate.vcpu.<num>.megabytes_per_second

Expected results:


Additional info:
Comment 1 Peter Krempa 2022-04-13 11:08:35 UTC 
Fixed upstream:

commit 67263604e60fbefe3b85560b81001e18a1e39533
Author: Peter Krempa <pkrempa>
Date:   Tue Apr 12 14:05:39 2022 +0200

    docs: man: Add description of 'calc_mode' and 'vcpu.<num>.megabytes_per_second' dirtyrate mode
    
    Commit 42d36b65a31 added new fields to the API docs but didn't add the
    virsh man page equivalent.
    
    Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2073867
    Signed-off-by: Peter Krempa <pkrempa>
    Reviewed-by: Ján Tomko <jtomko>

v8.2.0-143-g67263604e6
Comment 4 zhentang 2022-05-23 03:51:50 UTC 
Verified

version libvirt-8.3.0-1.el9

1. Check the doc of virsh
# man virsh

 --dirtyrate returns:

       • dirtyrate.calc_status - the status of last memory dirty rate calcula‐
         tion, returned as number from virDomainDirtyRateStatus enum.

       • dirtyrate.calc_start_time - the start time of last memory dirty  rate
         calculation.

       • dirtyrate.calc_period - the period of last memory dirty rate calcula‐
         tion.

       • dirtyrate.megabytes_per_second - the calculated memory dirty rate  in
         MiB/s.

       • dirtyrate.calc_mode  -  the  calculation  mode  used last measurement
         (page-sampling/dirty-bitmap/dirty-ring)

       • dirtyrate.vcpu.<num>.megabytes_per_second  -  the  calculated  memory
         dirty rate for a virtual cpu in MiB/s
Comment 6 errata-xmlrpc 2022-11-15 10:04:06 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 (Low: libvirt 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-2022:8003
Note You need to log in before you can comment on or make changes to this bug.