From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@gmail.com>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
"Bjørn Mork" <bjorn@mork.no>,
kvm@vger.kernel.org
Subject: Re: [PATCH] Add KVM version to monitor "info version"
Date: Wed, 26 Nov 2008 13:23:44 +0200 [thread overview]
Message-ID: <492D31C0.9070101@redhat.com> (raw)
In-Reply-To: <5d6222a80811260318i38e1a8c9n40d8336734347371@mail.gmail.com>
Glauber Costa wrote:
> On Wed, Nov 26, 2008 at 8:55 AM, Daniel P. Berrange <berrange@redhat.com> wrote:
>
>> On Wed, Nov 26, 2008 at 11:22:03AM +0100, Bj?rn Mork wrote:
>>
>>> Trying to track the current KVM head as closely as possible, I often
>>> find myself wondering which KVM version a particular guest instance is
>>> running. The attached patch adds this information to the monitor
>>> command "info version":
>>>
>>> (qemu) info version
>>> 0.9.1 (kvm-79)
>>>
>> I'd really rather we didn't touch the 'info version' command since it
>> means we have different syntax from upstream QEMU. If we want KVM
>> version info exposed, then I'd suggest 'info kvmversion' or some other
>> new command.
>>
>
> I believe it fits nicely into info kvm. Instead of enabled/disabled,
> we could answer
> disabled or kvm-whatever
>
>
(qemu) info kvm
enabled (kvm-123)
or
(qemu) info kvm
enabled
version kvm-123
May be easier to parse, and more backwards compatible.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-11-26 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 10:22 [PATCH] Add KVM version to monitor "info version" Bjørn Mork
2008-11-26 10:55 ` Daniel P. Berrange
2008-11-26 11:18 ` Glauber Costa
2008-11-26 11:23 ` Avi Kivity [this message]
2008-12-08 13:37 ` Bjørn Mork
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=492D31C0.9070101@redhat.com \
--to=avi@redhat.com \
--cc=berrange@redhat.com \
--cc=bjorn@mork.no \
--cc=glommer@gmail.com \
--cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.