Bug 1220122
Summary: | Run vm with one cpu and two numa nodes failed | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
Component: | ovirt-engine | Assignee: | Dudi Maroshi <dmaroshi> |
Status: | CLOSED ERRATA | QA Contact: | Artyom <alukiano> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.5.0 | CC: | dfediuck, ecohen, gklein, istein, juwu, lpeer, lsurette, rbalakri, rgolan, Rhev-m-bugs, sherold, tnisan, yeylon |
Target Milestone: | --- | Keywords: | Reopened, ZStream |
Target Release: | 3.5.3 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | sla | ||
Fixed In Version: | org.ovirt.engine-root-3.5.3-2 | Doc Type: | Bug Fix |
Doc Text: |
Previously, verification for NUMA nodes correlation to CPUs were missing and resulted in an inefficient NUMA architecture. This update adds validation for NUMA nodes correlation to CPUs in both the GUI and REST API.
|
Story Points: | --- |
Clone Of: | 1196235 | Environment: | |
Last Closed: | 2015-06-15 13:28:34 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1196235 | ||
Bug Blocks: |
Comment 2
Artyom
2015-05-17 08:21:58 UTC
Checked comment 2. Working as designed. The complaint in comment 2 is valid. We need to open a new bug on comment 2. With title: "Adding NUMA node with 0 CPU cores fails libvirt." Reason for opening a new bug: The current bug is about validating VM for: NUMA nodes and CPUs. The new bug is about validating NUMA node request. As for the complaint about inconvenient error message (reset all the user's work). This is a know architectural deficiency. Will not be addressed in the current version. Comments appreciated. Ok thanks for explanation, I already have opened couple of bug connect to NUMA validation under REST. Verified on rhevm-3.5.3-0.2.el6ev.noarch 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/RHBA-2015-1095.html |