Re: [ovirt-users] numa error after upgrading from 3.5rc2 to 3.5rc3
Hi,
I think the default was changed to INTERLEAVE, because that is the value I see everywhere
as preselected in the current 3.5 code.
This is the logic that governs if the select boxes are enabled:
if (getModel().getMigrationMode().getSelectedItem() != MigrationSupport.PINNED_TO_HOST ||
getModel().getIsAutoAssign().getEntity() ||
getModel().getDefaultHost().getSelectedItem() == null ||
!getModel().getDefaultHost().getSelectedItem().isNumaSupport()) {
enabled = false;
}
So it seems that the following conditions have to be satisfied for the select boxes to be
enabled:
The VM has to be pinned to a NUMA host (check that please, it might allow you to update
the values using UI).
Have the default host set (probably satisfied by the previous condition)
The host has to support NUMA
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.
Regards
--
Martin Sivák
msivak(a)redhat.com
Red Hat Czech
RHEV-M SLA / Brno, CZ
----- Original Message -----
On Thu, Sep 25, 2014 at 10:52 PM, Gianluca Cecchi
<gianluca.cecchi(a)gmail.com
> wrote:
> On Thu, Sep 25, 2014 at 8:38 PM, Martin Sivak <msivak(a)redhat.com> wrote:
>
>> Hi Gianluca,
>>
>> I see the numa mode select box in the Host sub-tab of the VM edit dialog.
>>
>> 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.
>>
>> http://gerrit.ovirt.org/#/q/I05b83028b722088e39ad7156c77ad4eb479dc241,n,z
>>
>
> Strange.
> For my hypervisor it represents a regression. No VM is able to start with
> default parameters.
> I can access the GUI again and it seems I cannot change the parameter.
> See here screenshot:
>
> https://drive.google.com/file/d/0BwoPbcrMv8mvTTZCb3RTRUdFcGc/edit?usp=sha...
>
> 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"
>
> Is there any engine-config option to change default?
>
> Gianluca
>
>
Hello,
so on engine I have
ovirt-engine-3.5.0-0.0.master.20140923231936.git42065cc.el6.noarch
and on node I have
vdsm-4.16.5-0.el6.x86_64
libvirt-0.10.2-29.el6_5.12.x86_64
They should be what in 3.5rc3
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.
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.
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.
Gianluca