Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1691760 - not able to enable VF on broadcom network card
Summary: not able to enable VF on broadcom network card
Status: NEW
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 4.2.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-4.3.5
: ---
Assignee: Dan Kenigsberg
QA Contact: Lukas Svaty
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-22 12:53 UTC by Marian Jankular
Modified: 2019-04-11 08:26 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
oVirt Team: Network
Target Upstream Version:

Attachments (Terms of Use)
vdsm and supervdsm logs (deleted)
2019-03-22 12:57 UTC, Marian Jankular
no flags Details

Description Marian Jankular 2019-03-22 12:53:16 UTC
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

Comment 1 Marian Jankular 2019-03-22 12:57:39 UTC
Created attachment 1546837 [details]
vdsm and supervdsm logs

Note You need to log in before you can comment on or make changes to this bug.