xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Roger Pau Monne <roger.pau@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: Xen 4.2 Release Plan / TODO
Date: Wed, 4 Jul 2012 18:08:51 +0100	[thread overview]
Message-ID: <4FF478A3.9080406@citrix.com> (raw)
In-Reply-To: <1341226929.4625.20.camel@zakaz.uk.xensource.com>

Ian Campbell wrote:
> Plan for a 4.2 release:
> http://lists.xen.org/archives/html/xen-devel/2012-03/msg00793.html
>
> The time line is as follows:
>
> 19 March        -- TODO list locked down
> 2 April         -- Feature Freeze
>                                                  <<  WE ARE HERE
> When It's Ready -- First release candidate
> Weekly          -- RCN+1 until release
>
> Lots of DONE this week which is good, including one of the big three
> remaining issues (libxl_domain_suspend asyncification) has gone in
> now. Still to come are Roger's hotplug script changes (which acutally
> cover multiple items on the list) and Dario's basic NUMA support, both
> of which I think are almost there.
>
> The updated TODO list follows.
>
> If you are aware of any bugs which must/should be fixed for 4.2 then
> please reply to this thread (otherwise I may not remember to pick them
> up next week)
>
> Per the release plan a strong case will now have to be made as to why
> new items should be added to the list, especially as a blocker, rather
> than deferred to 4.3.
>
> hypervisor, blockers:
>
>      * [BUG] stub domains broken. HVM_PARAM_DM_DOMAIN needs to reset
>        HVM_PARAM_BUFIOREQ_EVTCHN (Anthony Perard, patch sent, reviewed,
>        awaiting repost)
>
> tools, blockers:
>
>      * 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:
>
>          * Interfaces which may need to be async:
>
>              * libxl_domain_suspend. Move xc_domain_save/restore into a
>                separate process (Ian Jackson, DONE).
>
>              * libxl_device_{disk,nic,vkb,add,pci}_add (and
>                remove). (Roger Pau Monné, disk&  nic included in
>                calling hotplug scripts from xl, vkb
>                trivial, not looked at pci yet)
>
>          * LIBXL_NIC_TYPE enum names are confusing. (Roger, included in
>            calling hotplug scripts series)
>
>          * use libxl_cpumap for b_info.avail_cpus instead of an int,
>            this allows setting more than 31 CPUS (Yang Z Zhang, DONE)
>
>          * use an enum for VGA interface type (e.g. Cirrus,
>            StdVGA). Allows for QXL support (in 4.3). (Zhou Peng, DONE)
>
>      * xl compatibility with xm:
>
>          * [BUG] cannot create an empty CD-ROM drive on HVM guest,
>            reported by Fabio Fantoni in<4F9672DD.2080902@tiscali.it>
>
>          * does not automatically try to select a (set of) node(s) on
>            which to create a VM and pin its vcpus there. (Dario
>            Faggioli, posted and reviewed, awaiting a repost)
>
>      * [CHECK] More formally deprecate xm/xend. Manpage patches already
>        in tree. Needs release noting and communication around -rc1 to
>        remind people to test xl.
>
>      * calling hotplug scripts from xl (Linux and NetBSD) (Roger Pau
>        Monné, waiting on another iteration)

Posted v8.

