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

Bug 1887356

Summary: [RFE] Introduce auto-pinning to high performance VM
Product: [oVirt] ovirt-engine Reporter: Liran Rotenberg <lrotenbe>
Component: BLL.VirtAssignee: Liran Rotenberg <lrotenbe>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.4.1.4CC: ahadas, bugs
Target Milestone: ovirt-4.4.5Keywords: FutureFeature, RFE
Target Release: ---Flags: pm-rhel: ovirt-4.4?
pm-rhel: planning_ack?
pm-rhel: devel_ack?
pm-rhel: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-16 09:14:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1862968    
Bug Blocks:    

Description Liran Rotenberg 2020-10-12 08:35:55 UTC 
We introduced auto-pinning only to REST-API in BZ 1862968, which will set the CPU pinning and NUMA pinning to the best performance.

The idea of HP VMs is the same, at the moment users should set it manually.
Since we have both parts apart, it's good idea to give an option to the users to set it into HP VMs and skip the manual setting for the CPU.
Comment 1 Arik 2020-11-16 09:14:15 UTC 

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