From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
lars.kurth@xen.org,
"George.Dunlap@citrix.com" <George.Dunlap@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Hackathon Minutes] Xen 4.4 Planning
Date: Mon, 17 Jun 2013 10:27:47 +0200 [thread overview]
Message-ID: <51BEC883.1030804@m2r.biz> (raw)
In-Reply-To: <1371137973.6955.30.camel@zakaz.uk.xensource.com>
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
next prev parent reply other threads:[~2013-06-17 8:27 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 14:00 [Hackathon Minutes] Xen 4.4 Planning Lars Kurth
2013-06-13 14:22 ` Jan Beulich
2013-06-13 15:11 ` George Dunlap
2013-06-13 15:30 ` Jan Beulich
2013-06-13 15:39 ` Ian Campbell
2013-06-17 8:27 ` Fabio Fantoni [this message]
2013-06-17 9:52 ` Ian Campbell
2013-06-13 14:31 ` Ian Campbell
2013-06-13 14:52 ` George Dunlap
2013-06-13 15:06 ` Ian Campbell
2013-06-14 17:41 ` Konrad Rzeszutek Wilk
2013-06-13 14:43 ` George Dunlap
2013-06-13 17:09 ` Ben Guthro
2013-06-13 18:07 ` Pasi Kärkkäinen
2013-06-13 21:03 ` Alex Bligh
2013-06-13 23:56 ` Ian Murray
2013-06-14 7:01 ` Alex Bligh
2013-06-14 9:46 ` Ian Murray
2013-06-14 11:53 ` Alex Bligh
2013-06-14 12:32 ` Ian Murray
2013-06-14 12:49 ` Alex Bligh
2013-06-14 13:34 ` Ian Murray
2013-06-14 13:55 ` Ian Campbell
2013-06-14 14:44 ` Ian Murray
2013-06-14 14:55 ` Gordan Bobic
2013-06-14 15:00 ` George Dunlap
2013-06-14 15:09 ` Ian Campbell
2013-06-14 15:43 ` Alex Bligh
2013-06-14 21:05 ` Ian Murray
2013-06-19 21:22 ` Alex Bligh
2013-06-14 15:44 ` Alex Bligh
2013-06-14 17:25 ` Konrad Rzeszutek Wilk
2013-06-14 8:15 ` Jan Beulich
2013-06-14 9:47 ` George Dunlap
2013-06-14 9:59 ` Lars Kurth
2013-06-14 10:45 ` Jan Beulich
2013-06-14 11:19 ` George Dunlap
2013-06-14 11:30 ` Gordan Bobic
2013-06-14 12:10 ` Sander Eikelenboom
2013-06-14 10:44 ` George Dunlap
-- strict thread matches above, loose matches on Subject: below --
2013-06-14 11:46 Alex Bligh
2013-06-14 12:26 ` Jan Beulich
2013-06-14 12:45 ` Alex Bligh
2013-06-14 18:55 Alex Bligh
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=51BEC883.1030804@m2r.biz \
--to=fabio.fantoni@m2r.biz \
--cc=George.Dunlap@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=george.dunlap@eu.citrix.com \
--cc=lars.kurth@xen.org \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.