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.
Created attachment 1730729[details]
VM xml
Description of problem:
On virtio block attach, disk related UI becomes unresponsive and drive accesses hang.
Version-Release number of selected component (if applicable):
From Device Manager driver properties: 100.82.104.18400
fill package: virtio-win-1.9.12-2.el8.noarch
How reproducible:
Approximately every other time. If it doesn't happen with the first attach, it happens with the next. These do not need to be the same qcow image.
Steps to Reproduce:
1. Create a windows 2016 VM with viostor drivers
2. Attach a virtio block device, partition it, and give it a file system
3. Detach it
4. Re-attach it
Actual results:
Disk management related UI becomes unresponsive and any thing that accesses the drive becomes unresponsive.
Expected results:
The drive would be usable as if was attached at vm start.
Additional info:
(In reply to Vadim Rozenfeld from comment #2)
> Seems to be related to the common q3 hot-(un)plug problem
> https://bugzilla.redhat.com/show_bug.cgi?id=1744438
>
> Can QE correct or confirm my assumption?
>
> Thanks,
> Vadim.
Hi Vadim，
Your assumption is right. Hit this similiar issue quite often in my testing before.
Thanks
Menghuan
Created attachment 1730729 [details] VM xml Description of problem: On virtio block attach, disk related UI becomes unresponsive and drive accesses hang. Version-Release number of selected component (if applicable): From Device Manager driver properties: 100.82.104.18400 fill package: virtio-win-1.9.12-2.el8.noarch How reproducible: Approximately every other time. If it doesn't happen with the first attach, it happens with the next. These do not need to be the same qcow image. Steps to Reproduce: 1. Create a windows 2016 VM with viostor drivers 2. Attach a virtio block device, partition it, and give it a file system 3. Detach it 4. Re-attach it Actual results: Disk management related UI becomes unresponsive and any thing that accesses the drive becomes unresponsive. Expected results: The drive would be usable as if was attached at vm start. Additional info: