From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] KVM call minutes April 3 Date: Thu, 05 Apr 2012 19:16:48 +0300 Message-ID: <4F7DC570.6070003@redhat.com> References: <4F7B610D.8000101@redhat.com> <20120404011843.GA2918@illuin> <4F7BFAEB.7070000@redhat.com> <4F7C282E.6090309@redhat.com> <20120404121418.GB2918@illuin> <4F7C4AD6.6030105@redhat.com> <20120404143944.GA2905@illuin> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Igor Mammedov , Paolo Bonzini , Dor Laor , qemu-devel@nongnu.org, KVM devel mailing list , Markus Armbruster To: Michael Roth Return-path: Received: from mx1.redhat.com ([209.132.183.28]:56912 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755023Ab2DEQQz (ORCPT ); Thu, 5 Apr 2012 12:16:55 -0400 In-Reply-To: <20120404143944.GA2905@illuin> Sender: kvm-owner@vger.kernel.org List-ID: On 04/04/2012 05:39 PM, Michael Roth wrote: > > Will command line take in account hot-plugged devices? > > No, that's a good point. We'd probably need to generate the options > required to ensure the devices are created on the target, and we'd only > be able to do that just before sending the device state. That means we > need a way to create machines after we've completed tasks like memory > migration, which probably has similar requirements to just being able to > instantiate a machine from a serialized QOM composition tree. > Or we forward the hotplug events over the migration protocol. This is needed for devices that include memory (like ivshmem.c) -- error compiling committee.c: too many arguments to function