On Thu, Jun 11, 2009 at 03:53:15PM +0200, Daniel Veillard wrote: > On Wed, Jun 10, 2009 at 09:02:40PM +0100, Mark McLoughlin wrote: > > The KVM version string can be one of the following: > > > > - qemu-kvm-x.y.z in stable releases > > - kvm-XX for kvm versions up to kvm-85 > > - qemu-kvm-devel-XX for kvm version kvm-86 and later > > Any chance to secure an API in the future from those guys ? > > But anyway we need to deal with the mess so ... In 95% of cases we can ignore the version numbers. We aim to detect new command line features from the help output. And for monitor commands we just try them and catch failure. We just needed this version number for a couple of hacks not covered by those two approaches 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 :| -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list