Bug 2028000
Summary: | Add bus reset handler to viostor driver. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Peixiu Hou <phou> |
Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> |
virtio-win sub component: | virtio-win-prewhql | QA Contact: | menli <menli> |
Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
Severity: | high | ||
Priority: | unspecified | CC: | ailan, coli, danken, fdeutsch, hpopal, ipinto, jinzhao, juzhang, mdean, menli, mkedzier, mprivozn, pelauter, phou, qinwang, qizhu, rcain, rmohr, vrozenfe, xiagao, xzhou, zhguo |
Version: | 9.0 | Keywords: | RFE, TestCannotAutomate, Triaged |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | virtio-win-1.9.24-1.el8_4 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 2013976 | Environment: | |
Last Closed: | 2022-01-27 02:07:29 UTC | Type: | Feature Request |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 2013976 | ||
Bug Blocks: | 2010485 |
Comment 1
Vadim Rozenfeld
2021-12-02 07:53:27 UTC
Sorry for reply this late due to sick leave. Try it with 215 build. hit 5 129 event logs, and the time gap is larger than 30s. I tried to reboot the guest, the guest can be rebooted smoothly, keep the vm running about 24 hours (with speed limit),hit following error, I guess it should be an expected error, right? error: (qemu) q qemu-kvm: Failed to flush the refcount block cache: Input/output error now I have cleared the speed limit and let the vm run background for more hours, if no issue and above error is expected, I will change the bz to verify status, thanks Thanks Menghuan (In reply to menli from comment #3) > Sorry for reply this late due to sick leave. > > > Try it with 215 build. hit 5 129 event logs, and the time gap is larger > than 30s. > I tried to reboot the guest, the guest can be rebooted smoothly, keep the vm > running about 24 hours (with speed limit),hit following error, I guess it > should be an expected error, right? > > > error: > (qemu) q > qemu-kvm: Failed to flush the refcount block cache: Input/output error > > > now I have cleared the speed limit and let the vm run background for more > hours, if no issue and above error is expected, I will change the bz to > verify status, thanks hit a BSOD (but unfortunately not got the dump) kill the qemu process then start the guest again, after finish install the update ,reboot the guest. the VM is slow (eg:the buttons in the task bar is very slow response) > > > Thanks > > Menghuan (In reply to menli from comment #3) > Sorry for reply this late due to sick leave. > > > Try it with 215 build. hit 5 129 event logs, and the time gap is larger > than 30s. > I tried to reboot the guest, the guest can be rebooted smoothly, keep the vm > running about 24 hours (with speed limit),hit following error, I guess it > should be an expected error, right? Yep, that's true. The error has been triggered by QEMU as the flush request is not completed on time. It comes from the host storage subsystem which has its own timeout (something like sys/block/sda/device/timeout) and has nothing to do with the guest. > > > error: > (qemu) q > qemu-kvm: Failed to flush the refcount block cache: Input/output error > > > now I have cleared the speed limit and let the vm run background for more > hours, if no issue and above error is expected, I will change the bz to > verify status, thanks > > > > Thanks > > Menghuan Thanks Vadim. Base on comment3, I try retest it with a new image, and the windows update can be completed successfully, try to reboot the guest, the guest can be rebooted smoothly, keep the vm running about 20 hours, no BSOD occurs. so change the bug to verified. Thanks Menghuan |