[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Xen 4.5-rc1 update (RC1 is out 2014-Oct-24th)

On 27/10/14 08:39, Paul Durrant wrote:
>> -----Original Message-----
>> From: Andrew Cooper [mailto:amc96@xxxxxxxxxxxxxxxx] On Behalf Of
>> Andrew Cooper
>> Sent: 24 October 2014 20:17
>> To: konrad.wilk@xxxxxxxxxx; Wei Liu; m.a.young@xxxxxxxxxxxx;
>> tiejun.chen@xxxxxxxxx; avanzini.arianna@xxxxxxxxx;
>> boris.ostrovsky@xxxxxxxxxx; ufimtseva@xxxxxxxxx;
>> guijianfeng@xxxxxxxxxxxxxx; Eddie Dong; jgross@xxxxxxxx; Roger Pau
>> Monne; artem.mygaiev@xxxxxxxxxxxxxxx; Ian Jackson;
>> daniel.kiper@xxxxxxxxxx; Ian Campbell; Kelly.Zytaruk@xxxxxxx; Anthony
>> Perard; mukesh.rathor@xxxxxxxxxx; dslutz@xxxxxxxxxxx;
>> aravindp@xxxxxxxxx; josh.whitehead@xxxxxxxxxxxxxxx;
>> robert.vanvossen@xxxxxxxxxxxxxxx; Paul.Skentzos@xxxxxxxxxxxxxxx;
>> Steve.VanderLeest@xxxxxxxxxxxxxxx; andrii.tseglytskyi@xxxxxxxxxxxxxxx;
>> yang.z.zhang@xxxxxxxxx; Ross Lagerwall; Malcolm Crossley; George Dunlap;
>> bob.liu@xxxxxxxxxx; yjhyun.yoo@xxxxxxxxxxx;
>> serge.broslavsky@xxxxxxxxxx; christoffer.dall@xxxxxxxxxx; olaf@xxxxxxxxx;
>> wency@xxxxxxxxxxxxxx; Dave Scott; davi.d.vrabel@xxxxxxxxxx;
>> yanghy@xxxxxxxxxxxxxx; zhigang.x.wang@xxxxxxxxxx; msw@xxxxxxxxxx;
>> julien.grall@xxxxxxxxxx; xen-devel@xxxxxxxxxxxxxxxxxxxx; Stefano Stabellini;
>> tklengyel@xxxxxxxxxxxxx; suriyan.r@xxxxxxxxx; vijay.kilari@xxxxxxxxx;
>> Vijaya.Kumar@xxxxxxxxxxxxxxxxxx; talex5@xxxxxxxxx;
>> parth.dixit@xxxxxxxxxx; roy.franz@xxxxxxxxxx; chao.p.peng@xxxxxxxxxxxxxxx;
>> mengxu@xxxxxxxxxxxxx; rcojocaru@xxxxxxxxxxxxxxx; feng.wu@xxxxxxxxx;
>> Aravind.Gopalakrishnan@xxxxxxx; Suravee.Suthikulpanit@xxxxxxx; Paul
>> Durrant; Dario Faggioli; mcgrof@xxxxxxxx
>> Subject: Re: Xen 4.5-rc1 update (RC1 is out 2014-Oct-24th)
>> On 24/10/2014 19:08, konrad.wilk@xxxxxxxxxx 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=['<bdf'] wherein the '<bdf>' 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!] <==== <WE ARE HERE>
>>> * 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.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.