From: Mark McLoughlin <markmc@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Chris Lalancette <clalance@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH]: Always use KVM_VERSION to build version number
Date: Mon, 10 Aug 2009 10:52:12 +0100 [thread overview]
Message-ID: <1249897932.8784.71.camel@blaa> (raw)
In-Reply-To: <4A7FEC7F.9070304@redhat.com>
On Mon, 2009-08-10 at 12:46 +0300, Avi Kivity wrote:
> On 08/10/2009 12:19 PM, Mark McLoughlin wrote:
> >
> > Or we could drop this kvm snapshot numbering system and just use qemu
> > VERSION numbering - i.e. qemu-kvm-devel-88 could have been published as
> > qemu-kvm-0.10.50
> >
>
> Yeah. You still couldn't distinguish among different snapshots.
0.10.51, 0.10.52 etc.
> >> How about adding 'qemu -describe-features' which will output, one line
> >> per feature, what's supported (and limits where applicable)? I
> >> understand libvirt already does this for some features using -help; this
> >> is simply a formalization of that hack.
> >>
> >
> > Yes, libvirt would much rather not parse -help or use version numbers to
> > detect whether features are available.
> >
> > We should revisit the "info capabilities" thing again:
> >
> > http://lists.gnu.org/archive/html/qemu-devel/2008-11/msg00767.html
> >
>
> Logically it needs to work before starting a VM, so a command line
> option is more appropriate.
http://lists.gnu.org/archive/html/qemu-devel/2008-11/msg00899.html
Cheers,
Mark.
next prev parent reply other threads:[~2009-08-10 9:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 12:31 [PATCH]: Always use KVM_VERSION to build version number Chris Lalancette
2009-08-09 9:58 ` Avi Kivity
2009-08-10 9:19 ` Mark McLoughlin
2009-08-10 9:39 ` [PATCH] configure: make default KVM_VERSION qemu-kvm-devel Mark McLoughlin
2009-08-10 9:47 ` Avi Kivity
2009-08-10 9:46 ` [PATCH]: Always use KVM_VERSION to build version number Avi Kivity
2009-08-10 9:52 ` Mark McLoughlin [this message]
2009-08-10 10:12 ` Avi Kivity
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=1249897932.8784.71.camel@blaa \
--to=markmc@redhat.com \
--cc=avi@redhat.com \
--cc=clalance@redhat.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.