From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: KVM list <kvm@vger.kernel.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: 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
WARNING: multiple messages have this Message-ID (diff)
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: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 16:26 [ kvm-Bugs-2907597 ] qemu vnc server clips at 2560x1600 SourceForge.net
2010-01-10 16:30 ` Avi Kivity
2010-01-10 16:30 ` [Qemu-devel] " Avi Kivity
2010-01-11 13:53 ` Anthony Liguori
2010-01-11 13:53 ` [Qemu-devel] " Anthony Liguori
2010-01-11 14:30 ` Avi Kivity [this message]
2010-01-11 14:30 ` Avi Kivity
2010-01-11 16:25 ` Avi Kivity
2010-01-11 16:25 ` [Qemu-devel] " Avi Kivity
2010-01-11 14:57 ` Jernej Simončič
-- strict thread matches above, loose matches on Subject: below --
2010-02-10 21:54 SourceForge.net
2010-01-11 16:17 SourceForge.net
2010-01-11 10:19 SourceForge.net
2010-01-10 14:17 SourceForge.net
2010-01-10 14:14 SourceForge.net
2009-12-28 2:20 SourceForge.net
2009-12-17 3:18 SourceForge.net
2009-12-13 10:29 SourceForge.net
2009-12-02 16:57 SourceForge.net
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 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.