Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1228591

Summary: CPU Pinning topology still suggests to use Host CPU check box
Product: Red Hat Enterprise Virtualization Manager Reporter: Anand Nande <anande>
Component: DocumentationAssignee: Tahlia Richardson <trichard>
Status: CLOSED CURRENTRELEASE QA Contact: Julie <juwu>
Severity: medium Docs Contact:
Priority: high    
Version: 3.5.0CC: adahms, ecohen, lsurette, pstehlik, rbalakri, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-05 07:15:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1244999    

Description Anand Nande 2015-06-05 09:37:14 UTC
Description of problem:

The documentation still suggests:

In order to pin a virtual machine to a host, you must select Do not allow migration under Migration Options, and select the Use Host CPU check box. 

There is no more 'Use Host CPU check box' in the webadmin-portal.

The docs need to be updated to 'Use Pass-Through Host CPU' check box.

Also a clear flow like below would be great to have:

In the Edit VM window 
 |
 |--------> Host TAB 
 |            |--------> Start Running On: Specific Host
 |            |--------> Migration Options: Set "Do not allow migration"
 |            |--------> Pass-Through Host CPU
 |
 |--------> Resource Allocation TAB
              |--------> CPU Allocation: 
                         |---------> CPU Pinning topology: 0#2_1#4

[The above is just an example of mapping vCPU#0:pCPU2,vCPU#1:pCPU#4]

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

Comment 2 Andrew Dahms 2015-06-22 01:40:50 UTC
Assigning to Tahlia for review.

Comment 3 Andrew Dahms 2015-06-24 05:15:10 UTC
Assigning juwu as the QA contact.