From mboxrd@z Thu Jan 1 00:00:00 1970 From: ZhouPeng Subject: Re: Porting spice to xen Date: Fri, 8 Apr 2011 10:13:42 +0800 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1193099478==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefano Stabellini Cc: "wangfeng.v1.1985@gmail.com" , "Xen-Devel (E-mail)" , Yanjun Wu , "zhoupeng@nfs.iscas.ac.cn" , Yanjun Wu , ciyiwei , "wangfeng@nfs.iscas.ac.cn" , "ciyiwei@nfs.iscas.ac.cn" List-Id: xen-devel@lists.xenproject.org --===============1193099478== Content-Type: multipart/alternative; boundary=00504502c40b5f0fa504a05ec6a1 --00504502c40b5f0fa504a05ec6a1 Content-Type: text/plain; charset=ISO-8859-1 2011/4/7 Stefano Stabellini > On Thu, 7 Apr 2011, ZhouPeng wrote: > > 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. > > I think that porting spice and qxl to the current qemu-xen tree is not > worth the effort, considering that we are very close to having xen > support in upstream qemu right now. > Good news. How long will it be released? Also if you don't want to wait for xen support to go upstream in qemu > you can checkout Anthony Perard's git qemu branch and work directly on > it: > > git://xenbits.xen.org/people/aperard/qemu-dm.git qemu-dm-v12 > -- Zhou Peng Operating System Technology Group Institute of Software, the Chinese Academy of Sciences (ISCAS) --00504502c40b5f0fa504a05ec6a1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

2011/4/7 Stefano Stabellini <stefano.stabe= llini@eu.citrix.com>
On Thu, 7 Apr 2011, ZhouPeng wrote:
> 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=3D1' in xm config file), you are most likely to get a mes= s 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 tremen= dous
> difference. But before the Xen with upstream-qemu supported has been > released and runs stable, it may be a choice.

I think that porting spice and qxl to the current qemu-xen tree is no= t
worth the effort, considering that we are very close to having xen
support in upstream qemu right now.
=A0
=A0 = Good news. How long will it be released?

Also if you don't want to wait for xen support to go upstream in qemu you can checkout Anthony Perard's git qemu branch and work directly on<= br> it:

git://xenbits.xen.org/people/aperard/qemu-dm.git qemu-dm-v12

--
Zhou Peng
Operating System Technology Grou= p
Institute of Software, the Chinese Academy of Sciences (ISCAS)

--00504502c40b5f0fa504a05ec6a1-- --===============1193099478== 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 --===============1193099478==--