Bug 1506198

Summary: [Docs]Need to consolidate the setup and configuration of SR-IOV on RHEV
Product: Red Hat Enterprise Virtualization Manager Reporter: Frank DeLorey <fdelorey>
Component: DocumentationAssignee: rhev-docs <rhev-docs>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kovar <pkovar>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 4.3.0CC: cminkema, danken, dcadzow, dholler, fdelorey, lsurette, mkalinin, srevivo
Target Milestone: ovirt-4.3.6Keywords: Documentation, FutureFeature
Target Release: 4.3.0Flags: lsvaty: testing_plan_complete-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-07 17:05:16 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1706778    

Description Frank DeLorey 2017-10-25 11:41:38 UTC
Description of problem:
Currently we had pointing customers to multiple documents to figure out how to correctly setup and configure SR-IOV on RHEV. This is causing lots of wasted time and is very frustrating for customers and support as we have circular links and the steps are scattered between at least three seperate documents one of them not RHEV specific.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
Have clear steps in one document, I would recommend the Admin Guide, that shows how to setup and then configure SR-IOV on RHEV.

Additional info:

Comment 1 Lucy Bopf 2017-11-28 01:58:14 UTC
Adding needinfo on Derek.

Derek, as discussed, we should include this request in our ongoing content strategy, so we can determine how to approach any restructuring, and where it fits into upcoming programs.

Comment 2 Dan Kenigsberg 2018-09-03 08:52:34 UTC
Frank could you elaborate what you find as circular and confusing?

I see that we tell how to configure a host

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/installation_guide/appe-configuring_a_hypervisor_host_for_pci_passthrough

how to set the number of VFs
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/administration_guide/#Editing_VFs_on_NIC

how to define an SR-IOV-ready vNIC Profile
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/administration_guide/#Enabling_Passthrough_on_a_vNIC_Profile

and a bit more to allow live migration of VMs connected to SR-IOV
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/virtual_machine_management_guide/#Live_migration_prerequisites


Would you like these pointers to be aggregated into an "SR-IOV user story"? Such story would have to involve multiple user roles: the host admin, the network admin and the VM admin.

Comment 4 Frank DeLorey 2018-09-11 12:58:06 UTC
I think a concise set of steps would make this less painful for customers. We should not have to start in Appendix G then jump back to earlier chapters for each step. Even just a set of steps that maybe point to the already existing steps so that we can covey the exact sequence of steps required. So perhaps a story as you stated with something like this:

Step 1 : Configure the host (with a link) https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/installation_guide/appe-configuring_a_hypervisor_host_for_pci_passthrough

Step 2: Set the number of VFs (with a link) https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/administration_guide/#Editing_VFs_on_NIC

Step 3: Define an SR-IOV-ready vNIC Profile (with a link) https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/administration_guide/#Enabling_Passthrough_on_a_vNIC_Profile

Step 4: Make the VM with SR-IOV capable of being migrated (with a link)  https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/virtual_machine_management_guide/#Live_migration_prerequisites

Comment 5 Sandro Bonazzola 2019-01-28 09:44:27 UTC
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 8 Marina Kalinin 2019-02-27 18:43:38 UTC
*** Bug 1679695 has been marked as a duplicate of this bug. ***

Comment 10 Rolfe Dlugy-Hegwer 2019-05-30 15:56:24 UTC
*** Bug 1706778 has been marked as a duplicate of this bug. ***

Comment 18 Raul Aldaz 2022-04-05 13:46:03 UTC
*** Bug 1706778 has been marked as a duplicate of this bug. ***