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.
Descriptionmenli@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):
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
Comment 1Yvugenfi@redhat.com
2021-07-01 11:35:35 UTC