>
>      * Block script support -- follows on from hotplug script (Roger
>        Pau Monné, "just be a matter of removing an "if"")
>
>      * Adjustments needed for qdisk backend to work on non-pvops Linux.
>        "qemu/xendisk: set maximum number of grants to be used" (Jan
>        Beulich, DONE for both qemu-xen-upstream and
>        qemu-xen-traditional)
>
>      * [CHECK] Confirm that migration from Xen 4.1 ->  4.2 works.
>
>      * [BUG] LIBLEAFDIR et al and libfsimage do the wrong thing on
>        modern Debian/Ubuntu w/ multiarch capabilities (Matt Wilson,
>        patch posted)
>
>      * libxl to reject attempts to migrate a domain using upstream
>        qemu, due to lack of log dirty support (Ian C, patch sent,
>        reviewed, awaiting repost)
>
> hypervisor, nice to have:
>
>      * PoD performance improvements (George Dunlap, DONE)
>
>      * vMCE save/restore changes, to simplify migration 4.2->4.3
>       (Jinsong Liu)
>
> tools, nice to have:
>
>      * xl compatibility with xm:
>
>          * Accept "xl cr /dev/null param=value" to provide all config
>            on the command line (W. Michael Petullo, patch posted)
>
>      * libxl stable API
>
>          * libxl_wait_for_free_memory/libxl_wait_for_memory_target.
>            Interface needs an overhaul, related to
>            locking/serialization over domain create. IanJ to add note
>            about this interface being substandard but otherwise defer
>            to 4.3.
>
>          * Interfaces which may need to be async:
>
>              * libxl_cdrom_insert. Should be easy once
>                disk_{add,remove} done. This is basically a helper
>                function and its functionality can be implemented in
>                terms of the libxl_disk_* interfaces. If this is not
>                done in time we should document as a substandard
>                interface which is subject to change post 4.2.
>
>      * xl.cfg(5) documentation patch for qemu-upstream
>        videoram/videomem support:
>        http://lists.xen.org/archives/html/xen-devel/2012-05/msg00250.html
>        qemu-upstream doesn't support specifying videomem size for the
>        HVM guest cirrus/stdvga.  (but this works with
>        qemu-xen-traditional). (Pasi Kärkkäinen)
>
>      * [BUG] long stop during the guest boot process with qcow image,
>        reported by Intel: http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1821
>
>      * [BUG] vcpu-set doesn't take effect on guest, reported by Intel:
>        http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1822
>
>      * Load blktap driver from xencommons initscript if available, thread at:
>        <db614e92faf743e20b3f.1337096977@kodo2>. To be fixed more
>        properly in 4.3. (Patch posted, discussion, plan to take simple
>        xencommons patch for 4.2 and revist for 4.3)
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel


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

  parent reply	other threads:[~2012-07-04 17:08 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-02 11:02 Xen 4.2 Release Plan / TODO Ian Campbell
2012-07-03  7:52 ` Jan Beulich
2012-07-03 10:45   ` Anthony PERARD
2012-07-04 16:42 ` Dario Faggioli
2012-07-04 17:08 ` Roger Pau Monne [this message]
2012-07-13  9:55   ` Roger Pau Monne
  -- strict thread matches above, loose matches on Subject: below --
2012-06-26  8:39 Ian Campbell
2012-06-26 20:31 ` Matt Wilson
2012-06-26 21:09   ` Konrad Rzeszutek Wilk
2012-06-26 22:57     ` Matt Wilson
2012-06-27  8:41       ` Ian Campbell
2012-06-28  8:56       ` Ren, Yongjie
2012-06-27 13:12 ` Jan Beulich
2012-06-27 14:52   ` Ian Campbell
2012-06-27 14:57     ` Jan Beulich
2012-06-27 15:01       ` Ian Campbell
2012-06-27 15:36         ` Jan Beulich
2012-06-28 15:18 ` Tim Deegan
2012-06-20 11:29 Ian Campbell
2012-06-20 11:43 ` Andrew Cooper
2012-06-20 13:07   ` Jan Beulich
2012-06-20 13:19     ` Andrew Cooper
2012-06-20 19:29       ` Andrew Cooper
2012-06-26  8:16         ` Ian Campbell
2012-04-10 10:24 Ian Campbell
2012-04-12  9:56 ` George Dunlap
2012-04-12 10:24 ` Dario Faggioli
2012-04-12 11:00   ` Ian Campbell
2012-04-02 10:26 Ian Campbell
2012-04-02 10:39 ` David Vrabel
2012-04-02 10:43   ` Ian Campbell
2012-04-02 11:17 ` George Dunlap
2012-04-02 14:41 ` Stefano Stabellini
2012-04-11 16:11 ` Ian Jackson
2012-04-11 16:13   ` Ian Jackson
2012-04-12  7:42     ` Ian Campbell
2012-04-12  7:35   ` Ian Campbell
2012-04-12  7:59     ` Ian Campbell
2012-04-12 16:37       ` Dan Magenheimer
2012-04-12 16:45         ` Ian Campbell
2012-04-13 15:28           ` Dan Magenheimer
2012-04-13 10:45         ` Ian Jackson
2012-04-13 19:45           ` Dan Magenheimer
2012-04-16 10:16             ` Ian Jackson
2012-04-12  8:16     ` Ian Campbell
2012-04-24 17:52       ` Ian Jackson
2012-03-27  9:34 Ian Campbell
2012-03-27 18:30 ` Shriram Rajagopalan
2012-03-19 10:57 Ian Campbell
2012-03-19 11:25 ` Jan Beulich
2012-03-19 11:33   ` Ian Campbell
2012-03-19 12:02     ` Jan Beulich
2012-03-19 12:13   ` Stefano Stabellini
2012-03-19 12:13 ` George Dunlap
2012-03-19 12:28   ` Ian Campbell
2012-03-20  5:19 ` Matt Wilson
2012-03-20  8:42   ` Ian Campbell
2012-03-22  9:21 ` Ian Campbell
2012-03-22  9:22 ` Ian Campbell
2012-03-22 10:22   ` Stefano Stabellini
2012-03-22  9:35 ` George Dunlap
2012-03-22  9:53   ` Ian Campbell
2012-03-22 10:08     ` George Dunlap
2012-03-22 10:19       ` Ian Campbell
2012-03-22 10:31         ` Keir Fraser
2012-03-22 10:34         ` George Dunlap
2012-03-22 10:38           ` Ian Campbell
2012-03-27  9:33             ` Ian Campbell
2012-03-27 10:19               ` George Dunlap

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=4FF478A3.9080406@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).