Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>
To: kvm@vger.kernel.org
Subject: VNC framebuffer block artefacts on qemu-kvm-0.12.1.1
Date: Tue, 05 Jan 2010 16:11:26 +0000	[thread overview]
Message-ID: <4B4364AE.8080509@siriusit.co.uk> (raw)

Hi all,

Having just upgraded from kvm-85 to qemu-kvm-0.12.1.1 on one of our 
servers, I've noticed that I am seeing block artefacts when connecting 
using VNC to the graphical VGA console of a WinXP guest.

Looking at the VNC output, what I am seeing is that instead of updating 
some parts of the screen which require a redraw, they are just being 
replaced by light grey blocks of around 16x16 pixels. Generally, but not 
always, several of these blocks appear in a row. Moving the mouse over 
the relevant sections of the screen causes them to be redrawn correctly.

I've tried this using both the cirrus and vga drivers, switching between 
16/24/32 bit colour and also different resolutions and unfortunately the 
effect still remains :( Is there anything else I can do to help try and 
debug this? Again this is on an x86_64 Debian Lenny host with a 2.6.32.2 
kernel on Intel.


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

             reply	other threads:[~2010-01-05 16:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 16:11 Mark Cave-Ayland [this message]
2010-01-06 13:51 ` VNC framebuffer block artefacts on qemu-kvm-0.12.1.1 Marcelo Tosatti
2010-01-06 15:36   ` Mark Cave-Ayland
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=4B4364AE.8080509@siriusit.co.uk \
    --to=mark.cave-ayland@siriusit.co.uk \
    --cc=kvm@vger.kernel.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