Bug 2028000 - Add bus reset handler to viostor driver.
Summary: Add bus reset handler to viostor driver.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virtio-win
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Vadim Rozenfeld
QA Contact: menli@redhat.com
URL:
Whiteboard:
Depends On: 2013976
Blocks: 2010485
TreeView+ depends on / blocked
 
Reported: 2021-12-01 09:00 UTC by Peixiu Hou
Modified: 2022-03-09 03:31 UTC (History)
22 users (show)

Fixed In Version: virtio-win-1.9.24-1.el8_4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2013976
Environment:
Last Closed: 2022-01-27 02:07:29 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-104416 0 None None None 2021-12-01 09:05:03 UTC

Comment 3 menli@redhat.com 2021-12-09 03:18:53 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

Comment 5 menli@redhat.com 2021-12-09 06:41:16 UTC
(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

Comment 11 Vadim Rozenfeld 2021-12-15 02:29:05 UTC
(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

Comment 13 menli@redhat.com 2021-12-16 01:12:54 UTC
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


Note You need to log in before you can comment on or make changes to this bug.