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.

We are currently running code analysis once a week automatically, an email notifications containing runlogs will be sent in case of failures.
for drivers other than virtio-net, virtio-block and virtio-scsi:
static driver verifier is run with "no legacy" option.

current known failures:
viosock and viofs drivers show some errors that will be checked with driver developers.

Hi Basil,
How could QE verify this bz?

There is no verification needed from QE side as no changes we're made to upstream repository.

SDV tests are being run once a week, on upstream repository,
tests each device driver are being run separately.
In case of any failures the CI will send automatic emails to the relevant owner.

No changes were made to upstream repository or the released drivers.

The code related changes are in virtio-win-prewql 190 : https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1383208

Set status to verified according to comment#9

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 (virtio-win 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/RHEA-2021:0535