From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44356) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XLqiW-0003OQ-G9 for qemu-devel@nongnu.org; Mon, 25 Aug 2014 05:37:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XLqiQ-0000aS-Ag for qemu-devel@nongnu.org; Mon, 25 Aug 2014 05:37:36 -0400 Received: from mx1.redhat.com ([209.132.183.28]:31802) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XLqiQ-0000YT-2p for qemu-devel@nongnu.org; Mon, 25 Aug 2014 05:37:30 -0400 Message-ID: <1408959425.24970.1.camel@nilsson.home.kraxel.org> From: Gerd Hoffmann Date: Mon, 25 Aug 2014 11:37:05 +0200 In-Reply-To: <53F85723.607@msgid.tls.msk.ru> References: <53F85723.607@msgid.tls.msk.ru> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [bisected] VNC server can't get all sent chars correctly List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Michael Tokarev Cc: Gonglei , Gabriele Giacone <1o5g4r8o@gmail.com>, qemu-devel , 758881@bugs.debian.org On Sa, 2014-08-23 at 12:56 +0400, Michael Tokarev wrote: > There's a bug filed against debian qemu package, there: > > http://bugs.debian.org/758881 > > which says about problems sending keypress events over VNC to > a qemu guest, -- some keypresses gets lost, at least. > So it looks like something else is not right here. Before this patch, > it wasn't possible to use keyboard with VNC client with redhat 5 guest. > Now, it isn't possible to use keyboard with VNC in another scenario which > worked before (so it is a regression compared with 2.0 version). qemu 2.1 hardware emulation is more correct (ps/2 kbd queue size being 16 bytes instead of 256, matching real hardware). That may trip up software depending on old, broken behavior. IMO vncdotool should be fixed to add small delays between keyboard events, as if a real person is typing, instead of sending the key events at the maximum possible speed. I'm sure you can hit the issue with qemu 2.0 too, you just need longer user input strings to trigger it, so it is less likely to happen. cheers, Gerd