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:
The driver will try to access the "HW" after receiving surprise removal notification from OS.
It is a real issue if after S4(hibernation) the device will be removed from QEMU command line.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

The issue now has been fixed in upstream b the following PR:
https://github.com/virtio-win/kvm-guest-drivers-windows/pull/276

Hi,

Reproduce this issue with build 145 and verified on build 151 (win7-64)
with build145, after step4 in comment#5, BSOD occurred
with build151, no BSOD at all.

Above this bug has been fixed. Change status to verified.

Thanks
Yu Wang

(In reply to Yu Wang from comment #9)
> Hi,
> 
> Reproduce this issue with build 145 and verified on build 151 (win7-64)
> with build145, after step4 in comment#5, BSOD occurred
> with build151, no BSOD at all.
> 
> Above this bug has been fixed. Change status to verified.
> 
> Thanks
> Yu Wang

Thanks!

Can we have QA, PM and Release flags for this, please?

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.

https://access.redhat.com/errata/RHBA-2018:3413