On Mon, 2014-12-01 at 15:25 -0500, Konrad Rzeszutek Wilk wrote:
> On Fri, Nov 28, 2014 at 11:52:26AM +, Ian Jackson wrote:
> > Ian Campbell writes ("Re: [PATCH v2] fix migration failure with xl migrate
> > --debug"):
> > > Acked-by: Ian Campbell
> >
> > Thanks for reviewing it :-).
> >
> >
On Fri, Nov 28, 2014 at 11:52:26AM +, Ian Jackson wrote:
> Ian Campbell writes ("Re: [PATCH v2] fix migration failure with xl migrate
> --debug"):
> > Acked-by: Ian Campbell
>
> Thanks for reviewing it :-).
>
> > It's pretty big but a large chunk is pretty mechanical. Were you
> > intending
Ian Campbell writes ("Re: [PATCH v2] fix migration failure with xl migrate
--debug"):
> Acked-by: Ian Campbell
Thanks for reviewing it :-).
> It's pretty big but a large chunk is pretty mechanical. Were you
> intending this for 4.5? (Konrad CCd).
I think (based on reading the thread but not th
On Fri, 2014-11-28 at 08:32 +, M A Young wrote:
> On Fri, 28 Nov 2014, Ian Campbell wrote:
>
> > On Fri, 2014-11-28 at 00:28 +, M A Young wrote:
> >> Migrations with xl migrate --debug will fail because debugging information
> >> from the receiving process is written to the stdout channel.
On Fri, 28 Nov 2014, Ian Campbell wrote:
On Fri, 2014-11-28 at 00:28 +, M A Young wrote:
Migrations with xl migrate --debug will fail because debugging information
from the receiving process is written to the stdout channel. This channel
is also used for status messages so the migration wil
On Fri, 2014-11-28 at 00:28 +, M A Young wrote:
> Migrations with xl migrate --debug will fail because debugging information
> from the receiving process is written to the stdout channel. This channel
> is also used for status messages so the migration will fail as the sending
> process rece
Migrations with xl migrate --debug will fail because debugging information
from the receiving process is written to the stdout channel. This channel
is also used for status messages so the migration will fail as the sending
process receives an unexpected message. This patch moves the debugging