From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Xen 4.5-rc1 update (RC1 is out 2014-Oct-24th) Date: Mon, 27 Oct 2014 10:01:00 +0000 Message-ID: <544E17DC.9010309@citrix.com> References: <20141024180843.EA0DF10D709@laptop.dumpdata.com> <544AA594.8010404@citrix.com> <9AAE0902D5BC7E449B7C8E4E778ABCD011134A18@AMSPEX01CL01.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Xih6w-0003Hv-J8 for xen-devel@lists.xenproject.org; Mon, 27 Oct 2014 10:01:14 +0000 In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD011134A18@AMSPEX01CL01.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Paul Durrant , "konrad.wilk@oracle.com" , Wei Liu , "m.a.young@durham.ac.uk" , "tiejun.chen@intel.com" , "avanzini.arianna@gmail.com" , "boris.ostrovsky@oracle.com" , "ufimtseva@gmail.com" , "guijianfeng@cn.fujitsu.com" , Eddie Dong , "jgross@suse.com" , Roger Pau Monne , "artem.mygaiev@globallogic.com" , Ian Jackson , "daniel.kiper@oracle.com" , Ian Campbell , "Kelly.Zytaruk@amd.com" , Anthony Perard , "mukesh.rathor@oracle.com" List-Id: xen-devel@lists.xenproject.org On 27/10/14 08:39, Paul Durrant wrote: >> -----Original Message----- >> From: Andrew Cooper [mailto:amc96@hermes.cam.ac.uk] On Behalf Of >> Andrew Cooper >> Sent: 24 October 2014 20:17 >> To: konrad.wilk@oracle.com; Wei Liu; m.a.young@durham.ac.uk; >> tiejun.chen@intel.com; avanzini.arianna@gmail.com; >> boris.ostrovsky@oracle.com; ufimtseva@gmail.com; >> guijianfeng@cn.fujitsu.com; Eddie Dong; jgross@suse.com; Roger Pau >> Monne; artem.mygaiev@globallogic.com; Ian Jackson; >> daniel.kiper@oracle.com; Ian Campbell; Kelly.Zytaruk@amd.com; Anthony >> Perard; mukesh.rathor@oracle.com; dslutz@verizon.com; >> aravindp@cisco.com; josh.whitehead@dornerworks.com; >> robert.vanvossen@dornerworks.com; Paul.Skentzos@dornerworks.com; >> Steve.VanderLeest@dornerworks.com; andrii.tseglytskyi@globallogic.com; >> yang.z.zhang@intel.com; Ross Lagerwall; Malcolm Crossley; George Dunlap; >> bob.liu@oracle.com; yjhyun.yoo@samsung.com; >> serge.broslavsky@linaro.org; christoffer.dall@linaro.org; olaf@aepfle.de; >> wency@cn.fujitsu.com; Dave Scott; davi.d.vrabel@citrix.com; >> yanghy@cn.fujitsu.com; zhigang.x.wang@oracle.com; msw@amazon.com; >> julien.grall@linaro.org; xen-devel@lists.xenproject.org; Stefano Stabellini; >> tklengyel@sec.in.tum.de; suriyan.r@gmail.com; vijay.kilari@gmail.com; >> Vijaya.Kumar@caviumnetworks.com; talex5@gmail.com; >> parth.dixit@linaro.org; roy.franz@linaro.org; chao.p.peng@linux.intel.com; >> mengxu@cis.upenn.edu; rcojocaru@bitdefender.com; feng.wu@intel.com; >> Aravind.Gopalakrishnan@amd.com; Suravee.Suthikulpanit@amd.com; Paul >> Durrant; Dario Faggioli; mcgrof@suse.com >> Subject: Re: Xen 4.5-rc1 update (RC1 is out 2014-Oct-24th) >> >> On 24/10/2014 19:08, konrad.wilk@oracle.com wrote: >>> Feature patchsets that did not make it in by today have been put >>> on the deferred list. If you think your feature should make it in Xen 4.5-rc2 >>> please make your case. >>> >>> Xen 4.5-rc1 is out today. There are some issues (see 'Known Issues' below) >>> which are to be fixed in RC2. The official test-day is on Wednesday (Oct >> 29th) >>> but if you want to start testing it today - please do! >>> >>> Details for the test-day are at >>> >>> http://wiki.xen.org/wiki/Xen_4.5_RC1_test_instructions >>> >>> In terms of bugs, we have: >>> >>> #6 linux: pv drivers miss shutdown command if issued too early >>> #8 "linux, xenbus mutex hangs when rebooting dom0 and guests hung." >>> #11 qxl hypervisor support >>> #13 Re: [Xen-devel] man page example: xm block-attach >>> #18 xl improve support for migration over non-sshlike tunnels >>> #19 xl migrate transport improvements >>> #22 xl does not support specifying virtual function for passthrough device >>> #23 Remove arbitrary LIBXL_MAXMEM_CONSTANT from libxl, see what >> breaks >>> #24 xl missing support for encrypted VNC >>> #27 Re: [Xen-devel] xend vs xl with pci=['' are not >> owned by pciback or pcistub will still launch. >>> #28 support PCI hole resize in qemu-xen >>> #30 libxl should implement non-suspend-cancel based resume path >>> #36 credit2 only uses one runqueue instead of one runq per socket >>> #38 Implement VT-d large pages so we can avoid sharing between EPT >>> #40 linux pvops: fpu corruption due to incorrect assumptions >>> #42 "linux, S3 resume of PVHVM fails - missing call to >> xen_arch_post_suspend?" >>> #43 "30s delay loading xenfb driver on some systems" >>> #44 Security policy ambiguities - XSA-108 process post-mortem >>> >>> And we should start closing them if they are fixed. >>> >>> >>> = Timeline = >>> >>> We are planning on a 9-month release cycle. Based on that, below are >>> our estimated dates: >>> >>> >>> * Feature Freeze: 24th September 2014 >>> * First RC: 24th October [Friday!] <==== >>> * RC2: Unknown. Need to talk to maintainers on scheduling. >>> * RC2: Unknown. Need to talk to maintainers on scheduling. >>> * Release: 10th December 2014 >>> >>> 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. >>> >>> Bug-fixes, if Acked-by by maintainer, can go anytime before the First >>> RC. Later on we will need to figure out the risk of regression/reward >>> to eliminate the possiblity of a bug introducing another bug. >>> >>> = Prognosis = >>> >>> The states are: none -> fair -> ok -> good -> done >>> >>> none - nothing yet >>> fair - still working on it, patches are prototypes or RFC >>> ok - patches posted, acting on review >>> good - some last minute pieces >>> done - all done, might have bugs >>> >>> = Feature freeze exception = >>> >>> Remember our goal for the release: >>> 1. A bug-free release >>> 2. An awesome release >>> 3. An on-time release >>> >>> Accepting a new feature may make Xen more awesome; but it also >>> introduces a risk that it will introduce more bugs. That bug may be >>> found before the release (threatening #3), or it may not be found >>> until after the release (threatening #1). Each freeze exception >>> request will attempt to balance the benefits (how awesome the >>> exception is) vs the risks (will it cause the release to slip, or >>> worse, cause a bug which goes un-noticed into the final release). >>> >>> The idea is that today we will be pretty permissive, but that we will >>> become progressively more conservative until the first RC, which is >>> scheduled for 3 weeks' time (October 25). After that, we will only >>> accept bug fixes. >>> >>> Bug fixes can be checked in without a freeze exception throughout the >>> code freeze, unless the maintainer thinks they are particularly high >>> risk. In later RC's, we may even begin rejecting bug fixes if the >>> broken functionality is small and the risk to other functionality is >>> high. >>> >>> Features which are currently marked "experimental" or do not at the >>> moment work at all cannot be broken really; so changes to code only >>> used by those features should be able to get a freeze exception >>> easily. >>> >>> Features which change or add new interfaces which will need to be >>> supported in a backwards-compatible way (for instance, vNUMA) will >>> need freeze exceptions to make sure that the interface itself has >>> enough time to be considered stable. >>> >>> These are guidelines and principles to give you an idea where we're >>> coming from; if you think there's a good reason why making an >>> exception for you will help us achieve goals 1-3 above better than not >>> doing so, feel free to make your case. >>> >>> = Open = >>> >>> == Known issues == >>> >>> * Systemd integration >>> Affects CentOS7, SLES12, Fedora Core 21 and Debian Jessie. Xen source >> contains systemd files that can be used to configure the various run-time >> services. In the past the distributions would carry their own version of it - but >> now we host them. This is not yet complete - >> [[http://lists.xenproject.org/archives/html/xen-devel/2014- >> 10/msg03064.html patches]] for this are being worked on for RC2. >>> - Wei and Olaf >>> >>> * Stubdomains build issues >>> stubdomains will not build. Fix is in staging (and will make RC2) or >> [[http://lists.xen.org/archives/html/xen-devel/2014-10/msg02925.html >> stubdom/Makefile should use QEMU_TRADITIONAL_LOC]] >>> - Michael Young >>> >>> * Building against libxl (outside code) >>> If you are building against libxl for any APIs before Xen 4.5 you will >> encounter building errors. >>> - Andrew Cooper >>> >>> * Migrating large Windows guests can cause WMI service to hang >>> Patch is in 'staging' and will be in RC2. >> What is this in reference to? I can't see any patches relevant to >> windows in staging. >> > I assume this in reference to http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=f6a07643e1cc0045c2a8eabb0fb106e8655ce25d Quite, but that is already in rc1, hence the query. ~Andrew