Posting a bit late this week, due to public holidays in the UK.
I'm on vacation the next two Mondays 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
I'm not going get caught out making another guess at when we start
RCs, lets just go with "when it's ready" ;-). I think we are
edging closer...
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)
* [BUG] Spurious CPU params error message when starting a domain,
e.g. "Cpu weight out of range, valid values are within range
from 1 to 65535". (Ian C, DONE)
* More formally deprecate xm/xend. Manpage patches already in
tree. Needs release noting and communication around -rc1 to
remind people to test xl.
* Domain 0 block attach & general hotplug when using qdisk backend
(need to start qemu as necessary etc) (Stefano S, DONE)
* calling hotplug scripts from xl (Linux and NetBSD) (Roger Pau
Monné, patches posted, nearing completion?)
* 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, patches posted)
hypervisor, nice to have:
* PoD performance improvements (George Dunlap)
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, patches posted)
* libxl stable API
* libxl_*_path. Majority made internal, only configdir and
lockdir remain public. Used by xl therefore move to xl?
(IanC, DONE)
* libxl_wait_for_free_memory/libxl_wait_for_memory_target.
Interface needs an overhaul, related to
locking/serialization over domain create (deferred to
4.3). 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)
* [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
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel