Bug 1469842 - There is no clear procedure defined in RHV installation or Administration guide to configure SRIOV
Summary: There is no clear procedure defined in RHV installation or Administration gui...
Keywords:
Status: CLOSED DUPLICATE of bug 1470382
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.1.0
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
: ---
Assignee: rhev-docs@redhat.com
QA Contact: rhev-docs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-12 00:11 UTC by puneet
Modified: 2019-05-07 12:55 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-17 08:23:39 UTC
oVirt Team: Docs
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description puneet 2017-07-12 00:11:20 UTC
Description of problem:
There is no clear procedure defined in RHV installation or Administration guide to configure SRIOV

There is no clear procedure described anywhere which can describes how to configure SRIOV from start to stop.
I came across below link to configure SRIOV on RHV but it is not correct and very confusing. In short there should be a separate section in installation guide or admin guide which describes SRIOV configuration from start to stop.Currently SRIOV configuration is scattered across whole guide and very confusing.
https://access.redhat.com/articles/2335291


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

How reproducible:
every time

Steps to Reproduce:
1. open 4.1 install or admin guide


Actual results:


Expected results:

There should be a separate section in installation guide or admin guide which describes SRIOV configuration from start to stop

Additional info:

Comment 1 Meni Yakove 2017-07-17 08:23:39 UTC
bug 1470382 is slightly more detailed and specific regarding what needs to be fixed.

*** This bug has been marked as a duplicate of bug 1470382 ***


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