This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Porting spice to xen

To: "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Porting spice to xen
From: ZhouPeng <zpengxen@xxxxxxxxx>
Date: Thu, 7 Apr 2011 18:54:52 +0800
Cc: wangfeng.v1.1985@xxxxxxxxx, Yanjun Wu <yanjun@xxxxxxxxxxx>, zhoupeng@xxxxxxxxxxxxxxx, Yanjun Wu <yanjun.wu@xxxxxxxxx>, ciyiwei <ciyiwei@xxxxxxxxx>, wangfeng@xxxxxxxxxxxxxxx, ciyiwei@xxxxxxxxxxxxxxx
Delivery-date: Thu, 07 Apr 2011 03:55:46 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=fSBBD94AYbZ28+zHGg/9TNqM5dWXWRI0WZLVjqNNQcU=; b=F8H+yKgNYA9rsmEi7/TzM5hWRiyM2XeVfM/05ghi0pSldW9WOXv1Ee+iPfci533LPl PQfwldx8stJkHWoNWbhPhaPomzBl69DNV2bRm5gBHbJQeqwa0A1Y+ibgvTeNG4EGkJ36 70WMhW4Wie+Td5s4f+hm9vZ6hLDmfBBUqDFvw=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=cZoubMF/3O0xtxe8dJ+K896NW79yl/oVxO5ZuhpGaA0D59RIyOAEjZHKwYXnJ2wu6G PlomohLIDw7N8zFDzvTyUU3eXd/Ho5ogAOwY9dmv698dmYSDtPiAjVXSP5C9scKo0jhX pKGPvc31ZpgyA1nqHjln9l8Vs2alXz5/sVlp0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi all,

We have tried to port spice to Xen (Xen 4.0.1, Dom0 kernel 2.6.18).
The current porting allows basic spice run for xen-fv.

Now We are trying to port the qxl component, but it's difficult
because of the big difference between xen-qemu and upstream qemu.
If you enable the qxl device in our current porting(do it by setting
'qxl=1' in xm config file), you are most likely to get a mess screen.

So any help in qxl porting will be much appreciated.

Our work is shared here: http://code.google.com/p/spice4xen/

It's not be a good way to port spice to xen-qemu because of tremendous
difference. But before the Xen with upstream-qemu supported has been
released and runs stable, it may be a choice.

Zhou Peng
Operating System Technology Group
Institute of Software, the Chinese Academy of Sciences (ISCAS)

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>