[Qemu-devel] last call for bugs that need to be fixed for 2.6 release!

[Qemu-devel] last call for bugs that need to be fixed for 2.6 release!

[Peter Maydell]

Hi; looking at http://wiki.qemu.org/Planning/2.6#Known_issues and
the mailing list we seem to be in reasonable shape for the 2.6 release.
I would ideally like the 2.6rc3 tarball which we will make later this
week to be the final one before full release.

This is therefore the last call for any bugs that need to be fixed
for 2.6 or patches that must go in. If you have anything you think
should go into 2.6 please either add it to the "still unfixed in
master" part of the planning wiki page or follow up to this email to
describe it/link to the relevant patches/etc.

thanks
-- PMM

Re: [Qemu-devel] last call for bugs that need to be fixed for 2.6 release!

[Mark Cave-Ayland]

On 18/04/16 12:22, Peter Maydell wrote:

> Hi; looking at http://wiki.qemu.org/Planning/2.6#Known_issues and
> the mailing list we seem to be in reasonable shape for the 2.6 release.
> I would ideally like the 2.6rc3 tarball which we will make later this
> week to be the final one before full release.
> 
> This is therefore the last call for any bugs that need to be fixed
> for 2.6 or patches that must go in. If you have anything you think
> should go into 2.6 please either add it to the "still unfixed in
> master" part of the planning wiki page or follow up to this email to
> describe it/link to the relevant patches/etc.

I'd like to nominate the patch Aurelien posted earlier today which fixes
the RTC for the Mac g3beige/mac99 machines:
https://lists.nongnu.org/archive/html/qemu-devel/2016-04/msg02682.html.


ATB,

Mark.

Re: [Qemu-devel] last call for bugs that need to be fixed for 2.6 release!

[Samuel Thibault]

Hello,

Peter wrote:
> Hi; looking at http://wiki.qemu.org/Planning/2.6#Known_issues and
> the mailing list we seem to be in reasonable shape for the 2.6 release.
> I would ideally like the 2.6rc3 tarball which we will make later this
> week to be the final one before full release.
> 
> This is therefore the last call for any bugs that need to be fixed
> for 2.6 or patches that must go in. If you have anything you think
> should go into 2.6 please either add it to the "still unfixed in
> master" part of the planning wiki page or follow up to this email to
> describe it/link to the relevant patches/etc.

I'd be really useful to fix pv-grub boot when using xenfb, see the patch
I have just submitted on

http://lists.nongnu.org/archive/html/qemu-devel/2016-04/msg02741.html

Samuel

Re: [Qemu-devel] last call for bugs that need to be fixed for 2.6 release!

[Peter Maydell]

On 18 April 2016 at 12:22, Peter Maydell <peter.maydell@linaro.org> wrote:
> This is therefore the last call for any bugs that need to be fixed
> for 2.6 or patches that must go in. If you have anything you think
> should go into 2.6 please either add it to the "still unfixed in
> master" part of the planning wiki page or follow up to this email to
> describe it/link to the relevant patches/etc.

Hi Stefan -- I see you added "update the translation po/ files"
to the list. Can you remind me how to do this? I think it's
just "make -C po update", which seems to update the creation
date timestamps and a bunch of the line number references.
Do I need to do anything else, or just commit that automatic
change?

thanks
-- PMM

Re: [Qemu-devel] last call for bugs that need to be fixed for 2.6 release!

[Stefan Weil]

Am 18.04.2016 um 15:02 schrieb Peter Maydell:
> On 18 April 2016 at 12:22, Peter Maydell <peter.maydell@linaro.org> wrote:
>> This is therefore the last call for any bugs that need to be fixed
>> for 2.6 or patches that must go in. If you have anything you think
>> should go into 2.6 please either add it to the "still unfixed in
>> master" part of the planning wiki page or follow up to this email to
>> describe it/link to the relevant patches/etc.
> Hi Stefan -- I see you added "update the translation po/ files"
> to the list. Can you remind me how to do this? I think it's
> just "make -C po update", which seems to update the creation
> date timestamps and a bunch of the line number references.
> Do I need to do anything else, or just commit that automatic
> change?
>
> thanks
> -- PMM


