From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KdoxT-0003TJ-3f for qemu-devel@nongnu.org; Thu, 11 Sep 2008 12:23:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KdoxQ-0003R8-Gw for qemu-devel@nongnu.org; Thu, 11 Sep 2008 12:23:50 -0400 Received: from [199.232.76.173] (port=57816 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KdoxQ-0003R0-8L for qemu-devel@nongnu.org; Thu, 11 Sep 2008 12:23:48 -0400 Received: from an-out-0708.google.com ([209.85.132.241]:52525) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KdoxQ-00030k-0b for qemu-devel@nongnu.org; Thu, 11 Sep 2008 12:23:48 -0400 Received: by an-out-0708.google.com with SMTP id d18so47190and.130 for ; Thu, 11 Sep 2008 09:23:45 -0700 (PDT) Message-ID: <48C945DD.4020304@codemonkey.ws> Date: Thu, 11 Sep 2008 11:22:53 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 0/10] Live migration for QEMU References: <1220989802-13706-1-git-send-email-aliguori@us.ibm.com> <200809111213.m8BCDHaC012607@fjmscan502.ms.jp.fujitsu.com> <48C917F3.7040507@codemonkey.ws> <20080911133046.GE16427@shareable.org> <48C92742.8000002@us.ibm.com> <48C939F6.1070006@qumranet.com> In-Reply-To: <48C939F6.1070006@qumranet.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Chris Wright , Uri Lublin , qemu-devel@nongnu.org, kvm@vger.kernel.org Avi Kivity wrote: > Anthony Liguori wrote: >> >> Yes. The primary reason that hasn't been possible in the past was >> because of how memory was migrated. The new memory migration >> protocol happens to make it easier to let QEMU and KVM be >> compatible. That wasn't an accident :-) >> > > Well, it's still broken IMO (migration ram_addr_t rather than physical > addresses). Have you thought of a solution other than make "mem" only save physical memory and have everything else save their own memory? That gets really funky because then everything needs live save/restore tracking. It's quite messy. Regards, Anthony Liguori