From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Peter Lieven <pl@kamp.de>, qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-stable] [ANNOUNCE] QEMU 2.6.1 Stable released
Date: Thu, 25 Aug 2016 12:23:45 -0500 [thread overview]
Message-ID: <20160825172345.17599.42638@loki> (raw)
In-Reply-To: <8e3ac487-a3ee-1aef-2240-4c388e0004f7@kamp.de>
Quoting Peter Lieven (2016-08-25 01:38:13)
> Am 17.08.2016 um 21:30 schrieb Michael Roth:
> > Hi everyone,
> >
> > I am pleased to announce that the QEMU v2.6.1 stable release is now
> > available:
> >
> > http://wiki.qemu.org/download/qemu-2.6.1.tar.bz2
> >
> > v2.6.1 is now tagged in the official qemu.git repository,
> > and the stable-2.6 branch has been updated accordingly:
> >
> > http://git.qemu.org/?p=qemu.git;a=shortlog;h=refs/heads/stable-2.6
> >
> > This is a fairly large update that addresses a broad range of bugs
> > and security issues. Users should upgrade accordingly.
> >
> > Thank you to everyone involved!
>
> Hi Michael,
>
> thanks for putting this together. Unfortunately, I was on holiday during
> the patch round up for 2.6.1
>
> I additionally have the following 5 patches in case you want or need to
> release a 2.6.1.1 or 2.6.2:
>
> bd9f480 ui: fix refresh of VNC server surface
> 4c23084 net: limit allocation in nc_sendv_compat
I don't see these in master yet.
> bf97c17 iscsi: pass SCSI status back for SG_IO
I'll pull this in if there's another release, but doesn't look
like a regression from 2.6.0 at least.
> 7c509d1 virtio: decrement vq->inuse in virtqueue_discard()
> 700f26b virtio: recalculate vq->inuse after migration
Looks like these got posted during the freeze :(
>
> The virtio thing is important because live migration is broken without
> the fix as 86cc089 is in 2.6.1.
Not sure I understand the relation to 86cc089. Wouldn't the check
introduced there always pass due to target initializing inuse to 0?
Or is the issue that the fix introduced in 86cc089 is only partially
effective due to inuse not being recalculated properly on target? That might
warrant a 2.6.1.1...
>
> Thanks,
> Peter
>
next prev parent reply other threads:[~2016-08-25 17:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 19:30 [Qemu-devel] [ANNOUNCE] QEMU 2.6.1 Stable released Michael Roth
2016-08-25 6:38 ` [Qemu-devel] [Qemu-stable] " Peter Lieven
2016-08-25 17:23 ` Michael Roth [this message]
2016-08-26 11:45 ` Peter Lieven
2016-09-05 17:54 ` Stefan Hajnoczi
2016-09-08 20:58 ` Michael Roth
2016-09-13 15:42 ` Stefan Hajnoczi
2016-09-13 15:52 ` Peter Lieven
2016-09-13 18:04 ` Michael Roth
2016-09-13 20:16 ` Peter Lieven
2016-09-16 13:56 ` Peter Lieven
2016-09-27 10:28 ` Peter Lieven
2016-09-27 11:30 ` Peter Lieven
2016-09-28 19:52 ` Michael Roth
2016-09-30 8:17 ` Peter Lieven
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=20160825172345.17599.42638@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.