Re: [Qemu-devel] Re: libvirt vs. in-qemu management

[Jamie Lokier]

Alexander Graf wrote:
> > One way to avoid it is to have a rich plugin API so if some needs some
> > to, say, set up traffic control on the interface, they can write a
> > plugin to do that.
> 
> Another way would be to have an active open source community that just
> writes the support for traffic control upstream if they need it. I
> actually prefer that to a plugin API.

Not every local config quirk should go upstream, and if someone has
to edit the C source just to configure their tap interface a bit
differently, that's not a good sign.

Qemu already has a passable API for this in the form of thw network-up
and network-down scripts.  Imho much more ability to hook into many
parts of device setup that way would be good.  You don't need a rich
internal API then.

Even better if callout scripts are allowed to connect back to QMP and
tell Qemu what to do during machine setup and interesting events.

-- Jamie