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 2026541 - [virtio-win][whql test]'Static Tools Logo Test' failed on Win2016, Win2019 and Win2012-64/r2
Summary: [virtio-win][whql test]'Static Tools Logo Test' failed on Win2016, Win2019 an...
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
urgent
high
Target Milestone: rc
: ---
Assignee: Kostiantyn Kostiuk
QA Contact: leidwang@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-25 03:21 UTC by leidwang@redhat.com
Modified: 2022-05-17 15:35 UTC (History)
7 users (show)

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

Attachments (Terms of Use)
DVL logs for Windows Server 2012/2016 (3.92 KB, application/zip)
2021-12-02 09:09 UTC, Kostiantyn Kostiuk 		no flags Details
DVL logs for Windows Server 2019 (4.21 KB, application/zip)
2021-12-02 09:10 UTC, Kostiantyn Kostiuk 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-103900 0 None None None 2021-11-25 03:22:08 UTC
Red Hat Product Errata RHBA-2022:3890 0 None None None 2022-05-17 15:35:36 UTC

Description leidwang@redhat.com 2021-11-25 03:21:41 UTC 
Description of problem:
For prewhql-214 whql testing,this job failed.

Version-Release number of selected component (if applicable):
kernel-5.14.0-9.el9.x86_64
qemu-kvm-6.1.0-5.el9.x86_64
virtio-win-prewhql-214

How reproducible:
100%

Steps to Reproduce:
1.boot up Win2016/2019
/usr/libexec/qemu-kvm -name 214NIC196435CGV -enable-kvm -m 6G -smp 16,cores=16 -uuid cef6a7e3-c403-4429-8ea6-a902119d6414 -nodefaults -cpu EPYC,hv_stimer,hv_synic,hv_time,hv_vpindex,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_frequencies,hv_runtime,hv_tlbflush,hv_reenlightenment,hv_stimer_direct,hv_ipi -chardev socket,id=charmonitor,path=/tmp/214NIC196435CGV,server=on,wait=off -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -boot order=cd,menu=on -device piix3-usb-uhci,id=usb -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=214NIC196435CGV,node-name=my_file -blockdev driver=raw,node-name=my,file=my_file -device ide-hd,drive=my,id=ide0-0-0,bus=ide.0,unit=0,bootindex=1 -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=/home/kvm_autotest_root/iso/ISO/Win2019/en_windows_server_2019_updated_may_2020_x64_dvd_5651846f.iso,node-name=my_cd,read-only=on -blockdev driver=raw,node-name=mycd,file=my_cd,read-only=on -device ide-cd,drive=mycd,id=ide0-1-0,bus=ide.1,bootindex=2 -cdrom /home/kvm_autotest_root/iso/windows/virtio-win-prewhql-0.1-214.iso -device usb-tablet,id=input0 -vnc 0.0.0.0:9 -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=/home/kvm_autotest_root/iso/windows/FOD.iso,node-name=my_iso,read-only=on -blockdev driver=raw,node-name=myiso,file=my_iso,read-only=on -device ide-cd,drive=myiso,id=ide0-1-1,bus=ide.4 -M q35 -device pcie-root-port,bus=pcie.0,id=root1.0,multifunction=on,port=0x10,chassis=1,addr=0x7 -device pcie-root-port,bus=pcie.0,id=root2.0,port=0x11,chassis=2,addr=0x7.0x1 -netdev tap,script=/etc/qemu-ifup1,downscript=no,id=hostnet0 -device e1000e,bus=root1.0,netdev=hostnet0,id=net0,mac=00:52:2d:2b:08:e5 -vga std -netdev tap,script=/etc/qemu-ifup-private,downscript=no,id=hostnet1,vhost=on,queues=16 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=00:52:1e:13:56:ec,bus=root2.0,mq=on,vectors=34

