From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:57481) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ToLPr-0000Pn-3f for qemu-devel@nongnu.org; Thu, 27 Dec 2012 16:55:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ToLPq-0006F8-00 for qemu-devel@nongnu.org; Thu, 27 Dec 2012 16:55:03 -0500 Received: from mail.profihost.ag ([85.158.179.208]:48893) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ToLPp-0006Bv-L7 for qemu-devel@nongnu.org; Thu, 27 Dec 2012 16:55:01 -0500 Message-ID: <50DCC3AF.7020802@profihost.ag> Date: Thu, 27 Dec 2012 22:54:55 +0100 From: Stefan Priebe MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] setting migrate_downtime results in halted vm List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel Hello list, i'm using qemu 1.3 and migration works fine if i do not set migrate_downtime. If i set migrate_downtime to 1s or 0.5s or 0.3s the VM halts immediatly i cannot even connect to the qmp socket anymore and migration takes 5-10 minutes or never finishes. I see high cpu usage on source vm while it hangs. VM was for all tests IDLE and was using 1GB of 4GB mem. Do you have any ideas what happens here? Greets, Stefan