On Wed, Jul 02, 2008 at 10:51:49AM -0700, David Lutterkort wrote: > On Wed, 2008-07-02 at 17:11 +0100, Daniel P. Berrange wrote: > > Yes that kinda sucks. When I added the storage pool/volume APis to > > libvirt I basically re-implemented the file magic checks directly > > rather than parse qemu-info. > > Is there any way to get that upstream into qemu rather than forcing > libvirt to deal with these fairly low-level issues ? The idea of providing a library API gets raise every 6 months or so but no one ever wants to commit to a stable ABI with QEMU internals, so it doesn't go anywhere useful. I don't expect that to change any time soon since QEMU is still evolving quite significantly under the hood. 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 :| _______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/et-mgmt-tools
