From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NJXbz-0006jN-0g for qemu-devel@nongnu.org; Sat, 12 Dec 2009 14:26:39 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NJXbu-0006i0-Gj for qemu-devel@nongnu.org; Sat, 12 Dec 2009 14:26:38 -0500 Received: from [199.232.76.173] (port=57995 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NJXbu-0006hx-Dm for qemu-devel@nongnu.org; Sat, 12 Dec 2009 14:26:34 -0500 Received: from mail-yx0-f188.google.com ([209.85.210.188]:62163) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NJXbu-0003Uf-Ev for qemu-devel@nongnu.org; Sat, 12 Dec 2009 14:26:34 -0500 Received: by yxe26 with SMTP id 26so1840043yxe.4 for ; Sat, 12 Dec 2009 11:26:33 -0800 (PST) Message-ID: <4B23EE66.8080101@codemonkey.ws> Date: Sat, 12 Dec 2009 13:26:30 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: Spice project is now open References: <20091211213911.0dce90dc@redhat.com> <4B22A2D9.6020602@codemonkey.ws> <20091211223250.129675fc@redhat.com> <4B22B035.3010601@codemonkey.ws> <20091211233158.22e6681f@redhat.com> <4B22C093.2090806@codemonkey.ws> <4B231182.1080208@codemonkey.ws> <20091212144433.GA26966@random.random> <4B23B0BE.7080408@codemonkey.ws> <20091212160626.GB26966@random.random> <4B23D585.70400@codemonkey.ws> <20091212194836.7d94bb71@redhat.com> In-Reply-To: <20091212194836.7d94bb71@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Izik Eidus Cc: Andrea Arcangeli , Paolo Bonzini , qemu-devel@nongnu.org Izik Eidus wrote: > On Sat, 12 Dec 2009 11:40:21 -0600 > Anthony Liguori wrote: > > >> FWIW, I don't see any reason why Spice couldn't be made to be >> separate from guest emulation. I think it would just require the >> right interfacing in qemu. I think that's purely an implementation >> detail. >> > > The QXL device is one of the core compoments of spice..., how can you > separate it from the guest visible state? (it is pci device) > How does live migration work then? Do you have to query libspice for it's state? Does it return an opaque blob? How can it integrate with VMState since libspice doesn't have any knowledge of something like VMState? Regards, Anthony Liguori