* Laine Stump (la...@laine.org) wrote: > 2) Another possibility would be to define a new sub-element of<interface>, > called "<driver>", similar > to what's done in the storage device XML. In the future, other backend > driver-related items could be placed there: > > <devices> > <interface type='network'> > <source network='default'/> > <model type='virtio'/> > <driver vhost='default|require|disable'/> (or > "mode='default|kernel|user'") > </interface> > </devices> > > 3) A third method, which might make the XML file look less ugly if, in the > future, there were *many* > more configurable items for interface backends (this one was inspired by > the<memtune> element): > > <devices> > <interface type='network'> > <source network='default'/> > <model type='virtio'/> > <driver> > <vhost>default|require|disable</vhost> > </driver> > </interface> > </devices>
Either of these seems useful, perhaps the name <parameters>. There's already other tunable parameters that could conceivably be exposed here. -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
