From: Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Yaniv Kaul <ykaul@redhat.com>,
kvm@vger.kernel.org
Subject: Re: VNC framebuffer block artefacts on qemu-kvm-0.12.1.1
Date: Wed, 06 Jan 2010 15:36:54 +0000 [thread overview]
Message-ID: <4B44AE16.6040302@siriusit.co.uk> (raw)
In-Reply-To: <20100106135118.GA28640@amt.cnet>
Marcelo Tosatti wrote:
> Mark,
>
> Can you confirm that reverting commit
> 02c2b87fff97e77a1f6033fb09f53afa267c0c1e fixes the problem? (patch
> attached).
>
> Anthony: its reproducible with upstream/tcg.
Hi Marcelo,
Yes, this solves the problem for me - thanks a lot!
FWIW there is still another race condition in the VNC code somewhere.
Due to the bad weather in the UK today, I'm working remotely over an SSH
tunnel which seems to exacerbate the problem. What I see is that when
scrolling large windows in WinXP quickly, my VNC client disconnects from
the VGA framebuffer with messages like this:
CConn: Throughput 1131 kbit/s - changing to full colour
CConn: Using pixel format depth 24 (32bpp) little-endian rgb888
Rect too big: 7088x27 at 4123,40960 exceeds 800x600
main: Rect too big
CConn: Throughput 1093 kbit/s - changing to full colour
CConn: Using pixel format depth 24 (32bpp) little-endian rgb888
Rect too big: 30224x50704 at 50448,13840 exceeds 720x400
main: Rect too big
While I can always reconnect and continue where I left off, it can still
be quite annoying sometimes.
ATB,
Mark.
--
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: +44 870 608 0063
Sirius Labs: http://www.siriusit.co.uk/labs
next prev parent reply other threads:[~2010-01-06 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 16:11 VNC framebuffer block artefacts on qemu-kvm-0.12.1.1 Mark Cave-Ayland
2010-01-06 13:51 ` Marcelo Tosatti
2010-01-06 15:36 ` Mark Cave-Ayland [this message]
2010-01-06 17:58 ` Anthony Liguori
2010-01-06 18:12 ` Marcelo Tosatti
2010-01-06 19:06 ` Anthony Liguori
2010-01-06 22:21 ` Mark Cave-Ayland
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=4B44AE16.6040302@siriusit.co.uk \
--to=mark.cave-ayland@siriusit.co.uk \
--cc=aliguori@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=ykaul@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.