Bug 1366471
Summary: | QEMU prints "usb-kbd: warning: key event queue full" when pressing keys during SLOF boot | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Thomas Huth <thuth> |
Component: | qemu-kvm-rhev | Assignee: | Thomas Huth <thuth> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | dgibson, jsuchane, knoel, lvivier, mdeng, michen, mrezanin, qzhang, thuth, virt-bugs, virt-maint |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | ppc64le | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-rhev-2.6.0-21.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1352765 | Environment: | |
Last Closed: | 2016-11-07 21:30:34 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: | |||
Bug Depends On: | 1352765 | ||
Bug Blocks: | 1354177 |
Comment 1
Thomas Huth
2016-08-12 05:08:49 UTC
*** Bug 1348422 has been marked as a duplicate of this bug. *** When testing this issue, please make sure to test the scenario from bug 1348422, too, since it is slightly different (virtio input instead of USB). Fix included in qemu-kvm-rhev-2.6.0-21.el7 According to Description, Verified it on build qemu-kvm-rhev-2.6.0-22.el7,the issue has been fixed. According to comment 3, To my opinion,verified failed because the mouse cannot work at all after guest boot up but the error message was gone. As the original bug was closed as duplicated,should we reopen it or report new ? (In reply to dengmin from comment #6) > To my opinion,verified failed because the mouse cannot work at all after > guest boot up but the error message was gone. > As the original bug was closed as duplicated,should we reopen it or report > new ? OK, thanks for testing! I'd suggest to open a new bug, since BZ 1348422 was only about the error messages according to the bug description. So I think it is less confusing to have a new bug instead for the non-working mouse. (In reply to Thomas Huth from comment #7) > (In reply to dengmin from comment #6) > > To my opinion,verified failed because the mouse cannot work at all after > > guest boot up but the error message was gone. > > As the original bug was closed as duplicated,should we reopen it or report > > new ? > > OK, thanks for testing! I'd suggest to open a new bug, since BZ 1348422 was > only about the error messages according to the bug description. So I think > it is less confusing to have a new bug instead for the non-working mouse. Open a new bug for tracing new issue - Bug 1371054 Base on comment 6,the original issue has been fixed and another issue will be traced in new Bug 1371054. So we take it as fixed and move it to verified.Thanks a lot. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2673.html |