Bug 1293937

Summary: [SR-IOV] - VF that was attached to VM via HostDevices sub tab considered as free
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Dan Kenigsberg <danken>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.6.1.3CC: bugs, stirabos, ylavi
Target Milestone: ovirt-3.6.2Flags: rule-engine: ovirt-3.6.z+
ylavi: planning_ack+
rule-engine: devel_ack+
rule-engine: testing_ack+
Target Release: 3.6.2.5   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-18 11:00:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Michael Burman 2015-12-23 15:25:33 UTC 
Description of problem:
[SR-IOV] - VF that was attached to VM via HostDevices sub tab considered as free and can cause sometimes to other VM to fail running if it trying to run with a passthrough vNIC, because it tries to use the directly attached VF.

Version-Release number of selected component (if applicable):
3.6.2

How reproducible:
Sometimes 

Steps to Reproduce:
1. Enable few VFs on capable sr-iov host 
2. Attach 1 VF directly to a VM via HostDevices sub tab
3. Run VM
4. Add vNIC with passthrough profile to other VM and try to run it 

Actual results:
Sometimes VM failing to run, because the directly attached VF considered as free

Expected results:
VF that was attached directly to VM via HostDevices sub tab should be considered 
as non-free
Comment 1 Michael Burman 2016-01-17 09:31:45 UTC 
Verified on - 3.6.2.5-0.1.el6