On Thu, Aug 22, 2013 at 12:06:55PM +0200, Giuseppe Scrivano wrote: > "Daniel P. Berrange" <berrange@xxxxxxxxxx> writes: > > >> 2) as you said, support arch=NULL to get the full list (and now that > >> I've thought more about it, I should change the error to > >> VIR_ERR_NO_SUPPORT when arch==NULL instead of raising an internal > >> error). > > > > I'd strictly forbid arch=NULL in the API and wire protocol > > (ie use remote_nonnull_string arch). > > How do we get the set of supported architectures? I'd like that for > completeness sake we take this into account now, even if there is no > real use (yet?). The capabilities XML shows you all architectures that libvirt knows about. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list