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 1979022 - [virtio-win][whql test] 'NICStrictPropertyValidation' on Win2022 failed - *JumboPacket standard parameter validation failure
Summary: [virtio-win][whql test] 'NICStrictPropertyValidation' on Win2022 failed - *Ju...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: virtio-win
Version: 8.5
Hardware: Unspecified
OS: Windows
unspecified
high
Target Milestone: beta
: ---
Assignee: Yvugenfi@redhat.com
QA Contact: leidwang@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1968315 1973022 2057757
TreeView+ depends on / blocked
 
Reported: 2021-07-04 11:06 UTC by Yvugenfi@redhat.com
Modified: 2022-02-24 02:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-09 18:52:47 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2021:4341 0 None None None 2021-11-09 18:53:27 UTC

Description Yvugenfi@redhat.com 2021-07-04 11:06:33 UTC 
Description of problem:
For Win2022 whql testing,this job will failed.

There are three different failures in the logs. I am opening separate BZs to address them.

This BZ is for the failure of the *JumboPacket standard parameter validation:
[FAIL] *JumboPacket NumericParameterMaxValue is -ge 9014

Version-Release number of selected component (if applicable):
kernel-4.18.0-308.el8.x86_64
qemu-kvm-6.0.0-16.module+el8.5.0+10848+2dccc46d.x86_64
virtio-win-prewhql-199

How reproducible:
100%

Steps to Reproduce:
1.boot up ws2022
/usr/libexec/qemu-kvm -name 199NIC226435C0J -enable-kvm -m 6G -smp 8 -uuid f4c7ee00-3457-402d-8346-6fa32183e36f -nodefaults -cpu Skylake-Server,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/199NIC226435C0J,server,nowait -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=199NIC226435C0J,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 -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=/home/kvm_autotest_root/iso/ISO/Win2022/Windows_InsiderPreview_Server_vNext_en-us_20344.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,unit=0 -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=199NIC226435C0J.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 -device usb-tablet,id=input0 -vnc 0.0.0.0:0 -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:6c:3e:8c:2a -vga std -netdev tap,script=/etc/qemu-ifup-private,downscript=no,id=hostnet1,vhost=on,queues=8 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=00:52:32:17:be:4a,bus=root2.0,mq=on,vectors=18

/usr/libexec/qemu-kvm -name 199NIC226435S0J -enable-kvm -m 6G -smp 8 -uuid 884bc217-08de-47c3-9bf1-808d3632736c -nodefaults -cpu Skylake-Server,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/199NIC226435S0J,server,nowait -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=199NIC226435S0J,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 -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=/home/kvm_autotest_root/iso/ISO/Win2022/Windows_InsiderPreview_Server_vNext_en-us_20344.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,unit=0 -blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=199NIC226435S0J.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 -device usb-tablet,id=input0 -vnc 0.0.0.0:1 -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:61:2b:4d:e8 -vga std
Comment 1 Yvugenfi@redhat.com 2021-07-06 13:12:58 UTC 
From MS requirement document - Devices and Components WHCP Requirements for Windows Server 2022:


Device.Network.LAN.MTUSize

Applies to Windows Server 2022 x64

Description
Ethernet devices must support Jumbo Frames. MTU values in the User Interface must include the Ethernet header size of 14 Bytes. The “*JumboPacket” standardized keyword in the Windows Registry is currently used for setting the MTU size and should remain as an enumerable value with supported values being 1514, 4088, and 9014.
Comment 2 Yvugenfi@redhat.com 2021-07-14 11:29:27 UTC 
Upstream PR: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/599
Comment 3 Yvugenfi@redhat.com 2021-07-20 09:27:04 UTC 
(In reply to Yvugenfi from comment #2)
> Upstream PR: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/599

Actually, the bug is in Microsoft test: https://github.com/microsoft/Test-NetHLK/pull/2
Comment 4 Yvugenfi@redhat.com 2021-07-29 08:49:14 UTC 
(In reply to Yvugenfi from comment #3)
> (In reply to Yvugenfi from comment #2)
> > Upstream PR: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/599
> 
> Actually, the bug is in Microsoft test:
> https://github.com/microsoft/Test-NetHLK/pull/2

PR was accepted and MS released a new version of the test, please make sure that new version NICStrictPropertyValidation is installed and re-test.
Comment 5 leidwang@redhat.com 2021-07-29 10:51:14 UTC 
(In reply to Yvugenfi from comment #4)
> (In reply to Yvugenfi from comment #3)
> > (In reply to Yvugenfi from comment #2)
> > > Upstream PR: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/599
> > 
> > Actually, the bug is in Microsoft test:
> > https://github.com/microsoft/Test-NetHLK/pull/2
> 
> PR was accepted and MS released a new version of the test, please make sure
> that new version NICStrictPropertyValidation is installed and re-test.

Re-test this job with virtio-win-prewhql-0.1-205.iso and it passed.Thanks.
Comment 7 Yvugenfi@redhat.com 2021-07-29 12:21:49 UTC 
(In reply to leidwang from comment #5)
> (In reply to Yvugenfi from comment #4)
> > (In reply to Yvugenfi from comment #3)
> > > (In reply to Yvugenfi from comment #2)
> > > > Upstream PR: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/599
> > > 
> > > Actually, the bug is in Microsoft test:
> > > https://github.com/microsoft/Test-NetHLK/pull/2
> > 
> > PR was accepted and MS released a new version of the test, please make sure
> > that new version NICStrictPropertyValidation is installed and re-test.
> 
> Re-test this job with virtio-win-prewhql-0.1-205.iso and it passed.Thanks.

Then, you can move the BZ to verified. The fix is in the test, not in the driver.
Also, BZ#1973022 can be moved to verified in this case.
Comment 8 leidwang@redhat.com 2021-07-29 13:26:35 UTC 
According to comment5 and comment7, move the BZ to verified.
Comment 11 errata-xmlrpc 2021-11-09 18:52:47 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 (virtio-win bug fix and enhancement update), 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/RHEA-2021:4341
Note You need to log in before you can comment on or make changes to this bug.