From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
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 16:30:50 +0200 [thread overview]
Message-ID: <4B4B361A.4010805@redhat.com> (raw)
In-Reply-To: <4B4B2D41.2020306@codemonkey.ws>
On 01/11/2010 03:53 PM, Anthony Liguori wrote:
>> 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.
Google suggests such screens do exist, and -vga std (at least in
qemu-kvm) supports them.
I've asked the reporter to play with VNC_MAX_WIDTH.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-01-11 14:31 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
2010-01-11 14:30 ` Avi Kivity [this message]
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=4B4B361A.4010805@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--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).