From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:35791)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1WioF3-0002Mo-Vm
	for qemu-devel@nongnu.org; Fri, 09 May 2014 13:05:58 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1WioEu-0006yb-Uc
	for qemu-devel@nongnu.org; Fri, 09 May 2014 13:05:49 -0400
Sender: Paolo Bonzini <paolo.bonzini@gmail.com>
Message-ID: <536D0ACB.50206@redhat.com>
Date: Fri, 09 May 2014 19:05:15 +0200
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <536CD48B.2020907@profihost.ag>
In-Reply-To: <536CD48B.2020907@profihost.ag>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] Migration from older Qemu to Qemu 2.0.0 does not
	work
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>, qemu-stable@nongnu.org, qemu-devel <qemu-devel@nongnu.org>

Il 09/05/2014 15:13, Stefan Priebe - Profihost AG ha scritto:
>
> I see no output at the monitor of Qemu 2.0.
>
> # migrate -d tcp:a.b.c.d:6000
>
> # info migrate
> capabilities: xbzrle: off x-rdma-pin-all: off auto-converge: on
> zero-blocks: off
> Migration status: failed
> total time: 0 milliseconds
>
> The target machine is still running at this point with no output.

Anything on its stdout?

Another test you could do, in addition to changing the devices, is this:

1) try with commit 6141f3bd6904df7cf9519c6444a14a608b9874c4 on the 
destination (the next one caused a migration problem that was fixed 
later).  If it passes, go to step 1a.  If it fails, go to step 2.

1a) try with commit c01a71c1a56fa27f43449ff59e5d03b2483658a2.  If it 
passes, go to step 1b.  If it fails, report it here.

1b) bisect between v2.0.0 (known-bad) and 
c01a71c1a56fa27f43449ff59e5d03b2483658a2 (known-good) to find the 
culprit.  Report results.

2) change the source to v1.7.0 and bisect between v1.7.0 and 
6141f3bd6904df7cf9519c6444a14a608b9874c4.  Report results.

Thanks!

Paolo