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

Re: [Xen-devel] Xen 4.3 development update



On 09/20/2012 10:53 AM, Jean Guyader wrote:
On 19 September 2012 17:58, George Dunlap <George.Dunlap@xxxxxxxxxxxxx> wrote:
= Timeline =

We are planning on a 9-month release cycle.  Based on that, below are
our estimated dates:
* Feature Freeze: 1 March, 2013
* First RC: 15 April 2013
* Release: 1 June 2013

The RCs and release will of course depend on stability and bugs, and
will therefore be fairly unpredictable.  The feature freeze may be
slipped for especially important features which are near completion.

= Feature tracking =

Below is a list of features we're tracking for this release.  Please
respond to this mail with any updates to the status.  If the status
is "?", as most of them are, please respond with the status!  Example
statuses include "not started", "in progress", "initial implementation
submitted for review", "patches submitted".

There are a number of items whose owners are marked as "?".  If you
are working on this, or know who is working on it, please respond and
let me know.  Alternately, if you would *like* to work on it, please
let me know as well.

And if there is something you're working on you'd like tracked, please
respond, and I will add it to the list.


* PVH mode, domU (w/ Linux)
   owner: mukesh@oracle
   status: ?

* PVH mode, dom0 (w/ Linux)
   owner: mukesh@oracle
   status: ?

* Event channel scalability
   owner: attilio@citrix
   status: ?
   Increase limit on event channels (currently 1024 for 32-bit guests,
   4096 for 64-bit guests)

* ARM server port
   owner: ijc@citrix
   status: Core hypervisor patches accepted; Linux paches pending

* NUMA scheduler affinity
   critical
   owner: dario@citrix
   status: ?

* NUMA Memory migration
   owner: dario@citrix
   status: ?

* blktap3
   owner: thanos@citrix
   status: ?

* Default to QEMU upstream
  - qemu-based stubdom (Linux or BSD libc)
    owner: anthony@citrix
    status: ?
    qemu-upstream needs a more fully-featured libc than exists in
    minios.  Either work on a minimalist linux-based stubdom with
    glibc, or port one of the BSD libcs to minios.

  - pci pass-thru
    owner: anthony@citrix
    status: ?

* Persistent grants
   owner: @citrix
   status: ?

* Multi-page blk rings
  - blkback in kernel (konrad@oracle, ?@intel)
  - qemu blkback
   status: ?

* Multi-page net protocol
   owner: ?
   status: ?
   expand the network ring protocol to allow multiple pages for
   increased throughput

* Scalability: 16TiB of RAM
   owner: jan@suse
   status: ?

* libvirt integration
   owner: ?
   status: ?
   To begin with, we need someone to go and make some lists:
   - Features available in libvirt/KVM not available in libvirt/Xen
   - Features available in xl/Xen but not available in libvirt/Xen

* xl vm-{export,import}
   owner: ?
   status: ?
   Allow xl to import and export VMs to other formats; particularly
   ovf, perhaps the XenServer format, or more.


* xl USB pass-through for PV guests
   owner: ?
   status: ?
   - Port the xend PV pass-through functionality to xl.
   - Make sure qemu-based USB with qemu-upstream works
   - Upstream the Linux frontend/backend drivers

* openvswitch toostack integration
   owner: roger@citrix
   status: Sample script posted by Bastian ("[RFC] openvswitch support script")

* Rationalized backend scripts (incl. driver domains)
   owner: roger@citrix
   status: ?

* Linux console improvements
   owner: jan@suse
   -EHCI debug port (done, to be submitted)
   -xHCI debug port
   -Firewire

* CPUID-based idle (don't rely on ACPI info f/ dom0)
   owner: jan@suse
   status: done, to be submitted

* Remove hardcoded mobprobe's in xencommons
   owner: ?
   status: ?

* Make storage migration possible
   owner: ?
   status: ?
   There needs to be a way, either via command-line or via some hooks,
   that someone can build a "storage migration" feature on top of libxl
   or xl.

* Full-VM snapshotting
   owner: ?
   status: ?
   Have a way of coordinating the taking and restoring of VM memory and
   disk snapshots.  This would involve some investigation into the best
   way to accomplish this.

* VM Cloning
   owner: ?
   status: May need review
   Again, a way of coordinating the memory and disk aspects.  Research
   into the best way to do this would probably go along with the
   snapshotting feature.

* Memory: Replace PoD with paging mechanism
   owner: george@citrix
   status: May need review

* PV audio (audio for stubdom qemu)
   owner: stefano.panella@citrix
   status: ?

* Managed domains?

Hi George,

Maybe we could had V4V in the list.

* V4V: Inter-domain communication
   owner (Xen): jean.guyader@xxxxxxxxxx
   status (Xen): patches submitte
   owner (Linux driver):  stefano.panella@citrix
   status (Linux driver): in progress
As Jean has mentioned, I agree to take ownership of the linux driver for v4v.

Thanks,
Jean

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


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


 


Rackspace

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