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.
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
Comment 13menli@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