[Spice-devel] Port spice to Xen
The Ha
tha at math.ubc.ca
Thu Apr 7 08:25:32 PDT 2011
Dear Zhou Peng
I am much appreciated your group effort to contribute to FOSS.
I would love to see your group help KVM/Spice instead of focus on Xen port.
Here are few thing to reconsider.
KVM is young but it's an unstoppable train. Even Vmware consider KVM
is direct competitor to their Esxi but not XEN.
There is a huge exodus XEN to KVM from our Univeristy and many other shops.
IBM, Ubuntu, Eucalyptus, OpenStack (Nasa) and the list are growing daily.
They all KVM supportors and if you ask, we don't look back.
Another thing when using Spice is the connection broker that build around KVM.
Unless you want to build the Broker/Admin, Spice can't scale.
Back to Spice project. They can really use experts coder like your group.
Mac ports, Smart Device ports, mature from 0.xx to 1.x is much desirable.
Just look at the In-Progress and you see what I mean.
Much Aprreciate your group effort regardless of your decision.
Thanks for Reading.
Best
The Ha
On Thu, 7 Apr 2011, Zhou Peng 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.
>
> Best,
> --
> Zhou Peng
> Operating System Technology Group
> Institute of Software, the Chinese Academy of Sciences (ISCAS)
>
Alternate Email <the.ha at ubc.ca>
More information about the Spice-devel
mailing list