From: "Daniel P. Berrange" <berrange@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: libvir-list@redhat.com,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
kvm-devel <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: Changing the QEMU svn VERSION string
Date: Tue, 7 Apr 2009 10:04:05 +0100 [thread overview]
Message-ID: <20090407090405.GB8651@redhat.com> (raw)
In-Reply-To: <49DABC83.7010608@codemonkey.ws>
On Mon, Apr 06, 2009 at 09:37:55PM -0500, Anthony Liguori wrote:
> Hi,
>
> I'd like to update the VERSION string in QEMU's svn tree. Right now,
> it's 0.10.0 and since we have a 0.10.2 release, that's somewhat confusing.
>
> I don't want to make it 0.11.0 either because that's not going to be
> reliable from a feature detection perspective. What I would like is to
> make it 0.11.0-devel or something similar to that.
>
> Being the nice guy I am, I thought I would check that this didn't make
> libvirt go bonkers :-) This is the relevant detection code in libvirt:
>
>
> if (sscanf(help, "QEMU PC emulator version %u.%u.%u (kvm-%u)",
> &major, &minor, µ, &kvm_version) != 4)
> kvm_version = 0;
>
> if (!kvm_version && sscanf(help, "QEMU PC emulator version u.%u.%u",
> &major, &minor, µ) != 3)
> goto cleanup2;
>
> If I change SVN to 0.11.0-devel, that's going to break the KVM string
> although the QEMU string will continue to work. Avi could potentially
> carry a patch to keep it 0.10.x and since kvm-%u will be used to
> identify features, that should keep things working.
The only things we use the KVM version for are to decide whether migration
and vnet_hdr flag for tun devices is supported. These checks are already
outdated since 0.10.0 QEMU now has support for migration, and thus needs
updating. So if you choose to go with '0.11.0-devel' it won't cause any
huge problems for us, and I'll change this code to make it more forgiving
of version number string changes in future.
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2009-04-07 9:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 2:37 [Qemu-devel] Changing the QEMU svn VERSION string Anthony Liguori
2009-04-07 8:10 ` Gerd Hoffmann
[not found] ` <20090407090322.GC31447@redhat.com>
2009-04-07 13:52 ` [libvirt] " Anthony Liguori
2009-04-07 17:13 ` Jamie Lokier
2009-04-08 6:35 ` Gerd Hoffmann
2009-04-07 17:58 ` Daniel Jacobowitz
2009-04-07 22:36 ` Paul Brook
2009-04-08 13:13 ` Anthony Liguori
2009-04-08 13:56 ` Jamie Lokier
2009-04-07 9:04 ` Daniel P. Berrange [this message]
2009-04-07 16:09 ` Andreas Färber
2009-04-07 16:29 ` M. Warner Losh
2009-04-08 21:10 ` Andreas Färber
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=20090407090405.GB8651@redhat.com \
--to=berrange@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=libvir-list@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).