From: Chris Lalancette <clalance@redhat.com>
To: Anthony Liguori <aliguori@linux.vnet.ibm.com>
Cc: Jes.Sorensen@redhat.com, qemu-devel@nongnu.org, crobinso@redhat.com
Subject: Re: [Qemu-devel] Re: [PATCH 1/1] Add -version-simple argument, printing only version number.
Date: Fri, 14 May 2010 09:58:48 -0400 [thread overview]
Message-ID: <4BED5718.3060505@redhat.com> (raw)
In-Reply-To: <4BED4E73.2080802@linux.vnet.ibm.com>
On 05/14/2010 09:21 AM, Anthony Liguori wrote:
> On 05/13/2010 03:32 AM, Jes.Sorensen@redhat.com wrote:
>> From: Jes Sorensen<Jes.Sorensen@redhat.com>
>>
>> Add -version-simple argument for QEMU, printing just the version
>> number, without any supporting text.
>>
>
> I'm not a huge fan of the name.
>
> But what information are we trying to convey? Just major/minor number
> or would qemu-kvm also throw some info in there?
>
> Do version numbers even matter because 0.13 from qemu.git is going to be
> a hell of a lot different from 0.13 in RHEL6.x.
>
> What are the consumers of this information actually doing with it?
At the moment libvirt uses it mostly to determine what features are
present in a particular version of Qemu that is on the machine. So
for instrance, for 0.13 we turn on the JSON flag so we know to use
the QMP monitor instead of the text monitor. There are many other
examples as well.
Now, I agree that this isn't the best way to do it; much better would
be a way for libvirt to query the capabilities of Qemu directly and
not rely on versions (not the least because of the problem you point
out above). But up until now we haven't had a better way to do it.
--
Chris Lalancette
next prev parent reply other threads:[~2010-05-14 14:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 8:32 [Qemu-devel] [PATCH] Add -version-simple argument to QEMU Jes.Sorensen
2010-05-13 8:32 ` [Qemu-devel] [PATCH 1/1] Add -version-simple argument, printing only version number Jes.Sorensen
2010-05-13 13:33 ` Daniel P. Berrange
2010-05-13 13:41 ` Jes Sorensen
2010-05-13 19:30 ` Blue Swirl
2010-05-14 9:42 ` Markus Armbruster
2010-05-14 10:06 ` Daniel P. Berrange
2010-05-14 11:24 ` Markus Armbruster
2010-05-14 13:34 ` Daniel P. Berrange
2010-05-14 13:48 ` Anthony Liguori
2010-05-14 13:57 ` Daniel P. Berrange
2010-05-14 13:27 ` Anthony Liguori
2010-05-14 13:32 ` Daniel P. Berrange
2010-05-14 14:25 ` Markus Armbruster
2010-05-14 13:21 ` [Qemu-devel] " Anthony Liguori
2010-05-14 13:58 ` Chris Lalancette [this message]
2010-05-14 14:06 ` Daniel P. Berrange
2010-05-17 6:54 ` Jes Sorensen
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=4BED5718.3060505@redhat.com \
--to=clalance@redhat.com \
--cc=Jes.Sorensen@redhat.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=crobinso@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).