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 1969372 - [virtio-win][whql test] 'Static Tools Logo Test' on ws2022 still fail used existing dvl file
Summary: [virtio-win][whql test] 'Static Tools Logo Test' on ws2022 still fail used ex...
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virtio-win
Version: 9.0
Hardware: x86_64
OS: Windows
Target Milestone: rc
: 9.0
Assignee: Yvugenfi@redhat.com
QA Contact: menli@redhat.com
Depends On: 1978242 1978249 1978262
Blocks: 1967854 1968312 1968315 2057757
TreeView+ depends on / blocked
Reported: 2021-06-08 10:08 UTC by menli@redhat.com
Modified: 2022-11-08 01:44 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-11-08 01:44:26 UTC
Type: ---
Target Upstream Version:

Attachments (Terms of Use)

Description menli@redhat.com 2021-06-08 10:08:54 UTC
Description of problem:
For vioscsi/viostor, this job also failed used existing dvl file.

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

How reproducible:

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

Comment 2 leidwang@redhat.com 2021-09-27 05:29:19 UTC
Test virtio-win-prewhql-210 on Win2022/Win11.This job passed.
So set the status to VERIFIED.Thanks.

Note You need to log in before you can comment on or make changes to this bug.