Hi Peter,

yes, that's exactly the way how to do it.

Regards

Stefan

Re: [Qemu-devel] last call for bugs that need to be fixed for 2.6 release!

[Peter Maydell]

On 18 April 2016 at 14:44, Stefan Weil <sw@weilnetz.de> wrote:
> Am 18.04.2016 um 15:02 schrieb Peter Maydell:
>> Hi Stefan -- I see you added "update the translation po/ files"
>> to the list. Can you remind me how to do this? I think it's
>> just "make -C po update", which seems to update the creation
>> date timestamps and a bunch of the line number references.
>> Do I need to do anything else, or just commit that automatic
>> change?

> yes, that's exactly the way how to do it.

Weirdly, I just tried to repeat this, but make says
"Nothing to be done for `update'." It worked the first
time I did it... I think this is because a 'git reset'
ends up resetting the timestamps on the *.po files in
the source tree to the time of the checkout. I had to
'touch ui/gtk.c' to get update to do something.

thanks
-- PMM

Re: [Qemu-devel] last call for bugs that need to be fixed for 2.6 release!

[David Gibson]

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

On Mon, Apr 18, 2016 at 01:23:06PM +0100, Mark Cave-Ayland wrote:
> On 18/04/16 12:22, Peter Maydell wrote:
> 
> > Hi; looking at http://wiki.qemu.org/Planning/2.6#Known_issues and
> > the mailing list we seem to be in reasonable shape for the 2.6 release.
> > I would ideally like the 2.6rc3 tarball which we will make later this
> > week to be the final one before full release.
> > 
> > This is therefore the last call for any bugs that need to be fixed
> > for 2.6 or patches that must go in. If you have anything you think
> > should go into 2.6 please either add it to the "still unfixed in
> > master" part of the planning wiki page or follow up to this email to
> > describe it/link to the relevant patches/etc.
> 
> I'd like to nominate the patch Aurelien posted earlier today which fixes
> the RTC for the Mac g3beige/mac99 machines:
> https://lists.nongnu.org/archive/html/qemu-devel/2016-04/msg02682.html.

Seconded, since I believe that's a regression.  I'm planning to double
check it and send a pull request tomorrow.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: [Qemu-devel] last call for bugs that need to be fixed for 2.6 release!

[Kevin Wolf]

Am 18.04.2016 um 13:22 hat Peter Maydell geschrieben:
> Hi; looking at http://wiki.qemu.org/Planning/2.6#Known_issues and
> the mailing list we seem to be in reasonable shape for the 2.6 release.
> I would ideally like the 2.6rc3 tarball which we will make later this
> week to be the final one before full release.
> 
> This is therefore the last call for any bugs that need to be fixed
> for 2.6 or patches that must go in. If you have anything you think
> should go into 2.6 please either add it to the "still unfixed in
> master" part of the planning wiki page or follow up to this email to
> describe it/link to the relevant patches/etc.

Jeff, I still don't see a v2 gluster patch to avoid data corruption
after I/O errors. I think we agreed that we definitely need this in 2.6.

Kevin

Re: [Qemu-devel] last call for bugs that need to be fixed for 2.6 release!

[Jeff Cody]

On Tue, Apr 19, 2016 at 11:10:12AM +0200, Kevin Wolf wrote:
> Am 18.04.2016 um 13:22 hat Peter Maydell geschrieben:
> > Hi; looking at http://wiki.qemu.org/Planning/2.6#Known_issues and
> > the mailing list we seem to be in reasonable shape for the 2.6 release.
> > I would ideally like the 2.6rc3 tarball which we will make later this
> > week to be the final one before full release.
> > 
> > This is therefore the last call for any bugs that need to be fixed
> > for 2.6 or patches that must go in. If you have anything you think
> > should go into 2.6 please either add it to the "still unfixed in
> > master" part of the planning wiki page or follow up to this email to
> > describe it/link to the relevant patches/etc.
> 
> Jeff, I still don't see a v2 gluster patch to avoid data corruption
> after I/O errors. I think we agreed that we definitely need this in 2.6.
>

