On Mon, 20 May 2019 16:14:32 +1000
David Gibson wrote:
> On Fri, May 17, 2019 at 07:14:30PM +0200, Greg Kurz wrote:
> > On Fri, 17 May 2019 14:18:23 +1000
> > David Gibson wrote:
> >
> > > spapr machine capabilities are supposed to be sent in the migration stream
> > > so that we can sanity c
On Fri, May 17, 2019 at 07:14:30PM +0200, Greg Kurz wrote:
> On Fri, 17 May 2019 14:18:23 +1000
> David Gibson wrote:
>
> > spapr machine capabilities are supposed to be sent in the migration stream
> > so that we can sanity check the source and destination have compatible
> > configuration. Unf
On Fri, 17 May 2019 14:18:23 +1000
David Gibson wrote:
> spapr machine capabilities are supposed to be sent in the migration stream
> so that we can sanity check the source and destination have compatible
> configuration. Unfortunately, when we added the hpt-max-page-size
> capability, we forgot
On 5/17/19 6:18 AM, David Gibson wrote:
> spapr machine capabilities are supposed to be sent in the migration stream
> so that we can sanity check the source and destination have compatible
> configuration. Unfortunately, when we added the hpt-max-page-size
> capability, we forgot to add it to the
spapr machine capabilities are supposed to be sent in the migration stream
so that we can sanity check the source and destination have compatible
configuration. Unfortunately, when we added the hpt-max-page-size
capability, we forgot to add it to the migration state. This means that we
can genera
