Created attachment 941997[details]
logs
Description of problem:
Run vm in preferred mode drop libvirt error
Version-Release number of selected component (if applicable):
rhevm-3.5.0-0.13.beta.el6ev.noarch
How reproducible:
Always
Steps to Reproduce:
1. Create vm
2. Change vm mode to preferred:
<vm>
<numa_tune_mode>preferred</numa_tune_mode>
</vm>
3. Run vm
Actual results:
Vm failed to run
Expected results:
Vm success to run
Additional info:
Tried to run vm with 0,1,2 numa nodes
this bug status was moved to MODIFIED before engine vt5 was built,
hence moving to on_qa, if this was mistake and the fix isn't in,
please contact rhev-integ
Verified on vt5, I see that patch just prevent to create or update vm in preferred mode in vmNumaNodes != 1 and if it not pinned, I really don't understand why I can't use this mode for more that 1 node. But it's problems of libvirtd, so I verify bug.
Was success to change vm mode to preferred with next scenario:
1) Specify vm host to start to host with numa support and deny migration("Do not allow migration"), change NumaNodeCount to 1 and mode to preferred and also pin this VNUMA to PNUMA, click ok.
2) Edit this vm and just change "Start running on:" to "Any Host in Cluster", click ok.
Now you have vm without NUMA pinning in preferred mode.
Also when vm with preferred mode, engine success to run vm(if no VNUMA appear, engine also not run vm with tune mode). So I will open another bug that I success to change mode to prefer.
Created attachment 941997 [details] logs Description of problem: Run vm in preferred mode drop libvirt error Version-Release number of selected component (if applicable): rhevm-3.5.0-0.13.beta.el6ev.noarch How reproducible: Always Steps to Reproduce: 1. Create vm 2. Change vm mode to preferred: <vm> <numa_tune_mode>preferred</numa_tune_mode> </vm> 3. Run vm Actual results: Vm failed to run Expected results: Vm success to run Additional info: Tried to run vm with 0,1,2 numa nodes