Bug 982940
Summary: | [virtio-win][netkvm]NetKVMConfig can not modify the parameter "init.ConnetctionRate(Mb)" to 1G correctly | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | lijin <lijin> |
Component: | virtio-win | Assignee: | Yvugenfi <yvugenfi> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.5 | CC: | acathrow, bcao, bsarathy, qzhang, rhod |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
Bug in INF file incorrectly indicated 1G connection rate.
Consequence:
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).
Fix:
Set the correct connection rate in INF file
Result:
NetSH can set NIC connection rate correctly.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-11-22 00:14:08 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
lijin
2013-07-10 07:50:43 UTC
Fixed for OSes Vista and up. win2012,win2k8R2,win2k8-64,win8-64,win7-64, win7-32,win8-32,win2k8-32 Reproduced this issue on build65 Verified this issue on build66 steps same as comment #0 Actual Results: 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. http://rhn.redhat.com/errata/RHBA-2013-1729.html |