From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [Qemu-devel] [PATCH 28/35] kvm: x86: Introduce kvmclock device to save/restore its state Date: Thu, 20 Jan 2011 13:39:12 -0600 Message-ID: <4D388F60.5070001@linux.vnet.ibm.com> References: <4D35B6DD.1020005@linux.vnet.ibm.com> <4D35B963.7000605@siemens.com> <4D35BA22.7060602@linux.vnet.ibm.com> <4D35BD30.1060900@siemens.com> <4D35C1CE.10509@linux.vnet.ibm.com> <4D35C648.7050809@siemens.com> <4D35C92D.7030000@linux.vnet.ibm.com> <4D36B362.70202@redhat.com> <4D371732.5040901@linux.vnet.ibm.com> <20110119171918.GI5113@redhat.com> <4D3722BB.5030407@linux.vnet.ibm.com> <4D37F5D5.3040409@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "Daniel P. Berrange" , Markus Armbruster , "kvm@vger.kernel.org" , Jan Kiszka , Glauber Costa , Marcelo Tosatti , "qemu-devel@nongnu.org" , Avi Kivity To: Gerd Hoffmann Return-path: Received: from e36.co.us.ibm.com ([32.97.110.154]:47855 "EHLO e36.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752082Ab1ATTjO (ORCPT ); Thu, 20 Jan 2011 14:39:14 -0500 Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by e36.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p0KJYJQS009914 for ; Thu, 20 Jan 2011 12:34:19 -0700 Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id p0KJdDa9171970 for ; Thu, 20 Jan 2011 12:39:13 -0700 Received: from d03av06.boulder.ibm.com (loopback [127.0.0.1]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p0KJhh7R028381 for ; Thu, 20 Jan 2011 12:43:43 -0700 In-Reply-To: <4D37F5D5.3040409@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 01/20/2011 02:44 AM, Gerd Hoffmann wrote: > Hi, > >> For (2), you cannot use bus=X,addr=Y because it makes assumptions about >> the PCI topology which may change in newer -M pc's. > > Why should the PCI topology for 'pc' ever change? > > We'll probably get q35 support some day, but when this lands I expect > we'll see a new machine type 'q35', so '-m q35' will pick the ich9 > chipset (which will have a different pci topology of course) and '-m > pc' will pick the existing piix chipset (which will continue to look > like it looks today). But then what's the default machine type? When I say -M pc, I really mean the default machine. At some point, "qemu-system-x86_64 -device virtio-net-pci,addr=2.0" Is not going to be a reliable way to invoke qemu because there's no way we can guarantee that slot 2 isn't occupied by a chipset device or some other default device. Regards, Anthony Liguori > cheers, > Gerd