From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM call agenda for Jan 26 Date: Tue, 26 Jan 2010 15:45:06 +0200 Message-ID: <4B5EF1E2.5080900@redhat.com> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Graf , Anthony Liguori , Chris Wright , kvm@vger.kernel.org, qemu-devel@nongnu.org To: "Daniel P. Berrange" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:45961 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753660Ab0AZNpM (ORCPT ); Tue, 26 Jan 2010 08:45:12 -0500 In-Reply-To: <20100126133325.GI5366@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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