Bug 1969372

Description of problem:
For vioscsi/viostor, this job also failed used existing dvl file.

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 used existing dvl file.


Expected results:
PASS this case

Additional info:

phou mentioned on https://bugzilla.redhat.com/show_bug.cgi?id=1967854#c1

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