On Thu, May 15, 2008 at 08:55:25PM +0200, Gerd Hoffmann wrote: > Daniel P. Berrange wrote: > >> is required for any serious development work. I *hate* to having to > >> create a wrapper script each time I need to pass in additional > >> parameters, and I'd *love* to see libvirt being a bit more developer > >> friendly. > > > > Historically we've not had very complete coverage of QEMU args, but we've > > been adding alot of new functionality recently so the need for extra args > > is reducing all the time. We recently added serial, parallel, sound and > > drive support. USB is the next on the list at which point we basically > > have coverage of all the important options we should reasonably expect. > > Maybe for normal users. Certainly not for developers. I need stuff > like raising debug level for more verbose logs, enable experimental > features while working on them and similar stuff. Nothing which I'd > expect libvirt to support directly. > > > Creating wrapper scripts for experimentation is not that difficult. > > But it is quite inconvenient. > > And it also proves that you can't prevent users from passing additional > args to qemu, thereby creating unsupported configurations. So what was > the point in refusing <emulator args="-foo">...</emulator> support? There is a vast difference between having to go *outside* the API to add extra args, vs supporting it directly in the XML format. Dan. -- |: Red Hat, Engineering, Boston -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