From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NUKho-00027Z-VG for qemu-devel@nongnu.org; Mon, 11 Jan 2010 08:53:17 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NUKhk-00024v-4h for qemu-devel@nongnu.org; Mon, 11 Jan 2010 08:53:16 -0500 Received: from [199.232.76.173] (port=54930 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NUKhj-00024j-UN for qemu-devel@nongnu.org; Mon, 11 Jan 2010 08:53:12 -0500 Received: from mail-qy0-f194.google.com ([209.85.221.194]:56921) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NUKhj-0005zK-Ba for qemu-devel@nongnu.org; Mon, 11 Jan 2010 08:53:11 -0500 Received: by qyk32 with SMTP id 32so1821620qyk.4 for ; Mon, 11 Jan 2010 05:53:07 -0800 (PST) Message-ID: <4B4B2D41.2020306@codemonkey.ws> Date: Mon, 11 Jan 2010 07:53:05 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <4B4A00B6.9070600@redhat.com> In-Reply-To: <4B4A00B6.9070600@redhat.com> 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: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: qemu-devel , KVM list 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