From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53441) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d3PEQ-0001X2-GU for qemu-devel@nongnu.org; Wed, 26 Apr 2017 11:51:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d3PEP-00082y-OW for qemu-devel@nongnu.org; Wed, 26 Apr 2017 11:51:54 -0400 Received: from mail-oi0-x229.google.com ([2607:f8b0:4003:c06::229]:33966) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d3PEP-00082g-J7 for qemu-devel@nongnu.org; Wed, 26 Apr 2017 11:51:53 -0400 Received: by mail-oi0-x229.google.com with SMTP id x184so5871762oia.1 for ; Wed, 26 Apr 2017 08:51:53 -0700 (PDT) MIME-Version: 1.0 From: Pradeep Kiruvale Date: Wed, 26 Apr 2017 17:51:52 +0200 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: [Qemu-devel] VM-Migration List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "qemu-devel@nongnu.org Developers" Hi All, Is it possible to enable/disable to migration features on the fly for a qemu VM? I mean through qmp interface kind of a interface? I am asking this because keeping the dirty memory list, this could consume some compute and memory. So, the plan is to enable when the VM needs to be migrated. Please clarify. Regards, Pradeep