Re: [Xen-devel] [Hackathon Minutes] Xen 4.4 Planning

[Fabio Fantoni <fabio.fantoni@xxxxxxx>]

About release time, I think probably a good choice could be the 3 months 
of development + 1 of testing but with Debian style: a minimum of 1 
month for testing and, if there are critical/important bugs, one more 
week until it will be solved.
About features for 4.4, I think that in the first post list some very 
good features already discussed are missing:
- Improve hvm domUs integration adding configure parameters to allow 
usage of packaged qemu and seabios instead of compiling the internal one.
About seabios and qemu upstream patch for configure already discussed 
with Ian Campbell, I tried to make a quick patch but failed (I couldn't 
find the right configure parameters to do it and the exact part to 
change on libxl for qemu upstream binary path), I can't find the 
discussion about it at the moment.
- Add support for SSE and AVX for the hvm domU to improve performance 
and solve qxl problem (qxl requires SSE):
http://bugs.xenproject.org/xen/bug/11

- Improve Spice support in libxl:
* vdagent, working and tested, patch already posted: 
http://lists.xen.org/archives/html/xen-devel/2013-05/msg00484.html
* usbredirection (different from usb passthrough: from spice client to 
qemu instead of from dom0 to qemu), working and tested, I want improve 
the patch before posting it, it doesn't look good but I'll post it anyway.
* support auto select of port similar to vnc, I'll probably try to make 
the patch.
* support spice also on pv domU as an alternative to vnc, I don't have 
enough knowledge to try to do it now.

What do you think?
Thanks for any reply

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel