Bug 1957551
| Summary: | [RFE] Dynamically pin vCPUs to physical CPUs on the host | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Germano Veit Michel <gveitmic> |
| Component: | ovirt-engine | Assignee: | Liran Rotenberg <lrotenbe> |
| Status: | CLOSED DUPLICATE | QA Contact: | Polina <pagranat> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.4.6 | CC: | ahadas, emarcus, lrotenbe, mavital, sigbjorn.lie |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-03-27 16:21:10 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: | 1979041 | ||
| Bug Blocks: | 1729464 | ||
|
Description
Germano Veit Michel
2021-05-06 01:53:06 UTC
As discussed offline, currently we are going to block the existing policy. This means - it will dropped from the UI and blocked in the backend for API usage. Until we make the existing policy more reasonable to use, this is the best solution for now. The scope of this one is: 1. Pin the vCPUs in a way that they are better spread across the physical CPUs on the host 2. It does not mean we do dedicated pinning, i.e., other VMs that specified with pinning string or whose vCPUs are not pinned may run on the same pCPUs as the pinned vCPUs 3. This means that the pinning should be set when running the VM (we need to know on which host the VM is going to run and what's the current pinning rules on that host) Liran, please update the patch to point to bz 1963680 Is handled as part of bz 1782077 *** This bug has been marked as a duplicate of bug 1782077 *** |