From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:45465)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <s.priebe@profihost.ag>) id 1ToyBu-00014s-La
	for qemu-devel@nongnu.org; Sat, 29 Dec 2012 10:19:16 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <s.priebe@profihost.ag>) id 1ToyBt-0001QR-NK
	for qemu-devel@nongnu.org; Sat, 29 Dec 2012 10:19:14 -0500
Received: from mail.profihost.ag ([85.158.179.208]:49554)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <s.priebe@profihost.ag>) id 1ToyBt-0001QA-DX
	for qemu-devel@nongnu.org; Sat, 29 Dec 2012 10:19:13 -0500
Message-ID: <50DF09E5.7040309@profihost.ag>
Date: Sat, 29 Dec 2012 16:19:01 +0100
From: Stefan Priebe <s.priebe@profihost.ag>
MIME-Version: 1.0
References: <50DCC3AF.7020802@profihost.ag>
	<e1a0e4ea-cc4b-4cc3-81ba-69cab87835a6@mailpro>
	<50DDDCB2.1060403@redhat.com> <50DDED1C.2020208@profihost.ag>
	<50DEF785.7030706@redhat.com> <50DEF89F.2090203@profihost.ag>
	<50DF04FA.6010404@redhat.com>
In-Reply-To: <50DF04FA.6010404@redhat.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] setting migrate_downtime results in halted vm
	(qemu 1.3)
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: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Alexandre DERUMIER <aderumier@odiso.com>, Juan Quintela <quintela@redhat.com>

Am 29.12.2012 15:58, schrieb Paolo Bonzini:
> Il 29/12/2012 15:05, Stefan Priebe ha scritto:
>> It starts working to me after the first 22 patches (after introducing
>> the new mutex and threading for writes).
>
> And when does it break in 1.3?
>
> I suppose it will be between 05e72dc5812a9f461fc2c606dff2572909eafc39
> and aa723c23147e93fef8475bd80fd29e633378c34d.
>
> Probably at 2dddf6f4133975af62e64cb6406ec1239491fa89, which was supposed
> to be placed before switching to the migration thread (or even squashed
> in it) but ended up much earlier when the project moved from me to Juan.

You mean by bisecting between qemu 1.2 and 1.3? I retested qemu 1.2 and 
it wasn't 100% working for me there too. It worked fine until 
migrate_downtime 1s it breaks / vm just halts when i set it to 2s with 
qemu 1.2. So i don't really know where to start bisecting. As i have NO 
version where it worked perfectly. Except Qemu 1.3 with the patches 
backported from 1.4 this works fine.

Greets
Stefan