From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NJBJr-0005x4-3I for qemu-devel@nongnu.org; Fri, 11 Dec 2009 14:38:27 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NJBJm-0005pp-6R for qemu-devel@nongnu.org; Fri, 11 Dec 2009 14:38:26 -0500 Received: from [199.232.76.173] (port=59658 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NJBJl-0005pV-W5 for qemu-devel@nongnu.org; Fri, 11 Dec 2009 14:38:22 -0500 Received: from mail-yw0-f179.google.com ([209.85.211.179]:50683) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NJBJl-0004tv-Lq for qemu-devel@nongnu.org; Fri, 11 Dec 2009 14:38:21 -0500 Received: by ywh9 with SMTP id 9so1177295ywh.19 for ; Fri, 11 Dec 2009 11:38:20 -0800 (PST) Message-ID: <4B229FAA.8010606@codemonkey.ws> Date: Fri, 11 Dec 2009 13:38:18 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Spice project is now open References: <1393046876.1549021260539141025.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com> <4B226BFC.1040606@codemonkey.ws> <20091211204828.464707cf@redhat.com> <4B2297A2.8040102@codemonkey.ws> <1260559510.29755.14.camel@blaa> In-Reply-To: <1260559510.29755.14.camel@blaa> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mark McLoughlin Cc: Yaniv Kamay , Izik Eidus , qemu-devel@nongnu.org Mark McLoughlin wrote: > On Fri, 2009-12-11 at 13:04 -0600, Anthony Liguori wrote: > >> But to introduce another protocol where a user has to make a choice to >> use Spice over VNC, I think we need a really good justification for >> that. It's really about complexity. A user shouldn't have to know >> about Spice or VNC. They shouldn't have to contemplate the trade-offs >> of whether their management tool is aware or not. It should Just Work. >> > > That's a good goal. > > If we add a new protocol, we could achieve the same thing by allowing > qemu support both VNC and Spice at runtime. Then you just need a client > like virt-viewer that can handle both protocols, and old VNC clients > will continue to be able to connect to newer qemu. > Supporting them at the same time could be potentially challenging. You would need to render Spice locally in qemu in order to expose it via vnc. Another nasty bit is that two protocols mean two different sets of authentication mechanisms. Does Spice support SASL based authentication? Could it make sense to essentially tunnel Spice through vnc in order to reuse the existing authentication infrastructure? Regards, Anthony Liguori