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 1273793 - NetKVM: Initialisation and power on code sequences should use same or as similar as possible code
Summary: NetKVM: Initialisation and power on code sequences should use same or as simi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virtio-win
Version: 7.3
Hardware: All
OS: Windows
low
medium
Target Milestone: rc
: ---
Assignee: Yvugenfi@redhat.com
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-21 09:08 UTC by Yvugenfi@redhat.com
Modified: 2017-01-06 06:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-06 06:57:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Yvugenfi@redhat.com 2015-10-21 09:08:01 UTC
Description of problem:

Currently there are some differences between initial device initialisation and initialisation of the device after power up. 

Should be fix to make the code more robust and maintainable.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Yvugenfi@redhat.com 2015-10-21 12:28:41 UTC
Solved by 273791

Comment 4 lijin 2016-01-06 02:39:55 UTC
Hi Yan,

As you said in comment#1,it should avoid possible issues with HCK MPE test,does that means all HCK MPE jobs should pass with the fixed build?

According to virtio-win-prewhql-111 netkvm whql test result,job "NDISTest 6.5 - [2 Machine] - MPE_Ethernet.xml" failed on win2012,win2012R2 and win8.1-64 guests(bug1013336).

How should we confirm this issue has been fixed? Is no regression bug found enough?

Thanks

Comment 5 Yvugenfi@redhat.com 2016-01-06 06:59:14 UTC
(In reply to lijin from comment #4)
> Hi Yan,
> 
> As you said in comment#1,it should avoid possible issues with HCK MPE
> test,does that means all HCK MPE jobs should pass with the fixed build?
> 
> According to virtio-win-prewhql-111 netkvm whql test result,job "NDISTest
> 6.5 - [2 Machine] - MPE_Ethernet.xml" failed on win2012,win2012R2 and
> win8.1-64 guests(bug1013336).
> 
> How should we confirm this issue has been fixed? Is no regression bug found
> enough?
> 
> Thanks

Please check for regressions.

Thanks.

Comment 8 lijin 2016-09-02 07:42:56 UTC
change status to verified as there is no regression bugs with latest build:virtio-win-prewhql-126

Comment 9 lijin 2017-01-06 06:57:56 UTC
close as this issue has already been fixed in rhel7.3 virtio-win package


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