Bug 1444326

Summary: Keyboard inputs are buffered when qemu in stop status
Product: Red Hat Enterprise Linux 7 Reporter: Guo, Zhiyi <zhguo>
Component: qemu-kvm-rhevAssignee: Marc-Andre Lureau <marcandre.lureau>
Status: CLOSED ERRATA QA Contact: Guo, Zhiyi <zhguo>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.4CC: aliang, chayang, coli, jinzhao, juzhang, knoel, kraxel, virt-maint, xuma
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: qemu-kvm-rhev-2.9.0-8.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-02 04:35:59 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:

Description Guo, Zhiyi 2017-04-21 06:35:49 UTC 
Description of problem:
Keyboard inputs are buffered when qemu in stop status

Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.9.0-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.boot guest with vnc connection
2.in qemu monitor:
(qemu) stop
3.switch vnc client window to the top, type some characters
4.in qemu monitor:
(qemu) c

Actual results:
Characters are presented in client after continuing qemu-kvm 

Expected results:
Characters should not be presented in client after continuing qemu-kvm

Additional info:
No such issue happen via spice display
Comment 3 Marc-Andre Lureau 2017-05-09 11:59:09 UTC 
see patch on ML "[PATCH] input: don't queue delay if paused"
Comment 4 hachen 2017-05-22 09:46:06 UTC 
I test on 
kernel-3.10.0-656.el7.x86_64
qemu-kvm-rhev-2.9.0-5.el7.x86_64

The descriped issue happens agian.
Comment 5 Marc-Andre Lureau 2017-05-26 07:45:35 UTC 
sent on rhvirt-patches ML
Comment 6 Miroslav Rezanina 2017-06-06 08:54:01 UTC 
Fix included in qemu-kvm-rhev-2.9.0-8.el7
Comment 11 errata-xmlrpc 2017-08-02 04:35:59 UTC 
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://access.redhat.com/errata/RHSA-2017:2392