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 1967854 - [virtio-win][whql test] need dvl file to pass 'Static Tools Logo Test' on ws2022
Summary: [virtio-win][whql test] need dvl file to pass 'Static Tools Logo Test' on ws2022
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virtio-win
Version: 9.0
Hardware: x86_64
OS: Windows
high
medium
Target Milestone: rc
: 9.0
Assignee: Yvugenfi@redhat.com
QA Contact: xiagao
URL:
Whiteboard:
Depends On: 1969372 1979290
Blocks: 1968312 1968315 2057757
TreeView+ depends on / blocked
 
Reported: 2021-06-04 08:35 UTC by xiagao
Modified: 2022-05-17 15:36 UTC (History)
8 users (show)

Fixed In Version: virtio-win-prewhql-0.1-211
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 15:35:26 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2022:3890 0 None None None 2022-05-17 15:36:12 UTC

Description xiagao 2021-06-04 08:35:06 UTC 
Description of problem:
All drivers need dvl file to pass 'Static Tools Logo Test' on ws2022, currently netkvm/vioscsi/viostor have this file already.

Version-Release number of selected component (if applicable):
kernel-4.18.0-310.el8.x86_64
qemu-kvm-6.0.0-17.module+el8.5.0+11173+c9fce0bb.x86_64
virtio-win-prewhql-199

How reproducible:
100%

Steps to Reproduce:
1.boot up ws2022 with virtio device(q35)
2.submit Static Tools Logo Test to hlk-2022


Actual results:
Failed as no dvl file in c:\dvl.

Copy netkvm dvl and rename it,still fail.
Microsoft.StaticToolsLogo.ObjectModel.DvlException: DvlChecker: missing Semmle DVL log content for driver 'balloon' with the OS architecture 'x64'.
   at Microsoft.StaticToolsLogo.ObjectModel.DvlChecker.CheckDvl(dvlTypes dvlTypes)
   at DevfundTests.DvlTest.DvlCheck(dvlTypes dvlTypes)

So maybe we need build new ones.

Expected results:
PASS this case

Additional info:
Comment 1 Peixiu Hou 2021-06-05 14:33:27 UTC 
For vioscsi, this job also failed used existed vioscsi.dvl file, tried vioscsi.DVL and vioscsi.DVL-compat, both failed.
And tried test with build 199 and build 200, both reproduce this issue.

Report error as:
--------------------------------------------------------------------------------------------------------------------------------------------------
DVL test failed:

Microsoft.StaticToolsLogo.ObjectModel.DvlException: DvlChecker: missing Semmle DVL log content for driver 'vioscsi' with the OS architecture 'x64'.
   at Microsoft.StaticToolsLogo.ObjectModel.DvlChecker.CheckDvl(dvlTypes dvlTypes)
   at DevfundTests.DvlTest.DvlCheck(dvlTypes dvlTypes)
 WexTraceInfo ThreadId=6024 ProcessId=6720 TimeStamp=62151298984 LogSessionId=1 SessionTraceCount=69  


Used versions:
Guest os: Windows 2022
kernel-4.18.0-310.el8.x86_64
qemu-kvm-6.0.0-18.module+el8.5.0+11243+5269aaa1.x86_64
seabios-bin-1.14.0-1.module+el8.4.0+8855+a9e237a9.noarch
virtio-win-prewhql-199/200

