I see where the problem could be. "get_available_resource" will call "_get_pci_passthrough_devices" -> "_get_pcidev_info" -> "_get_device_capabilities" -> "_get_pcinet_info" -> "get_net_name_by_vf_pci_address" (here we have the warning message).
When "get_available_resource" is called before a VM is created, the VF port is present in the kernel. But this method is called "as part of a periodic task that records the results in the DB" (from the function description). When the port is bound to the VM, the network interface is not longer present in the host kernel and the method will log this warning message.
Because this is something usual in normal operation, I would recommend to lower to log severity to INFO or DEBUG.
Hello:
I see where the problem could be. "get_available_ resource" will call "_get_pci_ passthrough_ devices" -> "_get_pcidev_info" -> "_get_device_ capabilities" -> "_get_pcinet_info" -> "get_net_ name_by_ vf_pci_ address" (here we have the warning message).
When "get_available_ resource" is called before a VM is created, the VF port is present in the kernel. But this method is called "as part of a periodic task that records the results in the DB" (from the function description). When the port is bound to the VM, the network interface is not longer present in the host kernel and the method will log this warning message.
Because this is something usual in normal operation, I would recommend to lower to log severity to INFO or DEBUG.