Bug 1899343
Summary: | windows 2016 virtual disk service hangs when attaching formatted virtio drive | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Joshua Job <jjob> | ||||||
Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> | ||||||
virtio-win sub component: | distribution | QA Contact: | menli <menli> | ||||||
Status: | CLOSED DUPLICATE | Docs Contact: | |||||||
Severity: | unspecified | ||||||||
Priority: | unspecified | CC: | jinzhao, juzhang, lijin, menli, vrozenfe | ||||||
Version: | 8.2 | Keywords: | Triaged | ||||||
Target Milestone: | rc | ||||||||
Target Release: | 8.0 | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Windows | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2022-07-03 23:38:42 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Created attachment 1730734 [details]
XML used to attach devices
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. (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 *** This bug has been marked as a duplicate of bug 1744438 *** |
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: