Bug 838490
| Summary: | [RFE] Specify CPU per VM - lower or equal than cluster cpu, or non-migratable | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Andrew Cathrow <acathrow> | |
| Component: | RFEs | Assignee: | Michal Skrivanek <michal.skrivanek> | |
| Status: | CLOSED ERRATA | QA Contact: | sefi litmanovich <slitmano> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 3.1.0 | CC: | gklein, iheim, istein, lpeer, melewis, michal.skrivanek, rbalakri, sherold | |
| Target Milestone: | ovirt-3.6.0-rc | Keywords: | FutureFeature | |
| Target Release: | 3.6.0 | Flags: | sherold:
Triaged+
|
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| URL: | http://www.ovirt.org/Features/Cluster_parameters_override | |||
| Whiteboard: | ||||
| Fixed In Version: | ovirt-3-6-0-2 | Doc Type: | Enhancement | |
| Doc Text: |
Some cluster parameters can now be overridden on a per VM basis. See http://www.ovirt.org/Features/Cluster_parameters_override for detailed description
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 952238 (view as bug list) | Environment: | ||
| Last Closed: | 2016-03-09 20:26:57 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: | 1236049 | |||
| Bug Blocks: | 952238, 1302707 | |||
|
Description
Andrew Cathrow
2012-07-09 09:05:24 UTC
Andrew - can you please elaborate on goal/reason here? we have the -cpu host for performance. I assume you don't want someone to set a VM to a lower cpu, rather only to a higher one, which may make it impossible to migrate, etc. is this supposed to be like -cpu host, but "hopefully migrate-able"? (switching to sla, as main consideration here will be scheduling) User cases 1. Allow a virtual machine to maintain a static CPU configuration. eg. User is running VM on westmere host and upgrades the host systems to sandybridge. Just because we are using a SandyBridge based host it doesn't mean we want to expose that to the guest. The guest may need to keep a consistent CPU and hardware profile. 2. Best performance (+ migration and stability) - 10 node cluster. - 8 nodes are westmere, 2 are sandybridge - Cluster level set to "westmere" Allow admin to run VM with hardcoded "sandybridge" CPU on one of the 2 applicable hosts. Support migration between compatible hosts. Obviously this brings with it restrictions. - If no sandbridge system is running (or has capacity) then the VM can't be run - You can only migrate between the 2 sandybridge machines - If only one sandybridge machine is running the host won't be able to go into maintenance mode since it can't live migrate to another host so the VM will need to be stopped first. I've created bug 952238 as a clone of this bug for the more complex 2nd use case. so 1st use case can cover the simpler modes: - VM can be set to any cpu model *lower or equal* than cluster model without pinning (for static configuration) - VM can be set to any cpu model higher than cluster model in non-migratable mode. patch series: http://gerrit.ovirt.org/32546 http://gerrit.ovirt.org/32547 http://gerrit.ovirt.org/32548 http://gerrit.ovirt.org/31581 http://gerrit.ovirt.org/31582 Verified with rhevm-3.6.2-0.1.el6.noarch according to attached test plan. Test run: https://polarion.engineering.redhat.com/polarion/#/project/RHEVM3/testrun?id=3_6_VIRT_Cluster_Parameters_Override_23122015 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-0376.html |