Yes, I'm working on a good test for the patch still.  I'll go ahead and send
the patch for any comments now, though, and hopefully can have the testing
done later today.

Re: [Qemu-devel] last call for bugs that need to be fixed for 2.6 release!

[Kevin Wolf]

Am 18.04.2016 um 13:22 hat Peter Maydell geschrieben:
> Hi; looking at http://wiki.qemu.org/Planning/2.6#Known_issues and
> the mailing list we seem to be in reasonable shape for the 2.6 release.
> I would ideally like the 2.6rc3 tarball which we will make later this
> week to be the final one before full release.
> 
> This is therefore the last call for any bugs that need to be fixed
> for 2.6 or patches that must go in. If you have anything you think
> should go into 2.6 please either add it to the "still unfixed in
> master" part of the planning wiki page or follow up to this email to
> describe it/link to the relevant patches/etc.

We got two late fixes for bugs in the mirror block job, one resulting in
a crash, the other one in an inexact image copy:

[PATCH for-2.6 0/2] block/mirror: Fix mirroring with guest I/O load
[PATCH for-2.6 v2 0/3] block: Fix drive-mirror with image size unaligned with granularity

Sounds to me as if we wanted to have both of them in 2.6.

Kevin

Re: [Qemu-devel] last call for bugs that need to be fixed for 2.6 release!

[Markus Armbruster]

Peter Maydell <peter.maydell@linaro.org> writes:

> Hi; looking at http://wiki.qemu.org/Planning/2.6#Known_issues and
> the mailing list we seem to be in reasonable shape for the 2.6 release.
> I would ideally like the 2.6rc3 tarball which we will make later this
> week to be the final one before full release.
>
> This is therefore the last call for any bugs that need to be fixed
> for 2.6 or patches that must go in. If you have anything you think
> should go into 2.6 please either add it to the "still unfixed in
> master" part of the planning wiki page or follow up to this email to
> describe it/link to the relevant patches/etc.

[PATCH for-2.6 0/3] Fix dangling pointers and error message regressions

1+2/3 are small and simple.  We can punt 3/3 to -stable if the patch
looks too big for rc4.

Re: [Qemu-devel] last call for bugs that need to be fixed for 2.6 release!

[Samuel Thibault]

Hello,

Peter wrote:
> Hi; looking at http://wiki.qemu.org/Planning/2.6#Known_issues and
> the mailing list we seem to be in reasonable shape for the 2.6 release.
> I would ideally like the 2.6rc3 tarball which we will make later this
> week to be the final one before full release.
> 
> This is therefore the last call for any bugs that need to be fixed
> for 2.6 or patches that must go in. If you have anything you think
> should go into 2.6 please either add it to the "still unfixed in
> master" part of the planning wiki page or follow up to this email to
> describe it/link to the relevant patches/etc.

We very probably want to fix slirp on Darwin, see thread starting at

http://lists.nongnu.org/archive/html/qemu-devel/2016-04/msg03868.html

and patch submitted for review on 

http://lists.nongnu.org/archive/html/qemu-devel/2016-04/msg04262.html

Samuel

Re: [Qemu-devel] last call for bugs that need to be fixed for 2.6 release!

[Kevin Wolf]

Am 18.04.2016 um 13:22 hat Peter Maydell geschrieben:
> Hi; looking at http://wiki.qemu.org/Planning/2.6#Known_issues and
> the mailing list we seem to be in reasonable shape for the 2.6 release.
> I would ideally like the 2.6rc3 tarball which we will make later this
> week to be the final one before full release.
> 
> This is therefore the last call for any bugs that need to be fixed
> for 2.6 or patches that must go in. If you have anything you think
> should go into 2.6 please either add it to the "still unfixed in
> master" part of the planning wiki page or follow up to this email to
> describe it/link to the relevant patches/etc.

This one fixes a crash with vvfat in rw mode, so it would probably be
nice to have it in:

[PATCH v2 1/2] vvfat: Fix volume name assertion

The other patch in the series fixes a rather minor regression, so I
don't have a strong opinion on whether to take it for 2.6 or not. In any
case, the series still needs final review.

Kevin