[Qemu-devel] status for rc3/release

[Qemu-devel] status for rc3/release

[Peter Maydell]

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...

thanks
-- PMM

Re: [Qemu-devel] status for rc3/release

[Paolo Bonzini]

Il 17/07/2014 11:45, Peter Maydell ha scritto:
> 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.

Here is my queue:

Andreas Färber (2):
      module: Simplify module_load()
      module: Don't complain when a module is absent

		==> you already acked these

Nikolay Nikolaev (2):
      vhost-user: Fix VHOST_SET_MEM_TABLE processing
      qtest: Adapt vhost-user-test to latest vhost-user changes

		==> fix for a feature in 2.1

Paolo Bonzini (3):
      qtest: new test for wdt_ib700

		==> are more tests welcome at this stage?

      Revert "kvmclock: Ensure proper env->tsc value for kvmclock_current_nsec calculation"
      Revert "kvmclock: Ensure time in migration never goes backward"

		==> revert a buggy fix introduced in 2.1

Ricky Zhou (1):
      target-i386: Allow execute from user mode when SMEP is enabled.

		==> fix for a 2.1 regression

Re: [Qemu-devel] status for rc3/release

[Frederic Konrad]

On 17/07/2014 11:45, Peter Maydell 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...
>
> thanks
> -- PMM
>
Hi,

Is it possible to include the "cadence_uart: check serial backend before 
using it."
bug fix.

I think it's relatively safe.

Thanks,
Fred

Re: [Qemu-devel] status for rc3/release

[Stefan Hajnoczi]

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

On Thu, Jul 17, 2014 at 10:45:31AM +0100, Peter Maydell 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?

Sounds good.  There are only a tiny number of block fixes remaining.
I'll send a pull request tomorrow, as usual.

Stefan

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

Re: [Qemu-devel] status for rc3/release

[Dr. David Alan Gilbert]

* 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.

Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

Re: [Qemu-devel] status for rc3/release

[Dr. David Alan Gilbert]

* 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

Re: [Qemu-devel] status for rc3/release

[Paolo Bonzini]

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

Re: [Qemu-devel] status for rc3/release

[Paolo Bonzini]

Il 18/07/2014 22:12, Paolo Bonzini ha scritto:
> Il 18/07/2014 19:14, Dr. David Alan Gilbert ha scritto:
>> * Dr. David Alan Gilbert (dgilbert@redhat.com) wrote:
>> (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?

Got it now from your other message, it's Fedora 20 live.  I guess it's
just about migrating the image while it's loading and/or running.

Maybe something breaks in the dirty bitmap handling.

Paolo

Re: [Qemu-devel] status for rc3/release

[Gerd Hoffmann]

[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]

On Fr, 2014-07-18 at 23:53 +0200, Paolo Bonzini wrote:
> Il 18/07/2014 22:12, Paolo Bonzini ha scritto:
> > Il 18/07/2014 19:14, Dr. David Alan Gilbert ha scritto:
> >> * Dr. David Alan Gilbert (dgilbert@redhat.com) wrote:
> >> (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?
> 
> Got it now from your other message, it's Fedora 20 live.  I guess it's
> just about migrating the image while it's loading and/or running.

Yep.  I have a script[1] doing ping-pong live migration on localhost.
To check out live migration issues I either use a live iso, or do a
fresh install of the guest triggering the issues, with ping-pong live
migration already running during the install.

Any attempt to install fedora doesn't come very far, neither from iso
nor via pxe from network, with all sorts of strange guest behavior
(anaconda crashing or reporting corrupted repodata for example).  Dave
found squashfs errors in the guests kernel log, which explains why
anaconda is crashing.

cheers,
  Gerd

[1] attached.

[-- Attachment #2: migrate-loop --]
[-- Type: application/x-shellscript, Size: 4260 bytes --]

Re: [Qemu-devel] status for rc3/release

[Paolo Bonzini]

Il 21/07/2014 13:15, Gerd Hoffmann ha scritto:
> Yep.  I have a script[1] doing ping-pong live migration on localhost.
> To check out live migration issues I either use a live iso, or do a
> fresh install of the guest triggering the issues, with ping-pong live
> migration already running during the install.
> 
> Any attempt to install fedora doesn't come very far, neither from iso
> nor via pxe from network, with all sorts of strange guest behavior
> (anaconda crashing or reporting corrupted repodata for example).  Dave
> found squashfs errors in the guests kernel log, which explains why
> anaconda is crashing.

Thanks, it doesn't even pass media check here.

I've sent a patch to fix it, and will package it in a pull request tomorrow.

There's another migration issue, I guess either mst or I will look at it
in the next couple  of days.  It will definitely miss rc3, but it's PC only.

Paolo