[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] RFC: Still TODO for 4.2?

On 01/04/2012 11:25 AM, Pasi Kärkkäinen wrote:
On Wed, Jan 04, 2012 at 04:29:22PM +0000, Ian Campbell wrote:
What are the outstanding things to do before we think we can start on
the 4.2 -rc's? Does anyone have a timetable in mind?


       * ??? - Keir, Tim, Jan?


       * libxl stable API -- we would like 4.2 to define a stable API
         which downstream's can start to rely on not changing. Aspects of
         this are:
               * event handling (IanJ working on this)
               * drop libxl_device_model_info (move bits to build_info or
                 elsewhere as appropriate) (IanC working on this, patches
               * add libxl_defbool and generally try and arrange that
                 memset(foo,0,...) requests the defaults (IanC working on
                 this, patches shortly)
               * The topologyinfo datastructure should be a list of
                 tuples, not a tuple of lists. (nobody currently looking
                 at this, not 100% sure this makes sense, could possibly
                 defer and change after 4.2 in a compatible way)
               * Block script support -- can be done post 4.2?
       * Hotplug script stuff -- internal to libxl (I think, therefore I
         didn't put this under stable API above) but still good to have
         for 4.2? Roger Pau Monet was looking at this but its looking
         like a big can-o-worms...
       * Integrate qemu+seabios upstream into the build (Stefano has
         posted patches, I guess they need refreshing and reposting). No
         change in default qemu for 4.2.
       * More formally deprecate xm/xend. Manpage patches already in
         tree. Needs release noting and communication around -rc1 to
         remind people to test xl.

Has anybody got anything else? I'm sure I've missed stuff. Are there any
must haves e.g. in the paging/sharing spaces?

- What's the status of Nested Hardware Virtualization?
I remember some email saying Intel vmx-on-vmx has some performance issues,
and amd svm-on-svm works better..

- Also there's a bunch of VGA passthru related patches,
that I once volunteered to collect/rebase/cleanup/repost myself,
but I still haven't had time for that :(
Since there were quite a lot of interest on this subject, should we document it in a separate wiki for working combinations (like hypervisor, dom0, gfx card, driver version, tricks, etc)?

-- Pasi

Xen-devel mailing list

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.