From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NZmfA-0004Ka-26 for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:45:04 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NZmf5-0004HW-EW for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:45:03 -0500 Received: from [199.232.76.173] (port=42561 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NZmf5-0004HK-1c for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:44:59 -0500 Received: from mx1.redhat.com ([209.132.183.28]:34720) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NZmf4-0003RA-FF for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:44:58 -0500 Message-ID: <4B5EFFE6.9060102@redhat.com> Date: Tue, 26 Jan 2010 16:44:54 +0200 From: Avi Kivity MIME-Version: 1.0 References: <20100126064902.GD25779@x200.localdomain> <03EA8701-C607-4B87-A6C6-1DCD3E5DCAAC@suse.de> <4B5EE9EF.6030904@codemonkey.ws> <197BDDDF-D808-4157-8270-42B72B99BE0D@suse.de> <4B5EED22.4080009@redhat.com> <4B5EF874.3080306@codemonkey.ws> <4B5EF903.1070508@redhat.com> <4B5EFAB6.4080102@codemonkey.ws> <4B5EFB7A.7010709@redhat.com> <4B5EFD18.1030008@codemonkey.ws> <4B5EFE13.1070300@redhat.com> <4B5EFF56.8080207@codemonkey.ws> In-Reply-To: <4B5EFF56.8080207@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: KVM call agenda for Jan 26 List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Chris Wright , Alexander Graf , kvm@vger.kernel.org, qemu-devel@nongnu.org On 01/26/2010 04:42 PM, Anthony Liguori wrote: > On 01/26/2010 08:37 AM, Avi Kivity wrote: >> People who use discovery tools are probably setting up a migration >> cluster. They aren't going to use -cpu host. > > BTW, it might be neat to introduce a qemu command line that runs a > monitor command and exits without creating a VM. We could then > introduce a info cpucap command that dumped all of the supported CPU > features. > > Someone setting up a migration cluster would then run qemu -monitor > command="info cpucap", collect the results, compute an intersection, > and then use that to generate a -cpu flag. In fact, providing a tool > that parsed a bunch of those outputs and generated a -cpu flag would > be a pretty nice addition. Definitely. And query about supported machine models virtio NIC features, etc. -- error compiling committee.c: too many arguments to function