From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:43313) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ToxrV-0006WH-5E for qemu-devel@nongnu.org; Sat, 29 Dec 2012 09:58:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ToxrT-0005CG-Vz for qemu-devel@nongnu.org; Sat, 29 Dec 2012 09:58:09 -0500 Received: from mail-wg0-f50.google.com ([74.125.82.50]:48190) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ToxrT-0005CC-PU for qemu-devel@nongnu.org; Sat, 29 Dec 2012 09:58:07 -0500 Received: by mail-wg0-f50.google.com with SMTP id es5so5092416wgb.17 for ; Sat, 29 Dec 2012 06:58:07 -0800 (PST) Sender: Paolo Bonzini Message-ID: <50DF04FA.6010404@redhat.com> Date: Sat, 29 Dec 2012 15:58:02 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <50DCC3AF.7020802@profihost.ag> <50DDDCB2.1060403@redhat.com> <50DDED1C.2020208@profihost.ag> <50DEF785.7030706@redhat.com> <50DEF89F.2090203@profihost.ag> In-Reply-To: <50DEF89F.2090203@profihost.ag> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] setting migrate_downtime results in halted vm (qemu 1.3) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Priebe Cc: qemu-devel , Alexandre DERUMIER , Juan Quintela Il 29/12/2012 15:05, Stefan Priebe ha scritto: > Hi Paolo, > Am 29.12.2012 15:00, schrieb Paolo Bonzini: >>> i cherry picked that one on top of 1.3 sadly it does not help. VM halts, >>> monitor socket is no longer available kvm process is running with 100% >>> CPU on source side. >> >> Can you please test master and, if it works, bisect it in reverse? >> (That is, mark "bad" if it works, "good" if it fails). > > It's working fine with qemu master. > > I walked then through the bug patchset here: > http://www.mail-archive.com/qemu-commits@nongnu.org/msg02028.html > > and backported them step by step to qemu 1.3. > > 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. Paolo