qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: [ kvm-Bugs-2907597 ] qemu vnc server clips at 2560x1600
Date: Mon, 11 Jan 2010 07:53:05 -0600	[thread overview]
Message-ID: <4B4B2D41.2020306@codemonkey.ws> (raw)
In-Reply-To: <4B4A00B6.9070600@redhat.com>

On 01/10/2010 10:30 AM, Avi Kivity wrote:
> On 01/10/2010 06:26 PM, SourceForge.net wrote:
>> Initial Comment:
>> So I am running using the VESA driver to run an Ubuntu 9.10 guest at 
>> 2560x1600 (I had to modify the xserver-video-vesa package to remove 
>> an internal screen limit of 2048x2048 in the xorg vesa driver) and 
>> everything works great except that the qemu vnc server appears to 
>> clip at this resolution. The problem goes away if I run 1900x1200 and 
>> it doesn't change if I run 16bit depth or 24bit depth.
>>
>> I have attached two screenshots, the first is vncing directly into 
>> qemu (which exhibits the problem) and the second is vncing to a vnc 
>> server I have running in the guest which doesn't have the problem.
>>
>> I poked around in vnc.c and couldn't see any limits but I feel like 
>> its a buffer limit of some kind.
>>
>> Also if you look very closely at the first image you can see that the 
>> first row is drawn correctly all the way across but subsequent rows 
>> are not.
>>
>> If you need more information doesn't hesitate to ask.
>>
>
> Anthony, can you take a look at this?  Seems like a serious issue, 
> could find nothing obvious in vnc.c.

VNC_MAX_WIDTH and VNC_MAX_HEIGHT in vnc.h are currently defined to 
2048.  We do dirty tracking with a bitmap and that bitmap is currently a 
fixed size.

2048 is bigger than any physical screen that I know of so I assume this 
is a multiple monitor scenario.  Long term, I think exposing multiple 
monitors to the guest is a better approach for this kind of functionality.

Since these resolutions for a single screen don't really exist, this is 
largely an untested path within the guest.

Regards,

Anthony Liguori

  reply	other threads:[~2010-01-11 13:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1NU0ce-0008Ho-Em@665xhf1.ch3.sourceforge.com>
2010-01-10 16:30 ` [Qemu-devel] Re: [ kvm-Bugs-2907597 ] qemu vnc server clips at 2560x1600 Avi Kivity
2010-01-11 13:53   ` Anthony Liguori [this message]
2010-01-11 14:30     ` Avi Kivity
2010-01-11 16:25       ` Avi Kivity
2010-01-11 14:57     ` Jernej Simončič

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=4B4B2D41.2020306@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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).