From: ZhouPeng <zpengxen@gmail.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "wangfeng.v1.1985@gmail.com" <wangfeng.v1.1985@gmail.com>,
"Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>,
Yanjun Wu <yanjun@iscas.ac.cn>,
"zhoupeng@nfs.iscas.ac.cn" <zhoupeng@nfs.iscas.ac.cn>,
Yanjun Wu <yanjun.wu@gmail.com>, ciyiwei <ciyiwei@gmail.com>,
"wangfeng@nfs.iscas.ac.cn" <wangfeng@nfs.iscas.ac.cn>,
"ciyiwei@nfs.iscas.ac.cn" <ciyiwei@nfs.iscas.ac.cn>
Subject: Re: Porting spice to xen
Date: Fri, 8 Apr 2011 10:13:42 +0800 [thread overview]
Message-ID: <BANLkTi=V5TkCRRLVqW_+xwUp8CsVYsbLBg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1104071235560.3290@kaball-desktop>
[-- Attachment #1.1: Type: text/plain, Size: 1457 bytes --]
2011/4/7 Stefano Stabellini <stefano.stabellini@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=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)
<ailvpeng25@gmail.com>
[-- Attachment #1.2: Type: text/html, Size: 2284 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-04-08 2:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 10:54 Porting spice to xen ZhouPeng
2011-04-07 11:39 ` Stefano Stabellini
2011-04-08 2:13 ` ZhouPeng [this message]
2011-04-08 12:23 ` Stefano Stabellini
2011-04-09 10:27 ` ZhouPeng
-- strict thread matches above, loose matches on Subject: below --
2010-11-30 9:40 Porting Spice to Xen Yanjun Wu
2010-11-30 10:36 ` Stefano Stabellini
2009-12-28 16:50 Porting SPICE " David
2010-01-06 12:25 ` Stefano Stabellini
2010-01-07 4:33 ` Thiago Camargo Martins Cordeiro
2010-01-07 11:01 ` Vincent Hanquez
2010-01-07 11:16 ` Daniel P. Berrange
2010-01-08 0:46 ` David
2010-01-11 11:27 ` Vincent Hanquez
2010-01-11 11:57 ` Daniel P. Berrange
2010-01-11 11:57 ` David
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=V5TkCRRLVqW_+xwUp8CsVYsbLBg@mail.gmail.com' \
--to=zpengxen@gmail.com \
--cc=ciyiwei@gmail.com \
--cc=ciyiwei@nfs.iscas.ac.cn \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wangfeng.v1.1985@gmail.com \
--cc=wangfeng@nfs.iscas.ac.cn \
--cc=xen-devel@lists.xensource.com \
--cc=yanjun.wu@gmail.com \
--cc=yanjun@iscas.ac.cn \
--cc=zhoupeng@nfs.iscas.ac.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).