From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Jim Paris <jim-XrPbb/hENzg@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: KVM version reporting?
Date: Fri, 10 Aug 2007 19:53:58 +0300 [thread overview]
Message-ID: <46BC9826.6020809@qumranet.com> (raw)
In-Reply-To: <20070810162822.GA10440-lSbMZ+N7itA@public.gmane.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/
prev parent reply other threads:[~2007-08-10 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 16:28 KVM version reporting? Jim Paris
[not found] ` <20070810162822.GA10440-lSbMZ+N7itA@public.gmane.org>
2007-08-10 16:53 ` Avi Kivity [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46BC9826.6020809@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=jim-XrPbb/hENzg@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox