Bug 1537430

Summary: [NetKVM] Support setting link speed and duplex settings from QEMU
Product: Red Hat Enterprise Linux 8 Reporter: Yvugenfi <yvugenfi>
Component: virtio-winAssignee: ybendito
virtio-win sub component: virtio-win-prewhql QA Contact: Virtualization Bugs <virt-bugs>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: medium CC: ailan, dkutalek, fgarciad, jen, kanderso, lijin, phou, vrozenfe, wyu, xiagao, ybendito, yvugenfi
Version: 8.0Keywords: RFE
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1722184 (view as bug list) Environment:
Last Closed: 2019-07-30 14:22:06 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1722184, 1725380    

Description Yvugenfi@redhat.com 2018-01-23 08:20:19 UTC 
Description of problem:

There is an addition to virtio spec and implementation in QEMU of the support of setting link speed and duplex setting from QEMU command line.
NetKVM driver should be able to support this feature.

https://www.spinics.net/lists/kernel/msg2675444.html

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Yvugenfi@redhat.com 2018-01-25 08:43:20 UTC 
First patch is submitted: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/241
Comment 5 Vadim Rozenfeld 2018-03-06 07:05:54 UTC 
Please give a try to drivers from the latest (b148) build 
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=659785

Thanks,
Vadim.
Comment 11 lijin 2018-08-21 08:13:01 UTC 
move to rhel7.7 according to comment#8 and comment#9
Comment 24 errata-xmlrpc 2019-07-30 14:22:06 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, 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-2019:1997