From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Subject: Porting SPICE to Xen Date: Mon, 28 Dec 2009 16:50:05 +0000 Message-ID: <6894a6470912280850v5b7ad285l6d90f213ef18da0b@mail.gmail.com> Reply-To: admin@dmarkey.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0921159103==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============0921159103== Content-Type: multipart/alternative; boundary=001636457b04881aff047bccb29d --001636457b04881aff047bccb29d Content-Type: text/plain; charset=ISO-8859-1 Has anyone toyed with the idea of porting SPICE to Xen? I've been playing with it and it's quite impressive. As far as I can tell it can run without KVM being loaded so it must run almost entirely in userspace, could it be as simple as applying the xen patches to the "spiced" qemu to make a "spiced" qemu-dm? Any thoughts? --001636457b04881aff047bccb29d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Has anyone toyed with the idea of porting SPICE to Xen? I've been playi= ng with it and it's quite impressive.

As far as I can tell it c= an run without KVM being loaded so it must run almost entirely in userspace= , could it be as simple as applying the xen patches to the "spiced&quo= t; qemu to make a "spiced" qemu-dm?

Any thoughts?
--001636457b04881aff047bccb29d-- --===============0921159103== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0921159103==--