Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Cause: NetKVMConfig utility was not updating rx and tx parameters in Registry.
Consequence: users cannot update rx and tx parameters in Registry with NetKVMConfig utility.
Fix: correct NetKVMConfig parameters changing handler
Result: NetKVMConfig works as expected.
Description:
Try to config virtio nic parameters with NetKVMConfig, check with the tools and it report the value has changed. But the change is not shown in the windows device manager. It is the same that if I change it from device manager, it will no influence the value get by NetKVmConfig tools.
Version-Release number of selected component (if applicable):
kernel:
2.6.32-221
kvm&qemu:
qemu-img-0.12.1.2-2.210.el6.x86_64
qemu-kvm-0.12.1.2-2.210.el6.x86_64
qemu-kvm-tools-0.12.1.2-2.210.el6.x86_64
qemu-kvm-debuginfo-0.12.1.2-2.210.el6.x86_64
gpxe-roms-qemu-0.9.7-6.7.el6.noarch
virtio-win:
virtio-win-1.4.0-1.el6.noarch
How reproducible:
always
Steps to Reproduce:
1. boot up a win7 guest
2. update the device driver for virtio nic
3. Set up KVMNetConfig tools
- copy netkvmco.dll to system32
- register it
rundll32 netkvmco.dll,RegisterNetKVMNetShHelper
- run netsh
netsh netkvm show devices
netsh netkvm show parameters 0
netsh netkvm getparam 0 RxCapacity
netsh netkvm setparam 0 RxCapacity 256
4. Check the parameters in device manager in Windows
Actual results:
In netsh tools it shows the parameter has changed, while the parameter is not changed in device manager
Expected results:
The parameter's value should be the same in both tools.
Additional info:
Comment 2Yvugenfi@redhat.com
2011-12-26 16:06:41 UTC
1. The problem was found.
2. The utility changed default value instead of the parameter value in registry.
3. Keep in mind that device should be restarted in order for the parameters to take effect.
4. If advanced tab of device manager is opened while parameter is changed - it should be closed and reopened to see the change.
How is NetKVMConfig packaged and tested? I want to clear the flags of this bug: it is in POST but has rhel6.3.0? and devel_ack? flags set, plus a cond-nak:capacity.
Comment 4Yvugenfi@redhat.com
2012-01-08 12:25:41 UTC
NetKVMConfig is part of the NetKVM package according to WHQL requirements (we have to provide command line configuration tool if the driver has configuration options).
It was tested by the QE teem according to test and user documents provided to them by me (they are also part of the code repository).
It was decided that the bug priority is minor, because at least for now the only usage for this tool is to comply to MS checklist (although in the future this toll can be used for our network driver configuration). Nevertheless the problem that caused the bug was found and fixed - and the fix will be release with next build of Windows virtio drivers.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause: NetKVMConfig utility was not updating rx and tx parameters in Registry.
Consequence: users cannot update rx and tx parameters in Registry with NetKVMConfig utility.
Fix: correct NetKVMConfig parameters changing handler
Result: NetKVMConfig works as expected.
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-2012-0751.html
Description: Try to config virtio nic parameters with NetKVMConfig, check with the tools and it report the value has changed. But the change is not shown in the windows device manager. It is the same that if I change it from device manager, it will no influence the value get by NetKVmConfig tools. Version-Release number of selected component (if applicable): kernel: 2.6.32-221 kvm&qemu: qemu-img-0.12.1.2-2.210.el6.x86_64 qemu-kvm-0.12.1.2-2.210.el6.x86_64 qemu-kvm-tools-0.12.1.2-2.210.el6.x86_64 qemu-kvm-debuginfo-0.12.1.2-2.210.el6.x86_64 gpxe-roms-qemu-0.9.7-6.7.el6.noarch virtio-win: virtio-win-1.4.0-1.el6.noarch How reproducible: always Steps to Reproduce: 1. boot up a win7 guest 2. update the device driver for virtio nic 3. Set up KVMNetConfig tools - copy netkvmco.dll to system32 - register it rundll32 netkvmco.dll,RegisterNetKVMNetShHelper - run netsh netsh netkvm show devices netsh netkvm show parameters 0 netsh netkvm getparam 0 RxCapacity netsh netkvm setparam 0 RxCapacity 256 4. Check the parameters in device manager in Windows Actual results: In netsh tools it shows the parameter has changed, while the parameter is not changed in device manager Expected results: The parameter's value should be the same in both tools. Additional info: