From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38583) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WDEjJ-0006CZ-S2 for qemu-devel@nongnu.org; Tue, 11 Feb 2014 09:54:39 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WDEjD-0007cJ-0K for qemu-devel@nongnu.org; Tue, 11 Feb 2014 09:54:33 -0500 Received: from mail-ph.de-nserver.de ([85.158.179.214]:37552) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WDEjC-0007c8-MK for qemu-devel@nongnu.org; Tue, 11 Feb 2014 09:54:26 -0500 Message-ID: <52FA399F.6070802@profihost.ag> Date: Tue, 11 Feb 2014 15:54:23 +0100 From: Stefan Priebe - Profihost AG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] memory allocation of migration changed? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel Hello, in the past (Qemu 1.5) a migration failed if there was not enogh memory on the target host available directly at the beginning. Now with Qemu 1.7 i've seen succeeded migrations but the kernel OOM memory killer killing qemu processes. So the migration seems to takes place without having anough memory on the target machine? Could this be? Greets, Stefan