From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LaYpq-0004EJ-TH for qemu-devel@nongnu.org; Fri, 20 Feb 2009 12:06:47 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LaYpq-0004Dl-9E for qemu-devel@nongnu.org; Fri, 20 Feb 2009 12:06:46 -0500 Received: from [199.232.76.173] (port=55673 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LaYpq-0004DY-3C for qemu-devel@nongnu.org; Fri, 20 Feb 2009 12:06:46 -0500 Received: from main.gmane.org ([80.91.229.2]:51853 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LaYpp-0001tl-NG for qemu-devel@nongnu.org; Fri, 20 Feb 2009 12:06:45 -0500 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LaYpl-0000uu-2N for qemu-devel@nongnu.org; Fri, 20 Feb 2009 17:06:41 +0000 Received: from rrcs-71-41-149-67.sw.biz.rr.com ([71.41.149.67]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 20 Feb 2009 17:06:41 +0000 Received: from Charles_Duffy by rrcs-71-41-149-67.sw.biz.rr.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 20 Feb 2009 17:06:41 +0000 From: Charles Duffy Date: Fri, 20 Feb 2009 11:06:31 -0600 Message-ID: References: <499EBFD8.50307@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit In-Reply-To: <499EBFD8.50307@amd.com> Sender: news Subject: [Qemu-devel] Re: [RFC] More robust migration Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Andre Przywara wrote: > 1. Transfer configuration data. Currently there is no VM configuration > data transferred with the stream. One has to start QEMU/KVM with the > _exact_ same parameters on the other side to allow migration. If there > would be a pseudo-device (transferred first) holding these parameters > (and other runtime dependent stuff like kvm_enabled()) this would ease > migration a lot. I presently have code which *relies* on the ability to migrate from one VM to a target with different different backing stores for their disk images (albeit sharing the same contents). If this ability were to be removed, that would be unfortunate.