/usr/libexec/qemu-kvm -name 214NIC196435SGV -enable-kvm -m 6G -smp 16,cores=16 -uuid 2b886610-4527-425e-b35e-28a9b8ca1d5e -nodefaults -cpu EPYC,hv_stimer,hv_synic,hv_time,hv_vpindex,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_frequencies,hv_runtime,hv_tlbflush,hv_reenlightenment,hv_stimer_direct,hv_ipi -chardev socket,id=charmonitor,path=/tmp/214NIC196435SGV,server=on,wait=off -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -boot order=cd,menu=on -device piix3-usb-uhci,id=usb -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=214NIC196435SGV,node-name=my_file -blockdev driver=raw,node-name=my,file=my_file -device ide-hd,drive=my,id=ide0-0-0,bus=ide.0,unit=0,bootindex=1 -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=/home/kvm_autotest_root/iso/ISO/Win2019/en_windows_server_2019_updated_may_2020_x64_dvd_5651846f.iso,node-name=my_cd,read-only=on -blockdev driver=raw,node-name=mycd,file=my_cd,read-only=on -device ide-cd,drive=mycd,id=ide0-1-0,bus=ide.1,bootindex=2 -cdrom /home/kvm_autotest_root/iso/windows/virtio-win-prewhql-0.1-214.iso -device usb-tablet,id=input0 -vnc 0.0.0.0:8 -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=/home/kvm_autotest_root/iso/windows/FOD.iso,node-name=my_iso,read-only=on -blockdev driver=raw,node-name=myiso,file=my_iso,read-only=on -device ide-cd,drive=myiso,id=ide0-1-1,bus=ide.4 -M q35 -device pcie-root-port,bus=pcie.0,id=root1.0,multifunction=on,port=0x10,chassis=1,addr=0x7 -device pcie-root-port,bus=pcie.0,id=root2.0,port=0x11,chassis=2,addr=0x7.0x1 -netdev tap,script=/etc/qemu-ifup1,downscript=no,id=hostnet0 -device e1000e,bus=root1.0,netdev=hostnet0,id=net0,mac=00:52:20:3c:d2:10 -vga std -netdev tap,script=/etc/qemu-ifup-private,downscript=no,id=hostnet1,vhost=on,queues=16 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=00:52:0d:58:5a:c0,bus=root2.0,mq=on,vectors=34

2.submit 'Static Tools Logo Test' to hlk-1809

Error msg:
DVL test failed:

Microsoft.StaticToolsLogo.ObjectModel.DvlException: C:\dvl\netkvm.DVL.XML: DVL file format incorrect (netkvm.x64.Semmle.Summary).
   at Microsoft.StaticToolsLogo.ObjectModel.DvlChecker.CheckDvl()
   at DevfundTests.DvlTest.DvlCheck()

Actual results:
Job failed
Expected results:
Pass
Additional info:
Run this job with prewhql-207 and it passed.
Comment 1 Kostiantyn Kostiuk 2021-11-25 13:04:42 UTC 
The error occurred because netkvm.DVL.XML was built using EWDK11 with CodeQL results, but Windows Server 2016/2019 expects to have valid DVL.XML without CodeQL results.
Comment 2 yimsong 2021-11-29 02:27:07 UTC 
Hit the same issue on win2012 and win2012r2, and they have same error message.

Err msg:

DVL test failed: 
Microsoft.StaticToolsLogo.ObjectModel.DvlException: C:\dvl\netkvm_DVL.XML: DVL file format incorrect (netkvm.x64.Semmle.Summary). 
at Microsoft.StaticToolsLogo.ObjectModel.DvlChecker.CheckDvl() 
at DevfundTests.DvlTest.DvlCheck()

pkg version:

kernel-5.14.0-11.el9.x86_64
qemu-kvm-6.1.0-6.el9.x86_64
virtio-win-prewhql-214
Comment 9 Peixiu Hou 2021-12-02 05:14:58 UTC 
Hi Konstantin,

We also hit the same issue for vioscsi build 214 whql testing, and used the vioscsi.DVL.XML file for your provide on Win2019, the static job can be passed, but on Win2012-64/r2 and Win2016, all failed as well, error as:

