From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NJBJ8-0004vm-Bx for qemu-devel@nongnu.org; Fri, 11 Dec 2009 14:37:42 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NJBJ3-0004pV-E9 for qemu-devel@nongnu.org; Fri, 11 Dec 2009 14:37:41 -0500 Received: from [199.232.76.173] (port=50710 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NJBJ3-0004pK-6P for qemu-devel@nongnu.org; Fri, 11 Dec 2009 14:37:37 -0500 Received: from mail-pz0-f188.google.com ([209.85.222.188]:51113) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NJBJ2-0004p5-RL for qemu-devel@nongnu.org; Fri, 11 Dec 2009 14:37:37 -0500 Received: by pzk26 with SMTP id 26so819257pzk.4 for ; Fri, 11 Dec 2009 11:37:35 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20091211212253.3cf5a711@redhat.com> References: <1393046876.1549021260539141025.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com> <4B226BFC.1040606@codemonkey.ws> <20091211204828.464707cf@redhat.com> <20091211210032.425fb640@redhat.com> <4B229847.3060400@codemonkey.ws> <20091211212253.3cf5a711@redhat.com> Date: Fri, 11 Dec 2009 17:37:35 -0200 Message-ID: <5d6222a80912111137q4e4ae95bk6296621bb2d671dc@mail.gmail.com> Subject: Re: [Qemu-devel] Spice project is now open From: Glauber Costa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Izik Eidus Cc: Yaniv Kamay , qemu-devel@nongnu.org On Fri, Dec 11, 2009 at 5:22 PM, Izik Eidus wrote: > On Fri, 11 Dec 2009 13:06:47 -0600 > Anthony Liguori wrote: > >> Izik Eidus wrote: >> > I want to add that qemu is not the sole user of spice, Spice will be >> > used as a protocol to connect into physical windows/linux >> > machines.... >> > >> > So how can we change the library just for qemu? >> > >> A library is not necessarily a problem. >> >> What would be a probably is if the library maintains guest visible >> state. =C2=A0There are a lot of advantages to keeping qemu as the sole >> maintainer of guest visible state as it simplifies things like live >> migration. =C2=A0More importantly, it allows us to do things like Avi's >> suggested security sandboxing using seccomp(). =C2=A0For that to work, w= e >> need to make sure that we can isolate any code that interacts >> directly with the guest. > > Spice guest visible state inside qemu is just its PCI QXL device. > This part is qemu specificed. > But this part can work together with vnc with no problems, right? If this is so, why don't we just start by merging it, while trying to make the case for the rendering protocol in parallel ? --=20 Glauber Costa. "Free as in Freedom" http://glommer.net "The less confident you are, the more serious you have to act."