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:17:45 +0200 Message-ID: <4B5EEB79.3080802@redhat.com> References: <20100126064902.GD25779@x200.localdomain> <03EA8701-C607-4B87-A6C6-1DCD3E5DCAAC@suse.de> <4B5EE9EF.6030904@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Graf , Chris Wright , kvm@vger.kernel.org, qemu-devel@nongnu.org To: Anthony Liguori Return-path: Received: from mx1.redhat.com ([209.132.183.28]:47461 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752188Ab0AZNRu (ORCPT ); Tue, 26 Jan 2010 08:17:50 -0500 In-Reply-To: <4B5EE9EF.6030904@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: On 01/26/2010 03:11 PM, Anthony Liguori wrote: > On 01/26/2010 03:09 AM, Alexander Graf wrote: >> On 26.01.2010, at 07:49, Chris Wright wrote: >> >>> Please send in any agenda items you are interested in covering. >> KVM Hardware Inquiry Tool > > Avi beat you to it ;-) See vmxcap in the tree. I knew I should have put a disclaimer in there. Maybe I should make the output vary randomly over time? Anyway we really need a "virtualization stack inquiry tool", since capabilities depend on the hardware, kernel, and qemu. -- error compiling committee.c: too many arguments to function