Bug 1157149

Summary: Regression: Upgrading data center to 3.5 prevents VMs from starting because of NUMA policy
Product: [Retired] oVirt Reporter: Daniel Helgenberger <daniel.helgenberger>
Component: ovirt-engine-coreAssignee: bugs <bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Stehlik <pstehlik>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 3.5CC: bugs, ecohen, gchaplik, gklein, iheim, lsurette, rbalakri, sbonazzo, yeylon
Target Milestone: ---Keywords: Regression
Target Release: 3.5.1   
Hardware: x86_64   
OS: Linux   
Whiteboard: sla
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-21 16:13:18 UTC Type: Bug
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:    
Bug Blocks: 1155170    

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.