On Mon, 12 Feb 2018 16:13:23 +0000
"Dr. David Alan Gilbert" <dgilbert@redhat.com> wrote:
> * Peter Lieven (pl@kamp.de) wrote:
> > Am 06.02.2018 um 20:14 schrieb Michael Roth:
> > > Hi everyone,
> > >
> > > The following new patches are queued for QEMU stable v2.11.1:
> > >
> > > https://github.com/mdroth/qemu/commits/stable-2.11-staging
> > >
> > > The release is planned for 2017-02-14:
> > >
> > > https://wiki.qemu.org/Planning/2.11
> > >
> > > Please respond here or CC qemu-stable@nongnu.org on any patches you
> > > think should be included in the release.
> > >
> > > Of particular importance would be any feedback on the various QEMU
> > > patches relating to Spectre/Meltdown mitigation. The current tree has
> > > what I understand to be the QEMU components required for x86, s390,
> > > and pseries, but feedback/confirmation from the various authors would
> > > be greatly appreciated.
> >
> > Hi,
> >
> > I also found the following patches that affect migration:
> >
> > migration: Don't leak IO channels
> > migration: Recover block devices if failure in device state
> > migration/savevm.c: set MAX_VM_CMD_PACKAGED_SIZE to 1ul << 32
> >
> > In general it seems that migration related patches are often not tagged qemu-stable.
> > David, can you check if there are patches missing?
>
> I'm always a bit cautious about forwarding stuff to stable; just because
> it's landed in our main branch it doesn't mean many people have tested
> it, so I'd rather wait unless it was particularly urgent.
>
> The 'migration: Recover block devices if failure in device state' is
> probably a good candidate.
> Another one would be Greg Kurz's:
> 875fcd013ab68c64802998b22f54f0184479d21b - migration: incoming postcopy advise sanity checks
>
Yeah. Mike pushed it to its stable-2.11-staging tree:
https://github.com/mdroth/qemu/commit/a3fd64f2fe9f90c7b4d002910a54049ee6a09b64
Cheers,
--
Greg
> Dave
>
> > Thank you,
> > Peter
> >
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>