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.
Description of problem:
2 virtio-win devices with the same MAC address cause BSOD of netkvm.sys
Version-Release number of selected component (if applicable):
virtio-win-prewhql-0.1.193
How reproducible:
100%
Steps to Reproduce:
1. Define 2 virtio-net devices with the same MAC
2. Install the netkvm driver
Actual results:
BSOD happens
Expected results:
One or both adapters may not work, this is not correct situation, but the system crash should not happen.
Additional info:
This is a regression caused by SRIOV failover feature.
Reproduced this bug with virtio-win-193
steps:
1 boot with 2 virtio-net (the same mac)
2 install driver
guest BSOD after driver installed successfully
version:
Guest:win10-64
kernel-4.18.0-278.el8.dt3.x86_64
qemu-kvm-5.2.0-4.module+el8.4.0+9676+589043b9.x86_64
virtio-win-prewhql-193
seabios-bin-1.14.0-1.module+el8.4.0+8855+a9e237a9.noarch
RHEL-8.4.0-20210128.d.2
Reproduced this bug with virtio-win-193 and verified with virtio-win-prewhql-195
Steps as comment#2
Above all, this bug has been fixed, change status to verified
guests:win10-64, win10-32,win8.1-32,win2012
kernel-4.18.0-283.el8.x86_64
qemu-kvm-5.2.0-5.module+el8.4.0+9775+0937c167.x86_64
seabios-bin-1.14.0-1.module+el8.4.0+8855+a9e237a9.noarch
DISTRO=RHEL-8.4.0-20210206.n.0
Thanks
Yu Wang
Hi,
Since the issue described in this bug should be resolved (VERIFIED), could you please close this bug with resolution 'CURRENTRELEASE' if this bug got fixed ?
If the fix for this is not released yet, check if this will ever get fixed. In case of a negative answer then please change it as WONTFIX.
If there's anything else to be done on this BZ, if it's still active, not released yet and we actually intend to release it, then please ignore my message.
Please note: for those bugs which are not included in errata, please add 'TestOnly' keyword, and those bugs with 'TestOnly' keyword will be closed automatically after GA.
TestOnly: Use this when there is no code delivery involved, or for use when code is already upstream and will be incorporated automatically to the next release for testing purposes only.
Thank you.