Bug 1498187 - support automatic io threads+emulator threads pinning for High Performance VMs
Summary: support automatic io threads+emulator threads pinning for High Performance VMs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.2.0
: ---
Assignee: Sharon Gratch
QA Contact: Artyom
URL:
Whiteboard:
Depends On:
Blocks: 1457239
TreeView+ depends on / blocked
 
Reported: 2017-10-03 16:22 UTC by Sharon Gratch
Modified: 2017-12-20 11:45 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-20 11:45:48 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: planning_ack+
tjelinek: devel_ack+
mavital: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 82523 0 master MERGED core: support IO+emulator threads pinning for HP vms 2017-10-24 15:01:04 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.