Thanks~
Peixiu
Comment 2 menli@redhat.com 2021-06-08 03:24:26 UTC 
viostor hit the same issue with vioscsi as comment1
Comment 3 Yvugenfi@redhat.com 2021-06-08 06:04:48 UTC 
(In reply to menli from comment #2)
> viostor hit the same issue with vioscsi as comment1

Please create additional BZ for the failure with exiting DVL files
Comment 4 dehanmeng 2021-06-08 08:31:16 UTC 
vioser hit the same issue with vioscsi as comment1
Comment 5 menli@redhat.com 2021-06-08 10:11:56 UTC 
(In reply to Yvugenfi from comment #3)
> (In reply to menli from comment #2)
> > viostor hit the same issue with vioscsi as comment1
> 
> Please create additional BZ for the failure with exiting DVL files

Thanks, file a separated bz https://bugzilla.redhat.com/show_bug.cgi?id=1969372
Comment 6 dehanmeng 2021-06-08 12:38:27 UTC 
(In reply to dehanmeng from comment #4)
> vioser hit the same issue with vioscsi as comment1

After confirmation that vioser hit the issue should be as comment0.
Comment 7 leidwang@redhat.com 2021-06-10 00:37:59 UTC 
Pvpanic hit same issue as comment1


DVL test failed:

Microsoft.StaticToolsLogo.ObjectModel.DvlException: C:\dvl: no DVL files were found.
   at Microsoft.StaticToolsLogo.ObjectModel.DvlChecker.CheckDvl(dvlTypes dvlTypes)
   at DevfundTests.DvlTest.DvlCheck(dvlTypes dvlTypes)
 WexTraceInfo ThreadId=7036 ProcessId=4796 TimeStamp=548332930 LogSessionId=1 SessionTraceCount=69
Comment 8 leidwang@redhat.com 2021-06-10 00:54:18 UTC 
(In reply to leidwang from comment #7)
> Pvpanic hit same issue as comment1
> 
Sorry, Pvpanic's issue is the same as comment0
> 
> DVL test failed:
> 
> Microsoft.StaticToolsLogo.ObjectModel.DvlException: C:\dvl: no DVL files
> were found.
>    at Microsoft.StaticToolsLogo.ObjectModel.DvlChecker.CheckDvl(dvlTypes
> dvlTypes)
>    at DevfundTests.DvlTest.DvlCheck(dvlTypes dvlTypes)
>  WexTraceInfo ThreadId=7036 ProcessId=4796 TimeStamp=548332930
> LogSessionId=1 SessionTraceCount=69
Comment 9 Yvugenfi@redhat.com 2021-06-10 08:51:33 UTC 
The new MS policy is to have SDV (DLV) logs for all the drivers:
Device.DevFund.StaticTools.CAandSDV

Driver development includes static analysis to improve reliability using Code Analysis (CA) and Static Driver Verifier (SDV).

Applies to Windows Server 2022 x64

Description

Kernel-mode driver submissions are required to pass the Static Tools Logo Test for certification. The following technologies and tools are what must be used for static analysis of a kernel-mode driver for submission to Microsoft for signature or certification; Static Driver Verifier (SDV), Code Analysis for Drivers (CA), and CodeQL. For driver certification, passing log files from the above static analysis tools are required. See the below table for which tools are required for each certification program.
Comment 10 leidwang@redhat.com 2021-06-17 07:11:17 UTC 
Netkvm hit same issue as comment1

Error msg:
DVL test failed:

Microsoft.StaticToolsLogo.ObjectModel.DvlException: DvlChecker: missing Semmle DVL log content for driver 'netkvm' with the OS architecture 'x64'.
   at Microsoft.StaticToolsLogo.ObjectModel.DvlChecker.CheckDvl(dvlTypes dvlTypes)
   at DevfundTests.DvlTest.DvlCheck(dvlTypes dvlTypes)
Comment 11 Peixiu Hou 2021-07-07 08:11:46 UTC 
Also need DVL file for fwcfg64 driver.

Hit the same issue when run whql test on win2022 with fwcfg64 driver.

DVL test failed:

Microsoft.StaticToolsLogo.ObjectModel.DvlException: C:\dvl: no DVL files were found.
   at Microsoft.StaticToolsLogo.ObjectModel.DvlChecker.CheckDvl(dvlTypes dvlTypes)
   at DevfundTests.DvlTest.DvlCheck(dvlTypes dvlTypes)
Comment 12 Yvugenfi@redhat.com 2021-07-07 13:27:33 UTC 
PR to enable DVL creation: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/594

Still, SDV errors are not fixed for all the drives and CodeQL results are not included in SDV file.
Comment 14 xiagao 2021-08-26 02:42:26 UTC 
win11-64 also hit the same issue with Balloon as comment0.
Do we need to open a new bz to track?

driver: virtio-win-prewhql-0.1-207
Comment 15 lijin 2021-08-26 03:13:02 UTC 
(In reply to xiagao from comment #14)
> win11-64 also hit the same issue with Balloon as comment0.
> Do we need to open a new bz to track?

Yes, pls.
We track win11 and win2022 separately, and pls set new bug a block for bz1993779 as well

> driver: virtio-win-prewhql-0.1-207
Comment 16 xiagao 2021-08-26 03:19:36 UTC 
(In reply to lijin from comment #15)
> (In reply to xiagao from comment #14)
> > win11-64 also hit the same issue with Balloon as comment0.
> > Do we need to open a new bz to track?
> 
> Yes, pls.
> We track win11 and win2022 separately, and pls set new bug a block for
> bz1993779 as well

OK, cancel the needinfo accordingly.
> 
> > driver: virtio-win-prewhql-0.1-207
Comment 22 xiagao 2021-09-16 02:23:13 UTC 
Test virtio-win-prewhql-210.
Still failed on win11-64 guest.

DVL test failed:

Microsoft.StaticToolsLogo.ObjectModel.DvlException: DvlChecker: missing Semmle DVL log content for driver 'viohidkmdf' with the OS architecture 'x64'.
   at Microsoft.StaticToolsLogo.ObjectModel.DvlChecker.CheckDvl(dvlTypes dvlTypes)
   at DevfundTests.DvlTest.DvlCheck(dvlTypes dvlTypes)
Comment 23 Yvugenfi@redhat.com 2021-09-19 06:26:51 UTC 
(In reply to xiagao from comment #22)
> Test virtio-win-prewhql-210.
> Still failed on win11-64 guest.
> 
> DVL test failed:
> 
> Microsoft.StaticToolsLogo.ObjectModel.DvlException: DvlChecker: missing
> Semmle DVL log content for driver 'viohidkmdf' with the OS architecture
> 'x64'.
>    at Microsoft.StaticToolsLogo.ObjectModel.DvlChecker.CheckDvl(dvlTypes
> dvlTypes)
>    at DevfundTests.DvlTest.DvlCheck(dvlTypes dvlTypes)

Thanks, I will take a look.
Comment 24 leidwang@redhat.com 2021-09-23 08:57:44 UTC 
Test virtio-win-prewhql-210.

virtio-input/viofs/fwcfg64 still failed,others all pass.

virtio-input：
DVL test failed:

Microsoft.StaticToolsLogo.ObjectModel.DvlException: DvlChecker: missing Semmle DVL log content for driver 'viohidkmdf' with the OS architecture 'x64'.
   at Microsoft.StaticToolsLogo.ObjectModel.DvlChecker.CheckDvl(dvlTypes dvlTypes)
   at DevfundTests.DvlTest.DvlCheck(dvlTypes dvlTypes)

viofs/fwcfg64：
DVL test failed:

Microsoft.StaticToolsLogo.ObjectModel.DvlException: DvlChecker: missing SDV DVL log content for driver 'driver[translate(isinbox/text(),'falsetru','falsetru')=' with the OS architecture 'x64'.
   at Microsoft.StaticToolsLogo.ObjectModel.DvlChecker.CheckDvl(dvlTypes dvlTypes)
   at DevfundTests.DvlTest.DvlCheck(dvlTypes dvlTypes)
Comment 25 leidwang@redhat.com 2021-09-23 09:01:02 UTC 
(In reply to leidwang from comment #24)
> Test virtio-win-prewhql-210.
> 
> virtio-input/viofs/fwcfg64 still failed,others all pass.
> 
> virtio-input：
> DVL test failed:
> 
> Microsoft.StaticToolsLogo.ObjectModel.DvlException: DvlChecker: missing
> Semmle DVL log content for driver 'viohidkmdf' with the OS architecture
> 'x64'.
>    at Microsoft.StaticToolsLogo.ObjectModel.DvlChecker.CheckDvl(dvlTypes
> dvlTypes)
>    at DevfundTests.DvlTest.DvlCheck(dvlTypes dvlTypes)
> 
> viofs/fwcfg64：
> DVL test failed:
> 
> Microsoft.StaticToolsLogo.ObjectModel.DvlException: DvlChecker: missing SDV
> DVL log content for driver
> 'driver[translate(isinbox/text(),'falsetru','falsetru')=' with the OS
> architecture 'x64'.
>    at Microsoft.StaticToolsLogo.ObjectModel.DvlChecker.CheckDvl(dvlTypes
> dvlTypes)
>    at DevfundTests.DvlTest.DvlCheck(dvlTypes dvlTypes)

Test virtio-win-prewhql-210 on Win2022.
Comment 26 Yvugenfi@redhat.com 2021-09-23 13:37:23 UTC 
https://github.com/virtio-win/kvm-guest-drivers-windows/pull/658
Comment 27 dehanmeng 2021-10-11 11:46:56 UTC 
the issue is still there with virtio-win-prewhql-0.1-211 for driver Virtio-serial on win2022.

the error info from log : [HRESULT 0x8007007E] Failed to load 'C:\HLK\JobsWorkingDir\Tasks\WTTJobRun729D9E47-1229-EC11-995C-0052253A9E00\Devfund_DvlTest.dll'. (Could not load managed test module because RoMetadata.dll could not be found. Make sure the TAEF package is deployed or RoMetadata.dll is deployed to a location in your PATH environment variable.)

Is it the same issue or derived issue?
Comment 28 Peixiu Hou 2021-10-12 01:06:16 UTC 
Tested this job with virtio-input/fwcfg and virtio-win-prewhql-211 version on Win11/Win2022, all passed.

Thanks~
Peixiu
Comment 29 menli@redhat.com 2021-10-12 01:29:59 UTC 
Tested this job with rng/blk with virtio-win-prewhql-211 version on Win11/Win2022, all passed.


Thanks
Menghuan
Comment 30 xiagao 2021-10-12 05:54:13 UTC 
(In reply to menli from comment #29)
> Tested this job with rng/blk with virtio-win-prewhql-211 version on
> Win11/Win2022, all passed.
> 
> 
> Thanks
> Menghuan

Balloon and virtiofs also passed.
Comment 31 dehanmeng 2021-10-12 07:31:34 UTC 
after install GUI win2022 and copy vioser.DVL file to C:\dvl, the case gets passed.
Comment 32 leidwang@redhat.com 2021-10-13 01:11:27 UTC 
Tested this job with pvpanic/netkvm and virtio-win-prewhql-211 version on Win11/Win2022, all passed.Thanks!
Comment 33 xiagao 2021-10-14 02:24:17 UTC 
(In reply to Peixiu Hou from comment #28)
> Tested this job with virtio-input/fwcfg and virtio-win-prewhql-211 version
> on Win11/Win2022, all passed.
> 
> Thanks~
> Peixiu

Phou,is scsi passed on this job?
Comment 34 xiagao 2021-10-14 02:30:48 UTC 
(In reply to dehanmeng from comment #31)
> after install GUI win2022 and copy vioser.DVL file to C:\dvl, the case gets
> passed.

Demeng, is GPU need to run this case? If yes,is it passed ?
Comment 35 Peixiu Hou 2021-10-14 02:38:16 UTC 
(In reply to xiagao from comment #33)
> (In reply to Peixiu Hou from comment #28)
> > Tested this job with virtio-input/fwcfg and virtio-win-prewhql-211 version
> > on Win11/Win2022, all passed.
> > 
> > Thanks~
> > Peixiu
> 
> Phou,is scsi passed on this job?

Sure, It's passed for vioscsi. 
Due to the vioscsi tracked on bug https://bugzilla.redhat.com/show_bug.cgi?id=1969372, it's has been verified, so I did not paste this info.

BR~
Peixiu
Comment 36 dehanmeng 2021-10-14 02:41:20 UTC 
(In reply to xiagao from comment #34)
> (In reply to dehanmeng from comment #31)
> > after install GUI win2022 and copy vioser.DVL file to C:\dvl, the case gets
> > passed.
> 
> Demeng, is GPU need to run this case? If yes,is it passed ?

yes, viogpudo driver has this case 'Static Tools Logo Test', and it passed.
Comment 37 xiagao 2021-10-14 02:55:03 UTC 
Based on above comment,this bz is fixed on virtio-win-prewhql-211 version.
So change status to verify.
Comment 40 errata-xmlrpc 2022-05-17 15:35:26 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 (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
Note You need to log in before you can comment on or make changes to this bug.