qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>
Cc: amit.shah@redhat.com, aik@ozlabs.ru,
	QEMU Developers <qemu-devel@nongnu.org>,
	quintela@redhat.com
Subject: Re: [Qemu-devel] status for rc3/release
Date: Fri, 18 Jul 2014 22:12:27 +0200	[thread overview]
Message-ID: <53C97FAB.9020500@redhat.com> (raw)
In-Reply-To: <20140718171409.GD10517@work-vm>

Il 18/07/2014 19:14, Dr. David Alan Gilbert ha scritto:
> * 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.

Can you give precise reproduction instructions before leaving?  Which OS
is being installed?

Paolo

  reply	other threads:[~2014-07-18 20:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17  9:45 [Qemu-devel] status for rc3/release Peter Maydell
2014-07-17 12:32 ` Paolo Bonzini
2014-07-17 13:09 ` Frederic Konrad
2014-07-17 18:28 ` Stefan Hajnoczi
2014-07-17 19:22 ` Dr. David Alan Gilbert
2014-07-18 17:14   ` Dr. David Alan Gilbert
2014-07-18 20:12     ` Paolo Bonzini [this message]
2014-07-18 21:53       ` Paolo Bonzini
2014-07-21 11:15         ` Gerd Hoffmann
2014-07-21 16:39           ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53C97FAB.9020500@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=aik@ozlabs.ru \
    --cc=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).