From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM version reporting? Date: Fri, 10 Aug 2007 19:53:58 +0300 Message-ID: <46BC9826.6020809@qumranet.com> References: <20070810162822.GA10440@jim.sh> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Jim Paris Return-path: In-Reply-To: <20070810162822.GA10440-lSbMZ+N7itA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Jim Paris wrote: > Hi, > > Could qemu/VERSION get updated with each KVM release? Currently it > seems there is no way to determine the KVM version from the binaries. > > Putting it in MODULE_VERSION for the kernel modules would also be > useful. > > There will be a version string for the external modules starting with kvm-34. I'll look into adding same for qemu. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/