From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60929) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WirnL-0002Dc-Lq for qemu-devel@nongnu.org; Fri, 09 May 2014 16:53:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WirnD-000218-Bh for qemu-devel@nongnu.org; Fri, 09 May 2014 16:53:27 -0400 Received: from mail-ph.de-nserver.de ([85.158.179.214]:55729) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WirnD-00020w-0y for qemu-devel@nongnu.org; Fri, 09 May 2014 16:53:19 -0400 Message-ID: <536D403E.1020100@profihost.ag> Date: Fri, 09 May 2014 22:53:18 +0200 From: Stefan Priebe MIME-Version: 1.0 References: <536CD48B.2020907@profihost.ag> <536D0ACB.50206@redhat.com> In-Reply-To: <536D0ACB.50206@redhat.com> 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , qemu-stable@nongnu.org, qemu-devel ) Am 09.05.2014 19:05, schrieb Paolo Bonzini: > 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? Sadly no. But far more complex than i thought. I'm seeing this problem only on machines originally started under qemu 1.5 ten migrated to qemu 1.7 with machine type=pc440fc-1.5 . Only those do not work. But they also do not work migrating them to qemu 1.7.1. So let's ignore the whole fact and thanks for your bisect ideas. I will just shut them down all and start them with a fresh qemu 2.0. > 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