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.
(In reply to mazhang from comment #3)
> (In reply to Gerd Hoffmann from comment #2)
> > Graphical login or text console?
> > Does the mouse work?
>
> Graphical login, and the mouse was working.
When do those messages show up? Any chance this happens only before the guest driver is loaded and active?
If the mouse is working fine this seems to be a cosmetic issue only. The
message should probably converted to a tracepoint. It's not helpful, except
for trouble-shooting.
(In reply to Gerd Hoffmann from comment #4)
> (In reply to mazhang from comment #3)
> > (In reply to Gerd Hoffmann from comment #2)
> > > Graphical login or text console?
> > > Does the mouse work?
> >
> > Graphical login, and the mouse was working.
>
> When do those messages show up? Any chance this happens only before the
> guest driver is loaded and active?
Those messages shows up after virtio_input module loaded.
>
> If the mouse is working fine this seems to be a cosmetic issue only. The
> message should probably converted to a tracepoint. It's not helpful, except
> for trouble-shooting.
Fixed in qemu 2.7:
commit c80276b4206d534daaaf87305df5805db1b8db02
Author: Gerd Hoffmann <kraxel>
Date: Thu Jun 23 11:51:35 2016 +0200
input: add trace events for full queues
It isn't unusual to happen, for example during reboot when the guest
doesn't reveice events for a while. So better don't flood stderr
with alarming messages. Turn them into tracepoints instead so they
can be enabled in case they are needed for trouble-shooting.
Signed-off-by: Gerd Hoffmann <kraxel>
Message-id: 1466675495-28797-1-git-send-email-kraxel
... lets pick it up with the next rebase.