Bug 1099417

Summary:	nodeset of numatune is not calculated correctly
Product:	[Retired] oVirt	Reporter:	Bruce Shi <xiao-lei.shi>
Component:	ovirt-engine-core	Assignee:	Bruce Shi <xiao-lei.shi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.5	CC:	bugs, gchaplik, gklein, iheim, lagarcia, rbalakri, yeylon
Target Milestone:	---
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	sla
Fixed In Version:	ovirt-3.5.0_rc3	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-17 12:41:40 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:

Description Bruce Shi 2014-05-20 09:15:01 UTC

Description of problem:
When building libvirt xml, it uses vm.getRunOnVds to get the vds id which the vm will run, actually this field is filled after the vm is running, it's null when building the xml. It will cause the calculation of numa tune node set failed.

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

How reproducible:
100%

Steps to Reproduce:
1.try create a VM using the default settings
2.
3.

Actual results:
No numatune configuation in libvirt xml.

Expected results:
Numetune configuration should be append.

Additional info:

Comment 1 Sandro Bonazzola 2014-10-17 12:41:40 UTC

oVirt 3.5 has been released and should include the fix for this issue.