[libvirt] [PATCH v6 02/23] conf: introduce virNetworkPortDefPtr struct and XML support

[Daniel P. Berrangé]

On Fri, May 24, 2019 at 03:28:31PM -0400, Laine Stump wrote:
> On 5/23/19 11:32 AM, Daniel P. Berrangé wrote:
> > Introduce a virNetworkPortDefPtr struct to represent the data associated
> > with a virtual network port. Add APIs for parsing/formatting XML docs
> > with the data.
> > 
> > Signed-off-by: Daniel P. Berrangé <berrange at redhat.com>
> [...]
> > 
> > +    <pre>
> > +<networkport
> > +  <uuid>7ae63b5f-fe96-4af0-a7c3-da04ba1b3f54</uuid>
> > +  <owner>
> > +    <uuid>06578fc1-c686-46fa-bc2c-220893b466a6</uuid>
> > +    <name>myguest<name>
> > +  </owner>
> 
> 
> It just occurred to me that virHostdevManager (which is used by the node
> device driver to keep track of PCI and USB devices) maintains not only the
> domain name of the current owner of a device, but also which hypervisor
> driver that domain is in. Most of the time a host will only be using one
> hypervisor driver, but there may be cases where someone is, e.g., using qemu
> and lxc on the same host, and they could theoretically each have a domain
> with the same name. I wonder if we should add this to the <owner> element.
> (If it's useful here, it may also be useful for nwfilter bindings). It can
> always be added later though, so no need to think about it too much now...

We have the exact same blob of XML in the virNWFilterBinding XML schema
too, so I should think about that for both.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|