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 1842467 - [NetKVM] HLK: For Window Server 2019 the “*JumboPacket” standardized keyword in the Windows Registry is currently used for setting the MTU size
Summary: [NetKVM] HLK: For Window Server 2019 the “*JumboPacket” standardized keyword ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: virtio-win
Version: 8.3
Hardware: All
OS: Windows
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: ybendito
QA Contact: Yu Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-01 10:31 UTC by Yvugenfi@redhat.com
Modified: 2021-04-01 09:52 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-16 14:24:38 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Yvugenfi@redhat.com 2020-06-01 10:31:19 UTC
Description of problem:
This is a new HLK requirement for Window Server 2019:
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.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 Peixiu Hou 2020-11-11 09:58:17 UTC
(In reply to ybendito from comment #1)
> Merged to upstream
> https://github.com/virtio-win/kvm-guest-drivers-windows/commit/
> 91594594ccdb10625859d67c463cad56e990b891

Hi Yan,

If possible I can get a test build and verify steps? 
I want to try add a new case to our test plan.

Thanks~
Peixiu

Comment 5 Yvugenfi@redhat.com 2020-11-11 11:08:58 UTC
(In reply to Peixiu Hou from comment #4)
> (In reply to ybendito from comment #1)
> > Merged to upstream
> > https://github.com/virtio-win/kvm-guest-drivers-windows/commit/
> > 91594594ccdb10625859d67c463cad56e990b891
> 
> Hi Yan,
> 
> If possible I can get a test build and verify steps? 
> I want to try add a new case to our test plan.
> 
> Thanks~
> Peixiu

Hi Peixiu,

Sorry, there is still no downstream build available.

Best regards,
Yan.

Comment 6 ybendito 2020-11-11 15:43:50 UTC
(In reply to Peixiu Hou from comment #4)
> (In reply to ybendito from comment #1)
> > Merged to upstream
> > https://github.com/virtio-win/kvm-guest-drivers-windows/commit/
> > 91594594ccdb10625859d67c463cad56e990b891
> 
> Hi Yan,
> 
> If possible I can get a test build and verify steps? 
> I want to try add a new case to our test plan.
> 
> Thanks~
> Peixiu

When the BZ becomes modified, there are 2 things to verify this BZ:
1. Regular HCK
2. Get/Set  jumbo frames configuration using powershell, see for example https://blog.workinghardinit.work/2012/06/11/configuring-jumbo-frames-with-powershell-in-windows-server-2012/

Comment 7 Peixiu Hou 2020-11-12 03:20:44 UTC
(In reply to ybendito from comment #6)
> (In reply to Peixiu Hou from comment #4)
> > (In reply to ybendito from comment #1)
> > > Merged to upstream
> > > https://github.com/virtio-win/kvm-guest-drivers-windows/commit/
> > > 91594594ccdb10625859d67c463cad56e990b891
> > 
> > Hi Yan,
> > 
> > If possible I can get a test build and verify steps? 
> > I want to try add a new case to our test plan.
> > 
> > Thanks~
> > Peixiu
> 
> When the BZ becomes modified, there are 2 things to verify this BZ:
> 1. Regular HCK
> 2. Get/Set  jumbo frames configuration using powershell, see for example
> https://blog.workinghardinit.work/2012/06/11/configuring-jumbo-frames-with-
> powershell-in-windows-server-2012/

Got it, thanks a lot~

Peixiu

Comment 8 Yvugenfi@redhat.com 2020-11-12 09:04:27 UTC
The cnages are in virtio-win-prewql 190 : https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1383208

Comment 14 Lei Yang 2020-11-30 09:15:05 UTC
Hi, Yuri

Regarding the replacement of the MTU keyword with JumboPacket, I have a question that needs your help:
1.Is it possible to set the value of JumboPacket through netsh command? If so, can you tell me the specific usage?

Best Regards
Lei Yang

Comment 17 errata-xmlrpc 2021-02-16 14:24:38 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:0535

Comment 18 ybendito 2021-04-01 09:52:42 UTC
(In reply to Lei Yang from comment #14)
> Hi, Yuri
> 
> Regarding the replacement of the MTU keyword with JumboPacket, I have a
> question that needs your help:
> 1.Is it possible to set the value of JumboPacket through netsh command? If
> so, can you tell me the specific usage?

IMO yes, this should be possible as well as any other parameter of NETKVM specified in the INF/registry
You should use "*JumboPacket" parameter name and take in account that this is (MTU + 14), i.e.
for MTU=9000 you should use "*JumboPacket" of 9014

> 
> Best Regards
> Lei Yang


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