Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 615039 - Define and implement API for reporting and using SRIOV devices.
Define and implement API for reporting and using SRIOV devices.
Status: CLOSED WONTFIX
Product: oVirt
Classification: Retired
Component: vdsm (Show other bugs)
unspecified
All Linux
low Severity medium
: ---
: ---
Assigned To: Dan Kenigsberg
network
: FutureFeature
Depends On: 625530
Blocks: 641301
  Show dependency treegraph
 
Reported: 2010-07-15 16:10 EDT by Dan Kenigsberg
Modified: 2013-03-11 17:49 EDT (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 607609
Environment:
Last Closed: 2013-03-11 17:49:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Dan Kenigsberg 2010-07-15 16:10:12 EDT
1. getCapabilities - VDSM should report 2 additional properties:
         1. per nic:  SRIOV = VF/PF/unvirtualized
         2. per network: bridged/sriov

2. addNetwork - The interface today includes: bridge,vlan,bond,nics,options
      For 2.3 version, passing the option SRIOV=true/false tell if vdsm creates a bridge-based of sriov-based network.

3. getVdsStats - report how many VFs are available for each sriov-based network

4. create - no change in API. Implementation makes sure that only virtio interfaces are connected to sriov-based network. If no VF is available, connect the newly created VM through a bridge.
Comment 1 Itamar Heim 2013-03-11 17:49:44 EDT
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.

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