<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Sep 26, 2014 at 10:56 AM, Martin Sivak <span dir="ltr"><<a href="mailto:msivak@redhat.com" target="_blank">msivak@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I think the default was changed to INTERLEAVE, because that is the value I see everywhere as preselected in the current 3.5 code.<br>
<br>
This is the logic that governs if the select boxes are enabled:<br>
<br>
if (getModel().getMigrationMode().getSelectedItem() != MigrationSupport.PINNED_TO_HOST ||<br>
getModel().getIsAutoAssign().getEntity() ||<br>
getModel().getDefaultHost().getSelectedItem() == null ||<br>
!getModel().getDefaultHost().getSelectedItem().isNumaSupport()) {<br>
enabled = false;<br>
}<br>
<br>
So it seems that the following conditions have to be satisfied for the select boxes to be enabled:<br>
<br>
The VM has to be pinned to a NUMA host (check that please, it might allow you to update the values using UI).<br>
Have the default host set (probably satisfied by the previous condition)<br>
The host has to support NUMA<br>
<br>
I am adding Gilad to CC as he knows the code. Unfortunately he will be available some time next week as they have a holiday season in Israel atm.<br></blockquote><div><br></div><div>The point here is:</div><div>If I am on oVirt 3.4.x environment, is this numa_tune_mode parameter present in the VM definition?</div><div>I have not at hand now a 3.4 system so I cannot check.</div><div>If not present at all in pre-3.5 VMs and I upgrade my environment, what would be done for my pre-existing VMs?</div><div>Because I verified (not from 3.5rc3 scratch installation but upgrading from 3.5rc2) that for new VMs indeed the parameter is set with "interleave" as default.</div><div>I don't know if inside the sql upgrade scripts there is something like</div><div><br></div><div>if current < 3.5 then add parameter and set to interleave</div><div><br></div><div>So in this case it would make the correct thing for 3.4 environments, but as a corner effect it would do nothing for my 3.5.rc2 environment, that still didn't have the parameter, causing the problem I'm experiencing....</div><div><br></div><div>Gianluca </div></div></div></div>