From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC] New thread for the VM migration Date: Sun, 17 Jul 2011 11:39:10 +0300 Message-ID: <4E229FAE.9000905@redhat.com> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: quintela@redhat.com, Anthony Liguori , Umesh Deshpande , qemu-devel@nongnu.org, kvm@vger.kernel.org To: Paolo Bonzini Return-path: Received: from mx1.redhat.com ([209.132.183.28]:35083 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752161Ab1GQIjT (ORCPT ); Sun, 17 Jul 2011 04:39:19 -0400 In-Reply-To: <4E1FF360.8010609@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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