Comment 1 for bug 1961587

we spoke about this on irc and I agree with gibi that architecturally we should not couple the nuetorn module to the
virt driver or host operating system by using sysfs or having the neutron module call into the virt driver.

in the specific cases referred too in the bug the virtdriver should be able to populate the required info into the extra_info
filed of the pcidevice object and optionally expose that as properties on the object for convenience avoiding version bump and maintaining backwards compatibility.

this will allow the neutron module to be virt and sysfs independent and move the PCI module dependice to the virt driver which already depend on it today.

this is triaged as a medium bug since it will not break any existing deployments since hyperv does not support PCI passthrough or sriov today but going forward we should not continue this design approach so this is latent tech debt that is good to clean up.

this approach was first introduced with the port minium bandwidth qos feature and has recently been followed by the off path network backends feature which brought this architectural defect to light.