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

Bug 1498187

Summary: support automatic io threads+emulator threads pinning for High Performance VMs
Product: [oVirt] ovirt-engine Reporter: Sharon Gratch <sgratch>
Component: BLL.VirtAssignee: Sharon Gratch <sgratch>
Status: CLOSED CURRENTRELEASE QA Contact: Artyom <alukiano>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: bugs, tjelinek
Target Milestone: ovirt-4.2.0Keywords: Triaged
Target Release: ---Flags: rule-engine: ovirt-4.2+
rule-engine: planning_ack+
tjelinek: devel_ack+
mavital: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 11:45:48 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:    
Bug Blocks: 1457239    

Description Sharon Gratch 2017-10-03 16:22:09 UTC
Description of problem:
support automatic io threads+emulator threads pinning for  High Performance VMs

Comment 1 Red Hat Bugzilla Rules Engine 2017-10-03 16:22:40 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 2 Sharon Gratch 2017-10-25 09:50:24 UTC
No documentation is needed here since it is part of the "high performance feature documentation (https://bugzilla.redhat.com/show_bug.cgi?id=1505927)

Comment 4 Artyom 2017-12-03 11:54:26 UTC
Verified on rhvm-4.2.0-0.5.master.el7.noarch

Comment 5 Sandro Bonazzola 2017-12-20 11:45:48 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.