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

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(a)redhat.com&gt; [...] > > + <pre> > +&lt;networkport > + &lt;uuid&gt;7ae63b5f-fe96-4af0-a7c3-da04ba1b3f54&lt;/uuid&gt; > + &lt;owner&gt; > + &lt;uuid&gt;06578fc1-c686-46fa-bc2c-220893b466a6&lt;/uuid&gt; > + &lt;name&gt;myguest&lt;name&gt; > + &lt;/owner&gt; 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...