Bug 1157149 - Regression: Upgrading data center to 3.5 prevents VMs from starting because of NUMA policy
Summary: Regression: Upgrading data center to 3.5 prevents VMs from starting because o...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.5
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ---
: 3.5.1
Assignee: bugs@ovirt.org
QA Contact: Pavel Stehlik
URL:
Whiteboard: sla
Depends On:
Blocks: oVirt_3.5.1_tracker
TreeView+ depends on / blocked
 
Reported: 2014-10-25 12:02 UTC by Daniel Helgenberger
Modified: 2016-02-10 19:41 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-01-21 16:13:18 UTC
oVirt Team: SLA
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 33732 0 None None None Never

Description Daniel Helgenberger 2014-10-25 12:02:56 UTC
Description of problem:
Upgrading clusters / datacenters from a previous (3.x) release may result in VMs not being able to start any more with the error:
internal error NUMA memory tuning in 'preferred' mode only supports single node
Even if NUMA pinning is turned off for this VM.

Version-Release number of selected component (if applicable):
3.5

How reproducible:
unknown, seems to be confined to Windows Guests for some reason


Steps to Reproduce:
1. Create a Windows guest in oVirt 3.4.x. Make sure the VM is not pinned to a host
2. Upgate oVirt / datacenter to 3.5
3. Check VM is still not pinned and has NUMA turned off. Now, a greyed out box with 'NUMA policy: preferred' is shown.
4. Run VM

Actual results:
VM is unable to start. Error message: internal error NUMA memory tuning in 'preferred' mode only supports single node

Expected results:
VM starts up normally

Additional info:
Workaround: Either enable NUMA for the VM and leave preferred. Or, enable NUMA, set mode to 'interleave' and turn of NUMA again. [1]

For the user it is really hard to understand because NUMA was never turned on in the first place.

[1] http://lists.ovirt.org/pipermail/users/2014-September/027891.html

Comment 1 Sandro Bonazzola 2015-01-21 16:13:18 UTC
oVirt 3.5.1 has been released and since this bug is targeted 3.5.1 and in modified state, it should be included in this release.
Please re-target and move nack to modified if this assumption is not valid for this bug.


Note You need to log in before you can comment on or make changes to this bug.