<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Sep 25, 2014 at 10:52 PM, Gianluca Cecchi <span dir="ltr"><<a href="mailto:gianluca.cecchi@gmail.com" target="_blank">gianluca.cecchi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="">On Thu, Sep 25, 2014 at 8:38 PM, 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:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Hi Gianluca,<br>
<br>
I see the numa mode select box in the Host sub-tab of the VM edit dialog.<br>
<br>
It was committed three days ago to the 3.5 branch so it should be available in the 3.5 GA release I think. I am not exactly sure if it made the RC3 build though.<br>
<br>
<a href="http://gerrit.ovirt.org/#/q/I05b83028b722088e39ad7156c77ad4eb479dc241,n,z" target="_blank">http://gerrit.ovirt.org/#/q/I05b83028b722088e39ad7156c77ad4eb479dc241,n,z</a><br></blockquote><div><br></div></span><div>Strange.<br></div><div>For my hypervisor it represents a regression. No VM is able to start with default parameters.<br></div><div>I can access the GUI again and it seems I cannot change the parameter. <br></div><div>See here screenshot:<br></div><div><a href="https://drive.google.com/file/d/0BwoPbcrMv8mvTTZCb3RTRUdFcGc/edit?usp=sharing" target="_blank">https://drive.google.com/file/d/0BwoPbcrMv8mvTTZCb3RTRUdFcGc/edit?usp=sharing</a> <br></div></div><br></div><div class="gmail_extra">For the vm where I changed the setting through Rest API I see the field greyed too, but the value inside is "interleave" and not "preferred"<br><br></div><div class="gmail_extra">Is there any engine-config option to change default?<span class=""><font color="#888888"><br></font></span></div><span class=""><font color="#888888"><div class="gmail_extra"><br></div><div class="gmail_extra">Gianluca<br></div><div class="gmail_extra"> <br></div></font></span></div></blockquote><div><br></div><div>Hello, </div><div>so on engine I have</div><div>ovirt-engine-3.5.0-0.0.master.20140923231936.git42065cc.el6.noarch<br></div><div>and on node I have</div><div>vdsm-4.16.5-0.el6.x86_64<br></div><div>libvirt-0.10.2-29.el6_5.12.x86_64<br></div><div>They should be what in 3.5rc3<br></div><div>New VMs created in 3.5rc3 are ok in the sense that I verified that numa_tune_mode is populated by default with "interleave" value that my node is able to manage to correctly start VMs.</div><div><br></div><div>But all the 3 VMs that was previously created in 3.5rc2 had numa_tune_mode=preferred that lets them unable to be started with the specified error.</div><div><br></div><div>I don't know if this is a problem only because they were created in 3.5rc2 or if this problem could influence also oVirt 3.4 infras that are upgrading to 3.5 and so a critical regression.</div><div><br></div><div>Gianluca</div><div><br></div><div><br></div></div><br></div></div>