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.

Description of problem:
Microsoft added additional requirements for static code analysis tools. For Windows Server 2022 DLV log should include also CodeQL test results: https://securitylab.github.com/tools/codeql/ .
DVL log that includes CodeQL results can be only created with WDK for Windows Server 2022 and up. 

There are several failures in virtio-win drivers that must be fixed.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

'Static Tools Logo Test' in HCK should pass for all the drivers.

Testing virtio-win-prewhql-0.1-210 on win11.

Except vioinput driver, others all pass.
Failed info refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1967854#c22

reassign according to comment#2

Test virtio-win-prewhql-210 on Win2022.
virtio-input/viofs/fwcfg64 still failed,others all pass.

https://github.com/virtio-win/kvm-guest-drivers-windows/pull/658

Moving to VERIFIED per https://bugzilla.redhat.com/show_bug.cgi?id=1967854#c37 'Static Tools Logo Test' pass for all the drivers.

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 (new packages: virtio-win), 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-2022:3890