When using DPDK on Azure it is common to have one non-DPDK interface. If that non-DPDK interface is present vdev_netvsc correctly skip it. But if the non-DPDK has accelerated networking the Mellanox driver will still get associated with DPDK (and break connectivity).
The current process is to tell users to do whitelist or blacklist the PCI device(s) not used for DPDK. But vdev_netvsc already is doing a lot of looking at devices and VF devices. Could vdev_netvsc just do this automatically by setting devargs for the VF to blacklist?
