[XenPPC] Fwd: [Xen-devel] 3.0.3 freeze

[Hollis Blanchard <hollisb@xxxxxxxxxx>]

The code that we have upstream in xen-unstable right now will not
successfully launch a domU, and because those changes will be relatively
invasive (especially splitting xc_linux_build()), I will not be trying
to fix that before 3.0.3 is released (which will likely be weeks at
least).

I don't expect anybody here much cares, but just letting folks know
what's going on. Carry on with xenppc-unstable... :)

-- 
Hollis Blanchard
IBM Linux Technology Center

-------- Forwarded Message --------
From: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] 3.0.3 freeze
Date: Tue, 22 Aug 2006 17:03:27 +0100

Folks,

I think its time to declare a 3.0.3 feature freeze. We've got all the
'must have' feature patches in -unstable and many of the 'would be nice'
variety too.

Just to summarize, we have: the new scheduler, blktap with file-based VM
storage, upgraded device emulation, new shadow pagetable code, PV
drivers for HVM guests, networking support for segmentation offload,
support for the Power architecture, misc performance optimizations and
bug fixes.

There were a number of patches that haven't quite made the cut off due
to various outstanding issues or lack of review time: The NUMA allocator
patch has been observed to cause problems on at least one system. The PV
framebuffer could do with a few interface tweaks and a code cleanup. The
kexec/kdump patch just needs more testing [I feel bad about this one --
maybe we can retrofit it]. The xend lifecycle management patches will be
held-over to the next release so it can become part of a larger set of
control tool changes.

Now the tree is in 'freeze' state, please can everyone get ready to do
some serious testing. We're still working on a handful of known issues
we can reproduce, so this message isn't quite a full call to arms for
testing from the user community yet, but it would be great if developers
could start giving it a workout.  

Thanks,
Ian

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ppc-devel