From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:39432) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QiMsi-0002ev-SS for qemu-devel@nongnu.org; Sun, 17 Jul 2011 04:39:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QiMsh-0006PJ-E2 for qemu-devel@nongnu.org; Sun, 17 Jul 2011 04:39:20 -0400 Received: from mx1.redhat.com ([209.132.183.28]:4129) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QiMsg-0006PD-Tn for qemu-devel@nongnu.org; Sun, 17 Jul 2011 04:39:19 -0400 Message-ID: <4E229FAE.9000905@redhat.com> Date: Sun, 17 Jul 2011 11:39:10 +0300 From: Avi Kivity MIME-Version: 1.0 References: <1447945249.1317755.1310627692984.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> <4E1EAA72.1060103@redhat.com> <4E1EE183.5050100@codemonkey.ws> <4E1EE1F2.5020801@redhat.com> <4E1F0EC2.1050408@redhat.com> <4E1F1440.4080409@redhat.com> <4E1FF360.8010609@redhat.com> In-Reply-To: <4E1FF360.8010609@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC] New thread for the VM migration List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: kvm@vger.kernel.org, Umesh Deshpande , qemu-devel@nongnu.org, quintela@redhat.com On 07/15/2011 10:59 AM, Paolo Bonzini wrote: > On 07/14/2011 06:07 PM, Avi Kivity wrote: >> >> Maybe we can do this via a magic subsection whose contents are the >> hotplug event. > > What about making the device list just another "thing" that has to be > migrated live, together with block and ram? Excellent idea. Sticky points: - if a new device includes RAM, the device update must precede the migration of the new RAM section - the reverse for unplug - need better decoupling between host and guest state -- error compiling committee.c: too many arguments to function