From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NULIU-0005D2-Og
	for qemu-devel@nongnu.org; Mon, 11 Jan 2010 09:31:10 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NULIQ-0005Bb-7i
	for qemu-devel@nongnu.org; Mon, 11 Jan 2010 09:31:10 -0500
Received: from [199.232.76.173] (port=45628 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NULIQ-0005BW-0q
	for qemu-devel@nongnu.org; Mon, 11 Jan 2010 09:31:06 -0500
Received: from mx1.redhat.com ([209.132.183.28]:19172)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1NULIP-0003kw-9F
	for qemu-devel@nongnu.org; Mon, 11 Jan 2010 09:31:05 -0500
Message-ID: <4B4B361A.4010805@redhat.com>
Date: Mon, 11 Jan 2010 16:30:50 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <E1NU0ce-0008Ho-Em@665xhf1.ch3.sourceforge.com>
	<4B4A00B6.9070600@redhat.com> <4B4B2D41.2020306@codemonkey.ws>
In-Reply-To: <4B4B2D41.2020306@codemonkey.ws>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: [ kvm-Bugs-2907597 ] qemu vnc server clips at
	2560x1600
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>

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