From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NZljK-0000Xx-Us for qemu-devel@nongnu.org; Tue, 26 Jan 2010 08:45:19 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NZljD-0000QC-I1 for qemu-devel@nongnu.org; Tue, 26 Jan 2010 08:45:16 -0500 Received: from [199.232.76.173] (port=36223 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NZljD-0000PU-DF for qemu-devel@nongnu.org; Tue, 26 Jan 2010 08:45:11 -0500 Received: from mx1.redhat.com ([209.132.183.28]:55531) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NZljC-0003k7-MM for qemu-devel@nongnu.org; Tue, 26 Jan 2010 08:45:10 -0500 Message-ID: <4B5EF1E2.5080900@redhat.com> Date: Tue, 26 Jan 2010 15:45:06 +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> <20100126133325.GI5366@redhat.com> In-Reply-To: <20100126133325.GI5366@redhat.com> 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: "Daniel P. Berrange" Cc: Chris Wright , qemu-devel@nongnu.org, Alexander Graf , kvm@vger.kernel.org On 01/26/2010 03:33 PM, Daniel P. Berrange wrote: > >> Me too, especially as the whole stack is involved, and qemu is the >> topmost part from our perspective (no doubt libvirt will want to >> integrate that functionality as well). >> > FYI, libvirt already exposes this kind of functionality. The API call > virConnectGetCapabilities() / command line "virsh capabilities" command > tells you about what the virtualization host is able to support. It can > tell you what architectures are supported, by which binaries. What > machine types are available. Whether KVM or KQEMU acceleration are > present. What CPU model / flags are on the host. What NUMA topology is > available. etc etc > > Great. Note that for a cpu flag to be usable in a guest, it needs to be supported by both kvm.ko and qemu, so reporting /proc/cpuinfo is insufficient. There are also synthetic cpu flags (kvm paravirt features, x2apic) that aren't present in /proc/cpuinfo. -- error compiling committee.c: too many arguments to function