From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49208) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X8Bjk-0006EW-Hs for qemu-devel@nongnu.org; Fri, 18 Jul 2014 13:14:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1X8Bje-0001um-Ux for qemu-devel@nongnu.org; Fri, 18 Jul 2014 13:14:24 -0400 Received: from mx1.redhat.com ([209.132.183.28]:4889) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X8Bje-0001uc-NP for qemu-devel@nongnu.org; Fri, 18 Jul 2014 13:14:18 -0400 Date: Fri, 18 Jul 2014 18:14:09 +0100 From: "Dr. David Alan Gilbert" Message-ID: <20140718171409.GD10517@work-vm> References: <20140717192204.GL2424@work-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140717192204.GL2424@work-vm> Subject: Re: [Qemu-devel] status for rc3/release List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: amit.shah@redhat.com, aik@ozlabs.ru, QEMU Developers , quintela@redhat.com * Dr. David Alan Gilbert (dgilbert@redhat.com) wrote: > * Peter Maydell (peter.maydell@linaro.org) wrote: > > So we just released rc2. The proposed schedule has > > rc3 next Tuesday, with final release the Tuesday after. > > > > My thought is that we should aim for rc3 to add only > > a fairly small number of focussed and "safe" bugfixes, > > with the intention of making the final release be the > > same as rc3 if no showstopper bugs are discovered. > > If there are any showstoppers in rc3 we have a week > > to fix them and roll and test an rc4. > > > > Does it seem to other people like we're on track for that? > > I don't do the level of testing that I think Anthony had > > access to, so I'm reliant on those of you doing testing > > of the rc tarballs to report problems... > > There's something going on with migration; although we're > passing virt-test and my tests with google stress app test, > the thread on virtio-blk failures is one bad thing, and I've > got another failure case (possibly ide cdrom but not obvious) > that seems to be new somewhere between 2.0 and 2.1-rc0. Mine I seem to have bisected down to fe680d0dac85e0f2d6c3b53838c250f6e0b1f49b 'exec: Limit translation limiting in address_space_translate to xen' I'm told this doesn't necessarily make sense, but: works 62622c11f230edddcc47aabe2d988555bf125993 broken fe680d0dac85e0f2d6c3b53838c250f6e0b1f49b (confirmed by running each twice) and : b18a990c - good cab00a5aa - good This is squashfs on a livecd falling apart after migration. Dave > > Dave > -- > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK