From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NSrok-0006sP-C7 for qemu-devel@nongnu.org; Thu, 07 Jan 2010 07:50:22 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NSrof-0006o2-HN for qemu-devel@nongnu.org; Thu, 07 Jan 2010 07:50:21 -0500 Received: from [199.232.76.173] (port=43627 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NSrof-0006nl-9P for qemu-devel@nongnu.org; Thu, 07 Jan 2010 07:50:17 -0500 Received: from mx1.redhat.com ([209.132.183.28]:63354) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NSroe-0004lt-Op for qemu-devel@nongnu.org; Thu, 07 Jan 2010 07:50:17 -0500 Message-ID: <4B45D882.2090809@redhat.com> Date: Thu, 07 Jan 2010 14:50:10 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] cpuid problem in upstream qemu with kvm References: <4B4598BC.4000206@redhat.com> <4B45A536.1070300@redhat.com> <4B45A851.5000401@redhat.com> <4B45AC18.8040003@redhat.com> <4B45C7EB.1010501@codemonkey.ws> <4B45C90C.1000507@redhat.com> <4B45CCCE.1010208@redhat.com> <4B45D170.7050000@redhat.com> <4B45D497.40200@codemonkey.ws> <4B45D642.3070009@redhat.com> <20100107124738.GB9028@redhat.com> In-Reply-To: <20100107124738.GB9028@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: kvm-devel , Gleb Natapov , "Michael S. Tsirkin" , John Cooper , dlaor@redhat.com, Alexander Graf , qemu-devel@nongnu.org On 01/07/2010 02:47 PM, Daniel P. Berrange wrote: > > With the introduction of the new -device spport, there's no need to > replay hotplug events in order any more. Instead just use static > PCI addresses when starting the guest, and the same addresses after > migration. You could argue that QEMU should preserve the addressing > automatically during migration, but apps need to do it manually > already to keep addreses stable across power-offs, so doing it manually > across migration too is no extra burden. > > That's true - shutdown and startup are an equivalent problem to live migration from that point of view. -- error compiling committee.c: too many arguments to function