From: Roger Pau Monne <roger.pau@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.2 TODO / Release Plan
Date: Mon, 18 Jun 2012 09:36:52 +0100 [thread overview]
Message-ID: <4FDEE8A4.1080500@citrix.com> (raw)
In-Reply-To: <1339506046.24104.30.camel@zakaz.uk.xensource.com>
Ian Campbell wrote:
> A bit late this week, due to my being on vacation. I'm on vacation
> next two Monday as well so it will be late then too.
>
> 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
>
> The updated TODO list follows. 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.
>
> 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)
>
> Other than that I think we should consider the freeze to be in full
> effect and the bar to entry to 4.2 to be very high.
>
> hypervisor, blockers:
>
> * None
>
> 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:
>
> * LIBXL_NIC_TYPE enum names are confusing.
>
> * Interfaces which may need to be async:
>
> * libxl_domain_suspend. Move xc_domain_save/restore into a
> separate process (IanJ, patches posted).
>
> * libxl_device_{disk,nic,vkb,add,pci}_add (and
> remove). (Roger, patches posted for disk& nic, vkb
> trivial, not looked at pci yet)
>
> * use libxl_cpumap for b_info.avail_cpus instead of an int,
> this"allows setting more than 31 CPUS (Yang Z Zhang, patches
> posted)
>
> * use an enum for VGA interface type (e.g. Cirrus,
> StdVGA). Allows for QXL support (in 4.3). (Zhou Peng,
> patches posted)
>
> * 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, patches reposted, under review)
>
> * 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é, patches posted)
Another round posted (v6), waiting for review.
>
> * 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)
>
> * Confirm that migration from Xen 4.1 -> 4.2 works...
>
> * [BUG] Build failure due to gcc -Wswitch on some distros
> vs. LIBXL_DOMAIN_TYPE. (Dario Faggioli, DONE)
>
> hypervisor, nice to have:
>
> * PoD performance improvements (George Dunlap, patches posted)
>
> 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: Add API to retrieve domain console tty (Bamvor Jian
> Zhang, DONE)
>
> * 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)
>
> * qemu-upstream for NetBSD (Roger)
Patch committed to netbsd kernel, awaiting approval.
>
> * [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
>
>
>
>
> _______________________________________________
> 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
next prev parent reply other threads:[~2012-06-18 8:36 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 13:00 Xen 4.2 TODO / Release Plan Ian Campbell
2012-06-12 13:57 ` Jan Beulich
2012-06-12 14:05 ` Ian Campbell
2012-06-13 10:48 ` Stefano Stabellini
2012-06-20 15:25 ` Ian Campbell
2012-06-20 15:40 ` Jan Beulich
2012-06-20 15:47 ` Ian Jackson
2012-06-20 16:06 ` Jan Beulich
2012-06-20 15:50 ` Ian Campbell
2012-06-20 15:58 ` Ian Jackson
2012-06-20 15:46 ` Ian Jackson
2012-06-18 8:36 ` Roger Pau Monne [this message]
2012-06-18 12:19 ` Dario Faggioli
-- strict thread matches above, loose matches on Subject: below --
2012-08-28 10:06 Ian Campbell
2012-08-31 17:26 ` George Dunlap
2012-09-03 9:10 ` Ian Campbell
2012-08-31 17:36 ` George Dunlap
[not found] ` <CAFLBxZaDmZ8bTQzZ_CpQpTros9WFK7Q96v-1Y3zXXWLdciMXTw@mail.gmail.com>
2012-08-31 17:42 ` Konrad Rzeszutek Wilk
2012-09-02 4:46 ` Pasi Kärkkäinen
2012-09-03 9:09 ` Ian Campbell
2012-08-20 9:17 Ian Campbell
2012-08-20 11:06 ` Jan Beulich
2012-08-21 15:14 ` Ren, Yongjie
2012-08-21 15:27 ` Ian Campbell
2012-08-21 15:49 ` Ren, Yongjie
2012-08-21 15:39 ` Ben Guthro
2012-08-21 16:08 ` Jan Beulich
2012-08-14 9:05 Ian Campbell
2012-08-14 9:52 ` Jan Beulich
2012-08-15 15:46 ` George Dunlap
2012-07-30 8:30 Ian Campbell
2012-08-03 10:09 ` Ian Campbell
2012-08-03 10:28 ` Keir Fraser
2012-08-03 10:30 ` Ian Campbell
2012-08-03 10:44 ` Jan Beulich
2012-08-06 17:06 ` Liu, Jinsong
2012-08-07 6:38 ` Jan Beulich
2012-08-07 7:50 ` Keir Fraser
2012-08-07 8:05 ` Jan Beulich
2012-08-07 8:10 ` Ian Campbell
2012-08-07 18:13 ` Liu, Jinsong
2012-08-08 6:37 ` Jan Beulich
2012-07-17 16:47 Ian Campbell
2012-07-17 16:51 ` Andrew Cooper
2012-05-21 11:47 Ian Campbell
2012-05-21 13:00 ` Pasi Kärkkäinen
2012-05-21 13:05 ` Ian Campbell
2012-05-21 13:32 ` Jan Beulich
2012-05-14 10:26 Ian Campbell
2012-05-14 11:14 ` Jan Beulich
2012-05-29 9:32 ` Ian Campbell
2012-05-29 10:10 ` Jan Beulich
2012-05-31 9:24 ` Olaf Hering
2012-05-31 9:37 ` Jan Beulich
2012-05-31 9:56 ` Stefano Stabellini
2012-05-31 21:43 ` Olaf Hering
2012-05-14 13:51 ` Dario Faggioli
2012-05-14 15:33 ` Ian Jackson
2012-05-14 15:43 ` Ian Campbell
2012-05-14 17:07 ` Dario Faggioli
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=4FDEE8A4.1080500@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).