On Tue, Sep 20, 2016 at 07:21:07PM +0200, Paolo Bonzini wrote:
> On 20/09/2016 17:14, Daniel P. Berrange wrote:
> > Any VM which
> > uses the separate namespace is tainted, which means if theres a bug
> > report we'll require the reported to remove whatever config caused
> > the tainting and then reproduce the problem.
> > 
> > If the vendor specific mdev parameters are things that apps will often
> > need to be able to set, then allowing it via a separate namespace is
> > just providing a backdoor that everyone needs to use, defeating the
> > point of using a separate namespace.
> No, they don't need to be often set, and tainting the domain is a good idea.

Basically think of the XML namespace support as

 "a mechanism for accessing underlying platform features before they
  are exposed in the main XML, that happens to use the vendor specific
  data format"

*not* as

 "a mechanism for exposing vendor specific functionality"

|: 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 :|

Reply via email to