Description of problem: not able to enable VF on broadcom network card Version-Release number of selected component (if applicable): tested on rhvm 4.1.11 and 4.2.8 host used redhat-release-virtualization-host-4.2-7.5.el7.x86_64 () How reproducible: everytime with BCM57810 Steps to Reproduce: 1. enable "intel_iommu=on" 2. try to enable VF in "Setup Host Network" Actual results: it will fail with error "Failed to change the number of virtual functions." Expected results: Enabling VF will work. Additional info: workaround possible: 1, put host to maintenance 2, try to enable VF on the network card (as it will fail, cancel the "Setup Host Networks" window) 3, refresh host capabilities (right-click on the host > management > refresh capabilities) 4, virtual function are visible now
Created attachment 1546837 [details] vdsm and supervdsm logs
SR-IOV card that has SCSI offloading feature might display net device and offload under the same PCI root. This leads to exception thrown by vdsm when we try to set number of VFs, because vdsm is not capable to decide which device should be used to find the interface name. This can be easily fixed with filter that will list only net devices under particular PCI root.
[root@dell-m620-07 ~]# rpm -qe vdsm vdsm-4.30.25-1.el7ev.x86_64 [root@dell-m620-07 ~]# cat /tmp/sriov_test { "deviceName": "pci_0000_01_00_0", "numvfs": "1" } [root@dell-m620-07 ~]# vdsm-client -f /tmp/sriov_test Host hostdevChangeNumvfs true [root@dell-m620-07 ~]# cat /sys/bus/pci/devices/0000\:01\:00.0/sriov_numvfs 1 [root@dell-m620-07 ~]# cat /tmp/sriov_test0 { "deviceName": "pci_0000_01_00_0", "numvfs": "0" } [root@dell-m620-07 ~]# vdsm-client -f /tmp/sriov_test0 Host hostdevChangeNumvfs true [root@dell-m620-07 ~]# cat /sys/bus/pci/devices/0000\:01\:00.0/sriov_numvfs 0
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:3009