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: When the VIOPROT protocol installed, is does not bind to netkvm adapter (that's correct). But it is possible to enable binding of the protocol to netkvm adapter and this causes immediate BSOD.


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

How reproducible:
100%


Steps to Reproduce:
VM with virtio-net (no need to have VF). Install VIOPROT protocol. Go to Control panel - Network and Sharing center - Change adapter settings - VirtIO adapter - Properties - enabled check box VirtIO NetKVM protocol driver - OK.

Actual results:
BSOD

Expected results:
At least this should not do anything bad.


Additional info:

https://github.com/virtio-win/kvm-guest-drivers-windows/pull/552

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: win2016, 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

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 (virtio-win bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2021:1959