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.
I meet the same issue on Win8.1 at case NDISTes 6.0 - [1 Machine] -1c_Mini6PerfSend)
Version-Release number of selected component (if applicable):
virtio-win-prewhql-0.1-216.iso
Comment 3Yvugenfi@redhat.com
2022-03-15 06:50:19 UTC
Can you generate the dump from the host side?
Comment 6leidwang@redhat.com
2022-03-25 01:18:55 UTC
Let me update with some status on this bug.
I tested the job on rhel8.5, Win8.1-64 passed, Win11 still failed.
I noticed in hlk studio that the job took 35 minutes, but now the job is running for 12 hours and still not finished.The vm is still stuck.
I'll update the Win10-32/64 test results later. Thanks!
Comment 11Yvugenfi@redhat.com
2022-04-19 07:33:19 UTC
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/RHBA-2022:8261