Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
(In reply to Kostiantyn Kostiuk from comment #2)
> @jferlan
>
> This is a Linux bug, not Windows. The guest-get-diskstats command works only
> in Linux.
Fair enough - I hadn't realized you took over upstream maintainer for both Linux and Windows QGA...
Anyway you moved this bug to POST and set ITR, but didn't note the commit id for the patches.
If I grep thru qemu.git, I see commit id 3569664ee9f08c94a5a2c69f778f0d023e5e882f so I will assume that and fix the bug up to add some necessary data (see devel whiteboard and depends on bug for the qemu-7.2 rebase).
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.
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