DVL test failed: Microsoft.StaticToolsLogo.ObjectModel.DvlException: C:\dvl\vioscsi.DVL.XML: DVL file format incorrect (vioscsi.x64.General.Checksum). at Microsoft.StaticToolsLogo.ObjectModel.DvlChecker.CheckDvl() at DevfundTests.DvlTest.DvlCheck()

Could you help to check it?

Thanks~
Peixiu
Comment 10 menli@redhat.com 2021-12-02 07:01:34 UTC 
(In reply to Peixiu Hou from comment #9)
> Hi Konstantin,
> 
> We also hit the same issue for vioscsi build 214 whql testing, and used the
> vioscsi.DVL.XML file for your provide on Win2019, the static job can be
> passed, but on Win2012-64/r2 and Win2016, all failed as well, error as:

The same result as viostor.

> DVL test failed: Microsoft.StaticToolsLogo.ObjectModel.DvlException:
> C:\dvl\vioscsi.DVL.XML: DVL file format incorrect
> (vioscsi.x64.General.Checksum). at
> Microsoft.StaticToolsLogo.ObjectModel.DvlChecker.CheckDvl() at
> DevfundTests.DvlTest.DvlCheck()
> 
> Could you help to check it?
> 
> Thanks~
> Peixiu
Comment 11 Kostiantyn Kostiuk 2021-12-02 09:09:53 UTC 
Created attachment 1844436 [details]
DVL logs for Windows Server 2012/2016
Comment 12 Kostiantyn Kostiuk 2021-12-02 09:10:23 UTC 
Created attachment 1844437 [details]
DVL logs for Windows Server 2019
Comment 13 Kostiantyn Kostiuk 2021-12-02 09:12:42 UTC 
Hi Peixiu,

I attached two ZIP archives with DVL files for Windows Server 2012/2016 and for Windows Server 2019.

Please check these files.

Thanks,
Konstantin
Comment 14 leidwang@redhat.com 2021-12-02 10:15:50 UTC 
(In reply to Kostiantyn Kostiuk from comment #11)
> Created attachment 1844436 [details]
> DVL logs for Windows Server 2012/2016

Used this dvl file,rerun the job on win2016/2012/2012r2,all passed.
Comment 15 menli@redhat.com 2021-12-03 01:27:43 UTC 
use the lastest dvl, the job on win2016/2012/2012r2 for viostor can pass.
Comment 16 Peixiu Hou 2021-12-03 01:38:34 UTC 
(In reply to Kostiantyn Kostiuk from comment #13)
> Hi Peixiu,
> 
> I attached two ZIP archives with DVL files for Windows Server 2012/2016 and
> for Windows Server 2019.
> 
> Please check these files.
> 
Hi Konstantin, 

This job can be passed with the new vioscsi.DVL file on win2012-64/r2 and win2016.

Thanks~
Peixiu

> Thanks,
> Konstantin
Comment 22 menli@redhat.com 2022-02-21 07:34:51 UTC 
Test viostor job 'Static Tools Logo Test'  with 216 build passed on Win2016, Win2019 and Win2012-64/r2
Comment 23 Peixiu Hou 2022-02-22 15:53:56 UTC 
Tested this job with vioscsi on Win2012-64/r2, Win2016, Win2019, Win2022 guests, all passed.

Detail status as follows:
1. For Win2012-64/R2, Win2016:
   Passed only with renaming vioscsi_DVL_compat.xml to vioscsi.DVL.xml file.
2. For Win2019:
   Passed only with renaming vioscsi_DVL_win10.xml to vioscsi.DVL.xml file.
3. For Win2022:
   Passed with default vioscsi_DVL.xml file.

Thanks~
Peixiu
Comment 24 leidwang@redhat.com 2022-02-23 06:43:02 UTC 
Tested this job with netkvm on Win2012-64/r2, Win2016, Win2019, Win2022 guests, all passed.
Move this bz to verified according to comment22 and comment23. Thanks!
Comment 27 errata-xmlrpc 2022-05-17 15:35:27 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.