From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JynxU-00089E-Ex for qemu-devel@nongnu.org; Wed, 21 May 2008 09:02:20 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JynxS-00088q-GW for qemu-devel@nongnu.org; Wed, 21 May 2008 09:02:19 -0400 Received: from [199.232.76.173] (port=35230 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JynxS-00088m-Bv for qemu-devel@nongnu.org; Wed, 21 May 2008 09:02:18 -0400 Received: from mx1.redhat.com ([66.187.233.31]:57473) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JynxS-0003wW-6S for qemu-devel@nongnu.org; Wed, 21 May 2008 09:02:18 -0400 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m4LD2CdB005041 for ; Wed, 21 May 2008 09:02:12 -0400 Received: from file.fab.redhat.com (file.fab.redhat.com [10.33.63.6]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m4LD2B64030198 for ; Wed, 21 May 2008 09:02:11 -0400 Received: (from berrange@localhost) by file.fab.redhat.com (8.13.1/8.13.1/Submit) id m4LD2ARg006226 for qemu-devel@nongnu.org; Wed, 21 May 2008 14:02:10 +0100 Date: Wed, 21 May 2008 14:02:10 +0100 From: "Daniel P. Berrange" Subject: Re: [Qemu-devel] Sensible VNC encodings Message-ID: <20080521130210.GA3915@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Reply-To: "Daniel P. Berrange" , 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 On Wed, May 21, 2008 at 07:55:37AM +0200, Alexander Graf wrote: > > On May 21, 2008, at 3:20 AM, Johannes Schindelin wrote: > > >Hi, > > > >for those interested, I finally broke down and updated my personal > >fork of > >QEmu using LibVNCServer. Amongst the benefits are Tight, ZRLE and > >ZYWRLE > >encodings. Note that TLS is not supported with LibVNCServer, but > >nobody > >in her right mind uses VNC without an SSH tunnel anyway. > > It might be a good idea to have this as an additional output, not as a > replacement for the VNC support as it is now. Think of a system, where > libvncserver is not available. [snip] > I personally prefer reusage of code, so the general idea of using > libvncserver is great! My experiance with libvncserver has not been at all pleasant, finding it to be seriously crash happy and near impossible to debug, particuarly with its multithread code. We used to use it in Xen for the paravirt framebuffer server but because of its unreliability, libvncserver was ripped out and now Xen hooks into the QEMU VNC server code instead. While QEMU's existing code may not support as many encodings, it is it clearly written, easy to debug and doesn't crash. If there's more encodings we need to support for performance then IMHO they should be added to the existing code. Dan. -- |: Red Hat, Engineering, Boston -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|