From: Gerd Hoffmann <kraxel@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Gonglei <arei.gonglei@huawei.com>,
Gabriele Giacone <1o5g4r8o@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
758881@bugs.debian.org
Subject: Re: [Qemu-devel] [bisected] VNC server can't get all sent chars correctly
Date: Mon, 25 Aug 2014 11:37:05 +0200 [thread overview]
Message-ID: <1408959425.24970.1.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <53F85723.607@msgid.tls.msk.ru>
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
next prev parent reply other threads:[~2014-08-25 9:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-23 8:56 [Qemu-devel] [bisected] VNC server can't get all sent chars correctly Michael Tokarev
2014-08-25 3:19 ` Gonglei (Arei)
2014-08-25 7:30 ` Markus Armbruster
2014-08-25 7:36 ` Gonglei (Arei)
2014-08-25 9:37 ` Gerd Hoffmann [this message]
2014-08-25 10:40 ` [Qemu-devel] Bug#758881: " Gabriele Giacone
2014-08-26 4:11 ` Marc
2014-08-26 5:40 ` Gerd Hoffmann
2014-08-26 5:55 ` Michael Tokarev
2014-08-26 6:08 ` Gerd Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1408959425.24970.1.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=1o5g4r8o@gmail.com \
--cc=758881@bugs.debian.org \
--cc=arei.gonglei@huawei.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).