From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FaQyT-0001Mg-LT for qemu-devel@nongnu.org; Mon, 01 May 2006 01:29:33 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FaQyS-0001Jr-HD for qemu-devel@nongnu.org; Mon, 01 May 2006 01:29:33 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FaQyS-0001JX-Ac for qemu-devel@nongnu.org; Mon, 01 May 2006 01:29:32 -0400 Received: from [209.234.73.39] (helo=narn.hozed.org) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1FaR2C-0001mB-F8 for qemu-devel@nongnu.org; Mon, 01 May 2006 01:33:24 -0400 Date: Mon, 1 May 2006 00:29:30 -0500 From: Troy Benjegerdes Subject: Re: [Qemu-devel] [PATCH] VNC display support for QEMU Message-ID: <20060501052930.GZ15855@narn.hozed.org> References: <4453DBDE.8020306@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: <4453DBDE.8020306@codemonkey.ws> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org > Where 1 is the first display (port 5901). This syntax may change in the > near future to support binding to a particular interface. It's very > useful to use an absolute mouse with VNC as the relative support is > quite poor. It may be useful to adapt the libvncserver patch's > calibration code here but I've not attempted to do that yet. > > This patch is still experimental. I've tested it with RealVNC and > TightVNC under a variety of depths but I won't be suprised if there are > still problems. I only implement Raw, CopyRect, and Hextile encodings > too. Any sort of palette color mode or pixel format that QEMU doesn't > support will not work either. > > One thing you may notice is that RealVNC has some issues with being > disconnected. This is because it likes to switch from 8bit to 32bit > depths automatically at startup. Unfortunately, there is a race > condition in the VNC protocol and since this implementation is > asynchronous, we seem to be much more prone to exposing this. > > A short near-term TODO list is: > > 1) More testing > 2) Support switching between monitor/serial > 3) Support a better encoding (like TightEncoding or ZRLE) > 4) Support a vnc password (and perhaps stuff like TLS) > > Any feedback is greatly appreciated (especially with how it works with > clients I've not tested). realvnc on debian-ppc (xvncviewer-3.3.7) has endian issues (the colors are wrong). However, mouse tracking and dragging windows actually *works*. (This is with the version currently in cvs)