Bug in INF file incorrectly indicated 1G connection rate.
While the connection rate could be set from device manager, it was impossible to set 1G rate using command line tool (netsh with NetKVM plugin).
Set the correct connection rate in INF file
NetSH can set NIC connection rate correctly.
Description of problem:
the value of "init.ConnetctionRate(Mb)" cannot be set to 1G with command "netsh netkvm setparam 0 ConnectRate 1000",but can be set to 1G correctly with command "netsh netkvm setparam 0 ConnectRate 1001",seems there is a little mistake.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.boot a win2012 guest with virtio-net-pci
2.Registration in NetSH (instllation):
1).cmd --> run as administrator
3.get the index of virtio-net-pci:
netsh netkvm show devices
4.Read NetKVM parameter value
netsh netkvm getparam 0 param=ConnectRate
5.Modify NetKVM parameter value to 100M and check the value from device manager
netsh netkvm setparam 0 ConnectRate 100
6.Modify NetKVM parameter value to 10G and check the value from device manager
netsh netkvm setparam 0 ConnectRate 10000
7.Modify NetKVM parameter value to 1G and check the value from device manager
netsh netkvm setparam 0 ConnectRate 1000
8.netsh netkvm setparam 0 ConnectRate 1001
after step6,all values can be set correctly;
after step7,it prompts in cmd that "The parameter is incorrect";
after step8,the command can be execute successfully and from the device manager the value of "init.ConnetctionRate(Mb" has been set to 1G
the value of "init.ConnetctionRate(Mb" can be set to 1G with step7 instead of step8.
Fixed for OSes Vista and up.
Reproduced this issue on build65
Verified this issue on build66
steps same as comment #0
On build65, after "netsh netkvm setparam 0 ConnectRate 1000",it prompt "The parameter is incorrect";
On build66,win2012,win2k8R2,win2k8-64,win8-64 and win7-64 can set the connectrate to 1G correctly;as for guest win7-32,win8-32 and win2k8-32,there is bug 988302 to track another issue.
Based on above,this issue has been fixed already.
Move status to VERIFIED according to comment #5
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.